NFS Mount Fails... Network Unreachable
-
Hello All,
I am running FOG 1.2 on Ubuntu. Everything was working fine until a reboot of the server. I found that SAN volume had not remounted so images were not there. the mount point was but there was nothing behind it. I remounted it and images can be SENT to machines as expected.
When I attempt to create an image though, it fails. The following issue:
- Mounting File System…Mount: mounting 192.168.232.248:/san_images/dev/ on /images failed: Network is unreachable
From a windows machine, I can mount this NFS export to a drive letter so I know the network is reachable. Both the windows machine and FOG client are on the same VLAN.
Is fog trying to mount the image to a local /image path on the client?
Thanks!!!
mmethe -
Have you updated
/etc/fstaband/etc/exportsappropriately? If you’re doing mount commands on-the-fly, those don’t stick around after a reboot. -
@mmethe said:
192.168.232.248:/san_images/dev/ on /images failed: Network is unreachable
Is this IP on the same subnet? The error message is quite common in network terms and usually means that a client is meant to talk to another machine that is in a different subnet and does not have a proper default gateway/route set. Please make sure the client is getting correct IP settings via DHCP. For example schedule a debug job and run
ip a sandroute -nwhen you get to the shell on the client. Please post a picture here. -
@mmethe I launched a debug job at the target. Initially the machine gets to fog and drops to a console. It then appears to lose its network config as the only adapter listed by ‘ip a s’ is the loopback adapter. I have tried this from both the subnet local to the fog server as other VLANS and the same thing happens.
Does this sound like a target computer NIC driver issue? I am using the most recent kernel listed on the kernel updates page.
Thanks!
-
@mmethe sounds like the second round of DHCP isn’t working, do you have portfast turned on?
-
@Wayne-Workman Yes, portfast is enabled on this port.
This is the ONLY model PC this is happening with. I am leaning toward a kernel/driver issue I think. It is an HP ProDesk 600 G2 with an Intel NIC. Where can I get the most recent kernel build?
Thanks for all the help so far!
-
@Wayne-Workman Also, if DHCP was failing would ‘ip a s’ still list the eth without an IP? There is nothing but loopback listed as 127.0.0.1
-
@mmethe not sure on the last question, but you can follow this guide to get the latest kernels:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_UpdateIt’s written for fog trunk, but the steps in 1.2.0 are similar.
-
@Wayne-Workman Thank You. the problem I am seeing is that the most updated kernel is dated July 22, 2015. Seems a little old. Is there a repository where I can look for something more current than a year ago?
-
@mmethe FOG Trunk comes with the latest kernels, your problem might go away.
-
@Wayne-Workman So, I am using the SVN method to switch to trunk. All goes well until I am told to hot the GUI and do the schema update. When I hit the GUI URL I get:
SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘hosts.hostPending’ in ‘where clause’ SQL: [94] SELECT COUNT(
hosts.hostID) AStotalFROMhostsWHEREhosts.hostPending=‘1’ LIMIT 1 Params: 0SQL is running. There were no errors reported during the installation script execution.
Thanks!!
-
@mmethe Ok. @Tom-Elliott ideas?
-
Please update to latest and see if this issue is corrected for. I love prepared statements, but they can be a PITA as well.
I was able to fix the other thread that had the issue. I commented the lines that were causing the offending issues.
I’ve made a more appropriate fix in the latest and just have not got a good way to test it currently.
-
@Wayne-Workman Can I simply obtain the most current kernel somehow and point to it?
-
@mmethe when you run the fog trunk installer, it downloads the very latest kernels and inits for you. If this didn’t happen, you’d get a big fat failure message telling you about it during installation. Right now you have a different issue, and tom suggested updating to fix that, which will likely fix it.
-
@mmethe said in NFS Mount Fails... Network Unreachable:
@Wayne-Workman So, I am using the SVN method to switch to trunk. All goes well until I am told to hot the GUI and do the schema update. When I hit the GUI URL I get:
SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘hosts.hostPending’ in ‘where clause’ SQL: [94] SELECT COUNT(
hosts.hostID) AStotalFROMhostsWHEREhosts.hostPending=‘1’ LIMIT 1 Params: 0SQL is running. There were no errors reported during the installation script execution.
Thanks!!
Cross linking similar threads:
https://forums.fogproject.org/topic/7855/sql-error-when-upgrading-database-schema
https://forums.fogproject.org/topic/7873/sql-error-after-updating-to-trunk-at-login
https://forums.fogproject.org/topic/7870/chromium-os-woes/9
https://forums.fogproject.org/topic/7862/nfs-mount-fails-network-unreachable/16
-
This should now be fixed.
