PDA

View Full Version : problem with NFS while shutting down



naughtysriram
10th March 2009, 09:42 AM
I am running f10 i386 arch on my box,

Whenever I shutdown my comp I see the message "Failed" in red for "NFS Services", nothing is wrong while boot up, everything is perfect!

Maybe I guess there is a problem with the updates I did. As I dont have a speedy internet connection so I do the updates manually using yum/yumex for most of the programs, instead of using the "Update System" program from the "System->Administration" menu. I have not figured out what the problem is, yet.

Thanks in advance.

notageek
10th March 2009, 09:46 AM
Usually when you notice such anomalies, the best thing to do would be to search logs. In this case /var/log/messages.

This is a particularly verbose log file, which stores information on various dates therefore the best thing to do would be to "grep".

eg:


# grep -i nfs /var/log/messages
# grep "Mar 9 12:1" /var/log/messages

The second example lets you search all logs on March 9th at 12th hour.

naughtysriram
10th March 2009, 09:59 AM
This is the output that I get when I enter,

$ sudo grep -i nfs /var/log/messages

Mar 8 18:20:14 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 8 18:30:14 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 8 18:30:14 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 8 18:30:14 localhost kernel: NFSD: starting 90-second grace period
Mar 8 23:37:23 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 8 23:38:24 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 8 23:38:24 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 8 23:38:24 localhost kernel: NFSD: starting 90-second grace period
Mar 9 03:16:04 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 9 15:13:17 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 9 15:13:17 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 9 15:13:17 localhost kernel: NFSD: starting 90-second grace period
Mar 9 19:32:22 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 9 20:11:30 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 9 20:11:30 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 9 20:11:30 localhost kernel: NFSD: starting 90-second grace period
Mar 9 20:13:41 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 9 20:56:14 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 9 20:56:14 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 9 20:56:14 localhost kernel: NFSD: starting 90-second grace period
Mar 9 22:00:49 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 9 22:05:20 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 9 22:05:20 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 9 22:05:20 localhost kernel: NFSD: starting 90-second grace period
Mar 10 01:10:56 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 10 14:01:35 localhost kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Mar 10 14:01:35 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 10 14:01:35 localhost kernel: NFSD: starting 90-second grace period

notageek
10th March 2009, 10:03 AM
I don't see anything wrong with the logs, maybe someone with better experience can help.

Are you running a NFS server from your box? Please post /etc/exports

naughtysriram
10th March 2009, 01:01 PM
The file(/etc/exports) is empty, and I am not running NFS server, although I have installed it from the Install Media disk.

notageek
10th March 2009, 01:06 PM
Then you don't need this service running. Turn it off with the following command, although I admit this doesn't specifically resolve your question.


# chkconfig nfs off

Perhaps its due to the update. Have you manually stopped and started it?

# service nfs restart
or

# service nfs stop
# service nfs start
While you stop and start you may also check this on a different terminal window

# tail -f /var/log/messages

naughtysriram
10th March 2009, 01:40 PM
This is what I got now...

# service nfs restart
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS services: [FAILED]
Starting NFS services: [ OK ]
Starting NFS quotas: rpc.rquotad: Cannot bind to given address: Address already in use
[ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]

then...

# tail /var/log/messages

Mar 10 18:04:43 localhost kernel: NFSD: starting 90-second grace period
Mar 10 18:05:02 localhost mountd[4426]: Caught signal 15, un-registering and exiting.
Mar 10 18:05:03 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 10 18:05:07 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 10 18:05:07 localhost kernel: NFSD: starting 90-second grace period
Mar 10 18:06:59 localhost pulseaudio[3461]: module-alsa-sink.c: Increasing wakeup watermark to 188.03 ms
Mar 10 18:07:26 localhost mountd[4506]: Caught signal 15, un-registering and exiting.
Mar 10 18:07:27 localhost kernel: nfsd: last server has exited, flushing export cache
Mar 10 18:07:27 localhost kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 10 18:07:27 localhost kernel: NFSD: starting 90-second grace period

notageek
10th March 2009, 02:46 PM
Can you check if "portmap" service is on? (ls /etc/init.d/portmap*)

Based on the name of the service returned, check its status here

# service portmap status

BTW, since you're not using NFS server you can turn off this service.

notageek
10th March 2009, 02:52 PM
...and the command was

"tail -f /var/log/messages"

naughtysriram
10th March 2009, 03:18 PM
there is no service named as portmap... but a portreserve runs ... i did a

# ls /etc/init.d/
acpid firstboot mdmonitor pcscd smolt
anacron functions messagebus portreserve snmpd
atd gpm microcode_ctl preload snmptrapd
auditd haldaemon multipathd psacct squid
avahi-daemon halt mysqld qemu sshd
backuppc hsqldb netconsole racoon tor
blktapctrl httpd netfs rdisc udev-post
bluetooth ip6tables netplugd restorecond winbind
btseed iptables network rpcbind wine
bttrack irda NetworkManager rpcgssd wpa_supplicant
capi irqbalance nfs rpcidmapd xenconsoled
cpuspeed iscsi nfslock rpcsvcgssd xend
crond iscsid nmb rsyslog xendomains
cups isdn nscd saslauthd xenner
cups-config-daemon kerneloops ntpd sendmail xenstored
dc_client killall ntpdate setroubleshoot ypbind
dc_server libvirtd nvidia smartd zvbid
dnsmasq lm_sensors openvpn smb

notageek
10th March 2009, 03:23 PM
Then this is the service that must be running: rpcbind

If this still fails, then I'm afraid I wouldn't know why NFS service is failing.

sonoran
12th March 2009, 06:33 AM
I have gotten that same red NFS services "failed" line on shutdown
since I installed Fedora 10, but I never noticed that it was causing
any kind of problem.

My advice - ignore it. (On the theory that "If it ain't broke..."):)