mounting /images failed: Connection timed out

[sjensen]

I’m not sure what happened, i was able to push an image to my server. I am now getting the following message

mounting x.x.x.x:/images/dev on /images failed: Connection timed out

Fatal error: Failed to mount NFS volume

[george1421]

does your fog server have a statically defined IP address? Make sure the mounting X.X.X.X is pointing to your current fog server IP address.

[sjensen]

Yes my fog server has a statically assigned IP. Check out the attachment


[george1421]

@sjensen Hey the attachment didn’t happen.

OK, if you have a static IP address lets make sure that NFS is running. Use the following command and post the results here: showmount -e 127.0.0.1 This should show you the nfs shares on your FOG server.

[sjensen]

[sjensen]

Here you go.

[Tom Elliott]

@sjensen What’s the IP Address of the FOG Server?

Is firewall running blocking systems from connecting to it?

[sjensen]

@george1421

[george1421]

@sjensen Right, can you also answer Tom’s question about fog server IP. That was going to be my next one after “Is NFS running?” According to your image, yes it is running.

The next question would be: Did you disable the linux firewall on this box? Did it get turned on some how? iptables -L if it only displays 3 accept policies then its off.

[sjensen]

@Tom-Elliott I have no firewalls blocking. I was able to upload an image prior.

[sjensen]

@george1421

[george1421]

@sjensen OK firewall is off, what about IP address of fog server? ip addr show

[sjensen]

@george1421 address of the fog server is static. The way I have the network setup, i have a separate VLAN just for imaging. The fog server (static ip) and client (DHCP) both get an IP address from the same subnet.

[Tom Elliott]

@sjensen Is the IP Address of the FOG Server 192.168.28.18

[sjensen]

@sjensen

[Tom Elliott]

@sjensen So the picture from the NFS issue appears to be showing the IP as 192.168.28.18 or 192.168.28.18.16 (I can’t tell the picture get’s too pixelated).

Please either try getting a better picture of the message or tell us what IP it’s looking at for NFS?

[george1421]

@sjensen OK now that we confirmed the IP address is 192.168.28.10 its inline with the error message on the screen shot you posted. Its difficult to see in the picture if the last digit is an 8 or a 0, lets assume its 0.

now from the fog server command prompt lets connect to your nfs share.

mount -t nfs 192.168.28.10:/images /mnt

Then check the content of that mount

ls /mnt that should give you the same response as ls /images

If they are the same then you can nfs mount your fog server by your fog server.

You need to unmount that share to avoid conflicts in the future.

umount /mnt

[sjensen]

@george1421 The result was the same after that was mounted.

[sjensen]

@Tom-Elliott The ip is 192.168. 28.10

[Tom Elliott]

@sjensen What’s the permissions of the /images and /images/dev directories?