so you just learned something very valuable, that Linux needs to be rebooted too to clead up after it's self. despite what you may hear it needs it more often than you think, especaily if it is doig something other than just sitting there. chris At 01:50 PM 2/14/00 -0500, you wrote: > >Hey all sorry for the long post, > >I had to do something I really didn't want to do this weekend. I >had to reboot my server because of NFS. This is a little 486 that >runs NFS, Apache, dhcpd, named, and all the other normal services, >along with being my internet dialup server and IP MASQ server. >This system has been running without a single problem since last >August (of course it only serves my 2 home computers so it >doesn't really get a heavy load). > >At any rate, something strange happened to NFS, that was keeping >me from mounting any file systems on my other machines. So I >telneted in (on account of it not having a monitor) and figured >I could probably just stop the nfs services and restart them. >I stopped and started them via the /etc/rc.d/init.d/nfs script. >When it tried to restart nfs, it complained that the address was >already in use. I looked up the ports via netstat, and there >was nothing unusual. I figured it was something >to do with rpc. So I went hog wild, and stoped the nfs services, >and the portmaper, and unloaded all the kernel modules relating >to NFS (nfsd lockd sunrpc), figuring that would definitely do it > ... nope. Same stupid error after starting everything back up >(I even tried waiting for about 12 hours between start and stop). > >The error it was printing was: > > nfssvc: Address already in use > >I also checked the output of rpcinfo -p, but that did not >indicate that there were any nfs services mapped at all. >Only the rpc.nfsd actually had problems starting, the mountd >and lock stuff started without an incident. Anybody know >How I could have further debugged the problem? or maybe >what the problem could have been? > > >Here's contents from /var/log/messages for the nfs shutdown: > >Feb 10 10:57:49 firewall nfs: Shutting down NFS services: succeeded >Feb 10 10:57:54 firewall mountd[414]: Caught signal 15, un-registering and exiting. >Feb 10 10:58:00 firewall nfs: rpc.mountd shutdown succeeded >Feb 10 10:58:17 firewall kernel: nfsd: terminating on signal 9 >Feb 10 10:58:17 firewall last message repeated 7 times >Feb 10 10:58:17 firewall kernel: nfsd: last server exiting >Feb 10 10:58:17 firewall kernel: exp_do_unexport: 08:11 last use, flushing cache >Feb 10 10:58:17 firewall kernel: svc: server socket destroy delayed >Feb 10 10:58:20 firewall nfs: nfsd shutdown succeeded >Feb 10 10:58:30 firewall nfs: rpc.rquotad shutdown succeeded >Feb 10 10:58:34 firewall rpc.statd[392]: Caught signal 15, un-registering and exiting. >Feb 10 10:58:40 firewall nfs: rpc.statd shutdown succeeded > >And the subsequent start: > >Feb 10 10:59:07 firewall nfs: Starting NFS services: succeeded >Feb 10 10:59:12 firewall rpc.statd[13495]: gethostbyname error for firewall.local.domain >Feb 10 10:59:12 firewall nfs: rpc.statd startup succeeded >Feb 10 10:59:18 firewall nfs: rpc.rquotad startup succeeded >Feb 10 10:59:23 firewall nfs: rpc.mountd startup succeeded >Feb 10 10:59:28 firewall rpc.nfsd: nfssvc: Address already in use >Feb 10 10:59:28 firewall nfs: rpc.nfsd startup failed >Feb 10 10:59:43 firewall mountd[13517]: export request from 192.168.1.101 >Feb 10 10:59:56 firewall mountd[13517]: authenticated mount request from sublime.linux.bogus:826 >Feb 10 11:00:17 firewall kernel: exp_do_unexport: 08:11 last use, flushing cache >Feb 10 11:00:17 firewall nfs: Starting NFS services: succeeded >Feb 10 11:00:33 firewall rpc.nfsd: nfssvc: Address already in use >Feb 10 11:00:33 firewall nfs: rpc.nfsd startup failed > >Anybody got any Ideas? > >-Matt > >-- >Matthew W. Herbert x75764 >Spectrum Advanced Applications >http://www.aprisma.com/ >mailto:[EMAIL PROTECTED] > >********************************************************** >To unsubscribe from this list, send mail to >[EMAIL PROTECTED] with the following text in the >*body* (*not* the subject line) of the letter: >unsubscribe gnhlug >********************************************************** > > ********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************
