mounting /images failed: Connection timed out
-
@george1421Please understand I am very new to Linux, I appreciate all the commands you have sent. I downloaded the latest kernel for 1.2.0, however i do not remember the version. I can try to revert to old kernel.
To clarify, yes the setup worked. I was able to upload and download an image. Host had an ip address ending in 6.62, Fog server Vm ip address ending in 28.10, client got its ip from the dhcp server in the subnet as fog server 28.xx.
No the original system does not work any longer.
TO my knowledge I have not changed anything else except the kernel.
As a test this morning I put host, server, and client on the same subnet. I still get the same result. I am thinking its got to be the kernel. Thoughts?
-
@sjensen The kernel has nothing to do with connecting to the NFS Mount point. Support for NFS is embedded in every kernel in the same way (so if one kernel works all the rest will as well).
You can try reverting to the original kernel but I don’t think that will fix the issue either. From a client within a Debug mode: (From FOG GUI goto Host->Basic Tasks->Advanced->Download - Debug)
Let the system boot and press enter if/when prompted to. It will drop the client machine booting into a console shell.
Let me know when it’s there.
-
@sjensen Thanks for the clarity on the issue.
So now we know there is a router between the target computer and the FOG server. Might you think there is some kind of filter turned on this router? Is the fog server and the target computer on the same physical campus? Understand I’m trying to get a picture of your setup. But Tom is right getting access to the target computer’s command prompt by a debug capture mode will allow us to type in commands on the target computer, to see (in a way) what the target computer sees in the form of your network.
-
@Tom-Elliott OK i will do so. Do i want download debug or upload debug?
-
@sjensen I thought my information was specific enough, but ultimately either one or the other will work just fine. In your case, as you’re trying to upload a new image?: Use upload debug.
-
@Tom-Elliott Ok it is waiting at the command prompt.
-
@sjensen Try mounting the nfs: run->
mkdir /images mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime "192.168.28.10:/images/dev" /images
-
Also, so we know the kernel version you’re running, can you get us the output of:
uname -rm
-
@sjensen The first thing I want you to do is this:
On the console of the target computer key in
ip addr show
that will tell you the current IP address of the target computer (please post it here)- I need you to give root a password so we can connect to it remotely (so you don’t have to sit in front of the target computer)
passwd
and give root a password it can be something as simple as Password-1 or complex, it is up to you. This password will exist until the target computer is rebooted so its only temporary. - Install putty on your computer [ http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html ], its a free download and will allow you to connect to the target computer over the network. You will need this to copy and paste commands given by Tom or myself. The exe is not installed, but just run.
I see Tom went in directly to the point.
-
-
This post is deleted! -
@sjensen OOoops you fell into the kernel hole. The kernels between 4.2 and 4.6 don’t work for FOG 1.2.0, if you upgrade to latest kernels for FOG 1.3.0 you will be in a better state.
cd /var/www/html/fog/service/ipxe cp bzImage bzImage.old cp bzImage32 bzImage32.old wget -P https://fogproject.org/kernels/bzImage wget -P https://fogproject.org/kernels/bzImage32
Now here is the part I’m not sure of, and Tom will need to answer. I was under the impression that FOG 1.2.0 was 32bit only? if that’s the case we need to rename the kernel file
-
@Tom-Elliott this is what got
mount: cant find images: in /etc/fstab -
@sjensen I need to see the exact mount command you used.
The command should not run multiple lines.
-
@george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.
-
@Tom-Elliott said in mounting /images failed: Connection timed out:
@george1421 1.2.0 (1.0.0 and up really) all used 64 bit and auto adjusted for 32 bit.
OK so the names bzImage == x64 and bzImage32 == x86 is still proper for 1.2.0?
-
@george1421 Yessir.
-
@george1421 Ok gentleman do I need to upgrade 1.3.0 to fix my issue? Or do I need to do some additional debuging?
-
@sjensen All of the commands I’m asking you to run should be run on the Client machine, NOT the fog server.
-
@Tom-Elliott I used the exact lines you posted on the client in debug mode as instructed. I can send a picture of what is being displayed on the clients screen.