Hello
After i have upgraded to centos 4.4 i have a problem during the boot with NFS, CentOS can't mount NFS shares:
Oct 2 11:47:28 s2 mount: mount: mount to NFS server '192.168.140.13' failed: Oct 2 11:47:28 s2 mount: System Error: No route to host. Oct 2 11:47:34 s2 mount: mount: mount to NFS server '192.168.140.13' failed: Oct 2 11:47:34 s2 mount: System Error: No route to host. Oct 2 11:47:40 s2 mount: mount: mount to NFS server '192.168.140.13' failed: Oct 2 11:47:40 s2 mount: System Error: No route to host. Oct 2 11:47:40 s2 netfs: Mounting NFS filesystems: failed Oct 2 11:47:40 s2 netfs: Mounting other filesystems: succeeded
This CentOS is only a client NFS. If i run "/etc/init.d/netfs start" shares are mount regolary.
It can't be a network problem, the only one changes i have made to this server is upgrade from 4.3 to 4.4.
Why this? Thanks
Alessio Cecchi wrote:
Oct 2 11:47:28 s2 mount: mount: mount to NFS server '192.168.140.13' failed: Oct 2 11:47:28 s2 mount: System Error: No route to host.
[...]
It can't be a network problem, the only one changes i have made to this server is upgrade from 4.3 to 4.4.
But it looks like a network problem to me. You seem to be trying to mount the shares *before* the network is up and the NFS server is reachable.
Cheers,
Ralph
Il giorno lun, 02/10/2006 alle 14.52 +0200, Ralph Angenendt ha scritto:
Alessio Cecchi wrote:
Oct 2 11:47:28 s2 mount: mount: mount to NFS server '192.168.140.13' failed: Oct 2 11:47:28 s2 mount: System Error: No route to host.
[...]
It can't be a network problem, the only one changes i have made to this server is upgrade from 4.3 to 4.4.
But it looks like a network problem to me. You seem to be trying to mount the shares *before* the network is up and the NFS server is reachable.
No because in the runlevel the network is up before that netfs start:
S10network -> ../init.d/network ... S25netfs -> ../init.d/netfs
I can see also during the boot process on the screen, network start first.
Thanks
Alessio Cecchi wrote:
Il giorno lun, 02/10/2006 alle 14.52 +0200, Ralph Angenendt ha scritto:
Alessio Cecchi wrote:
Oct 2 11:47:28 s2 mount: System Error: No route to host.
But it looks like a network problem to me. You seem to be trying to mount the shares *before* the network is up and the NFS server is reachable.
No because in the runlevel the network is up before that netfs start:
S10network -> ../init.d/network ... S25netfs -> ../init.d/netfs
I can see also during the boot process on the screen, network start first.
Some iptables rules acting up? No idea what else it could be - the no route to host just screams for non-availability of the network.
Ralph
Il giorno lun, 02/10/2006 alle 15.32 +0200, Ralph Angenendt ha scritto:
Alessio Cecchi wrote:
Il giorno lun, 02/10/2006 alle 14.52 +0200, Ralph Angenendt ha scritto:
Alessio Cecchi wrote:
Oct 2 11:47:28 s2 mount: System Error: No route to host.
But it looks like a network problem to me. You seem to be trying to mount the shares *before* the network is up and the NFS server is reachable.
No because in the runlevel the network is up before that netfs start:
S10network -> ../init.d/network ... S25netfs -> ../init.d/netfs
I can see also during the boot process on the screen, network start first.
Some iptables rules acting up? No idea what else it could be - the no route to host just screams for non-availability of the network.
Thanks Ralph, but i have made all possible test:
iptables is stop network is available set a sleep before to run netfs...
The NFS is in the same network(mask).
Thanks
-
Alessio Cecchi -
Ralph Angenendt