Problem with deployment in a physical machine / connection timeout
-
Have you imaged with this FOG server before or is it new?
The reason why I ask is the error is not related to WOL, but more of an nfs issue reaching the FOG server.
Is it also safe to assume that 192.168.230.10 is your FOG server IP address?
And finally, execute this command on your fog server
showmount -e 127.0.0.1and post the results here. -
No, I already have imaged with this FOG Server but in virtual. I have imaged virtual machines, but now I want imaged with Wake On Lan and I must image in a physical machine.
192.168.230.10 is my fog server’s address, I’m sure. But I have a switch connected between my FOG Server and my physical machine. I don’t know if the problem come here.
Here is the results :
-
It’s possible a firewall is blocking the port, which would cause it to timeout.
Might also want to doublecheck Storage Node settings
-
@Quazz
my firewall is disabled in my FOG Server. And my storage node, i haven’t touched anything. I don’t know if I must do anything in Storage Management in FOG Web UI -
@Andre OK lets do a bit of detective work.
I want you to schedule another capture or deploy (doesn’t matter) but before you hit the button to schedule the task, make sure you check the debug option. Then pxe boot the target computer. This feature will drop the pxe booting computer to a command prompt after a few pages of text. This is the command prompt of the FOS engine (customized linux OS for capture and deploying on the target computer).
Once at the command prompt see if you can ping the fog server.
If that works then we can try to nfs mount the fog server. -
@george1421 Yes I can ping my server
-
@Andre just for clarity you get a ping response from the FOS engine (pxe booted hardware)?
See if the FOS engine has the
showmountcommand. In this case you wantshowmount -e <fog_server_ip> -
@george1421 Yes I did my ping from FOS Engine
For the command showmount, it says that “command not found” -
@Andre OK from FOS do this
mkdir /mnt mount -t nfs <fog_server_ip>:/images/dev /mnt ls -la /mntThe idea is to connect from the FOS back to the fog server using nfs.
-
@george1421 I tried what you told me to do. But when I do the command for mounting, I have the same error “Connection Timeout” .
-
@george1421 But I don’t understand why in virtual it works and in physical it doesn’t work. I can deploy or capture virtual machines without problem, and physical machines I can’t.
-
This sounds an aweful lot like the nic of the fogserver is setup in Nat mode vs. bridged mode. I say this because of the “it works in virtual systems, but not on physical machines.”
-
@Tom-Elliott My Fogserver is setup in bridged mode
-
Nobody has a solution for my problem ?
-
@Andre There has to be something we are not seeing here.
Lets just recap where we are here.
- You have a new fog server that is running FOG 1.3.5 that is a physical server (not really relevant that its physical)
- Your fog server’s IP address is 192.168.230.10
- Your target computer IS talking to the FOG server because it can check in, plus FOS does load and is running.
- NFS is sharing the proper directories.
- NFS is timing out in that it can’t connect.
Possible issues.
- The firewall is running on the FOG server blocking nfs mounting.
- selinux is not set to permissive on the FOG server.
- There is some kind of screening router between the target computer and FOG server
- Not all of the nfs services are running on the FOG server
- Since there is a second fog server in the environment maybe it is playing a part in the target computer’s booting process that is unknown to us.
Since the target computer can’t seem to mount the nfs share on the physical fog server and you have a second virtual fog server, I would try to mount the nfs shares on the phy fog server from the vm fog server to confirm that nfs is working on the phy fog server.
from the vm fog server
mount -t nfs 192.168.230.10:/images /mnt ls -la /mnt umount /mntThe above command should mount the images share on the phy fog server, list the contents of the directory and then unmount the images directory. When you run this command I would expect to see something like this:
drwxrwxrwx 5 fog root 4096 Apr 4 06:37 . drwxr-xr-x 25 root root 4096 Apr 15 21:35 .. drwxrwxrwx 3 fog root 4096 Apr 4 06:37 dev -rwxrwxrwx 1 fog root 0 Sep 24 2016 .mntcheck drwxrwxrwx 2 fog root 4096 Sep 24 2016 postdownloadscriptsNot directly related to your issue, i would update your FOG server to the latest RC build of 1.4.0 to test to see if 1.3.5 is the issue. Only do this on your phy fog server.
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk -
@george1421 I just have one server FOG and it is virtual. I don’t have a Physical server FOG.
-
@george1421 I tried to mount what do you said, in a Virtual machine, on which I have already capture his image. But when I execute the command “mount -t nfs 192.168.230.10:/images /mnt”, in FOS engine. It say “connection refused”.
-
@george1421 I tried with these commands in FOS Engine, with my virtual machine :
mkdir /images
mkdir /images/dev
mount -o nolock,proto=tcp,rsize=32768,intr,noatime 192.168.230.10:/images /images
mount -o nolock,proto=tcp,rsize=32768,intr,noatime 192.168.230.10:/images/dev/ /images/devAnd it works, I can mount
-
@george1421 And when I tried to do the same thing in my physical machine, it doesn’t work
-
@Andre This is not logical.
back on the fog server can you execute this command:
cat /etc/exportsYou should get something that looks like this
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)The key to look for is the space, star ( * ) right after the share name. This restricts nfs access to specific hosts. The start means everyone.
