CentOS - Oct 2006 - Problem with NFS mount after upgrade to 4.4

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
-- 
Ralph Angenendt......ra at br-online.de | .."Text processing has made it
possible
Bayerischer Rundfunk...80300 M?nchen | ....to right-justify any idea, even one
Programmbereich.Bayern 3, Jugend und | .which cannot be justified on any other
Multimedia.........Tl:089.5900.16023 | ..........grounds." -- J. Finnegan,
USC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos/attachments/20061002/52881c6a/attachment-0003.sig>

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 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).
How about a simple sanity check in the startup script?

    ping -c 4 192.168.140.13

Put that in before you attempt to mount the filesystem to make sure
there aren't network problems.

-- 
Bowie