Mandriva Linux Archives: cooker@mandrivalinux.org

Mandriva Linux: cooker@mandrivalinux.org


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

  • From: Udo Rader
  • Subject: Re: [Cooker] [nfs] not all shares exported
  • Date: 6 Feb 2007 14:41:32 -0000

On Tue, 2007-02-06 at 15:02 +0100, Fabrice FACORAT wrote:
> Le mardi 6 février 2007, Udo Rader a écrit :
> > Hi,
> >
> > I am not sure if this is a leftover from some failed update/upgrade run
> > or a bug, so please help me solve this:
> >
> > on some box the /etc/exports file looks like this:
> > ---------CUT--------
> > #
> > /usr/src *.example.com(ro,async,no_subtree_check)
> > /usr/bestsolution athene.example.com(rw,sync,no_subtree_check)
> > /home/udo/wa/local-3.2 athene.example.com(rw,sync,subtree_check)
> > ---------CUT--------
> >
> > now if I freshly boot the box, showmount gets me this:
> >
> > ---------CUT--------
> > % showmount -e localhost
> > Export list for localhost:
> > /usr/src *.example.com
> > ---------CUT--------
> >
> > Obviously only the first export is shown here (and accessible).
> >
> > During bootup I see this when the nfs service is started:
> > ---------CUT--------
> > Starting NFS services:  exportfs: athene.example.com has non-inet addr
> > exportfs: athene.example.com has non-inet addr
> > exportfs: athene.example.com has non-inet addr
> > exportfs: athene.example.com has non-inet addr
> > ---------CUT--------
> >
> > So this looks like name resolution would not work at the time the nfs
> > service is started, but AFAIS, the network has already been started
> > before (network-up is rc5.d/S-1network-up, network is rc5.d/S10network
> > and nfs is rc5.d/S60nfs)
> >
> > BTW, why is network-up defined as "S-1network-up"? Never saw this
> > before ...
> >
> > Any ideas?
> 
> fix your initscripts :
> chkconfig --del network-up
> chkconfig --add network-up

OK, that gave me 

S50resolvconf
S51network
S52network-up
S60nfs

now. But that does not change anything else or fix my problem.

> Be sure to have latest packages ( initscripts, resolvconf, ... )

as recent as can be:

---------CUT--------
% rpm -q initscripts resolvconf
initscripts-8.48-8mdv2007.1
resolvconf-1.37-3mdv2007.1
---------CUT--------

But after digging a bit deeper, I found this:

---------CUT--------
% ls --full-time /etc/resolv.conf 
-rw-r--r-- 2 root root 222 2007-02-06 15:15:21.706332226
+0100 /etc/resolv.conf
---------CUT--------

So resolv.conf was last modified on 15:15:21

however, /var/log/syslog logs the "host has non-inet addr" on 15:15:15

---------CUT--------
Feb  6 15:15:15 yamm exportfs[2310]: athene.example.com has non-inet
addr
---------CUT--------

This looks like exportfs was querying for athene.example.com on 15:15:15
before resolver information was present (15:15:21) and thus fails.

So this looks like exportfs does not wait until resolver information is
available.

Maybe a prcsys/init script issue?

-- 
Udo Rader

bestsolution.at EDV Systemhaus GmbH
http://www.bestsolution.at

Attachment: signature.asc
Description: This is a digitally signed message part



Date Index | Thread Index

Search the archive:



To (un)subscribe from/to the lists:

Sympa mailing lists server.





Fund the Mandriva Linux project

Looking for a job?