I do have exported file systems.
NFS starts but stops randomly.
Main Topics
Browse All TopicsHi,
I use a HP DL320S with openfiler 2.2 (on rpath linux) to make backups of a Vmware ESX server.
The VMs are exported to a NFS share mounted on the ESX host.
However, the process fails after a while and I noticed it's because rpc.mountd is not running anymore thus making the share inaccessible.
# service nfs status
Shutting down NFS mountd: rpc.mountd is stopped
nfsd (pid 4315 4314 4313 4312 4311 4310 4309 4308) is running...
rpc.rquotad (pid 4302) is running...
Any help will be appreciated (linux n00b here)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You may see /var/log/messages for any reasons why rpc.mountd.
What seems strange to me is, why the command:
# service nfs status
Shutting down NFS mountd: rpc.mountd is stopped
results to stopping rpc.mountd. Such message is usually printed when we do service 'stop'. In your case it seems that 'status' command shuts down rpc.mountd. Try to _not_ run this command (as root). May be your rpc.mountd will be alive.
Also try to find core files after possible rpc.mountd crash.
It's possible you are being hacked, there where vulnerabilities in rpc.mountd, for example read here: http://www.securityfocus.c
What OS/version are you using, how often do you perform software updates?
It's part of the startup script:
status)
[ -x /usr/sbin/rpc.svcgssd ] && /sbin/service rpcsvcgssd status
echo -n $"Shutting down NFS mountd: "
status rpc.mountd
status nfsd
It's not shutting down mountd. The echo statement is wrong.
OS is openfiler 2.2 appliance (based on rpath) with the latest patches.
I don't see anything interesting in /var/log/messages :(
Probably it's a bug either in OS or in rpc.mountd. Without any info about why mountd is stopped we may only guess.
If you wish, you may try to debug this service yourself (for example to run 'strace -f -o /tmp/logfile rpc.mountd') or you may try to find your problem in support forum or to subscribe to support mailing list here: http://www.rpath.org/rbuil
I viewed mailing list for last year and didn't find why your problem occurs.
Probably I found your question there: http://www.openfiler.com/c
without any answer (as many other questions on this forum). But there are more details in that post:
*** glibc detected *** double free or corruption (!prev): 0x00000000005209a0 ***
Aborted
So it's a 100% bug, but not sure I'm in what library/software.
What about commercial support, I didn't read their agreement, but most probably they will not help you with a bug in a 3rd party software (even GNU rpc.mountd). It _may_ be a result of a compilation problem (suppose they use gcc 4.x to create openfiler distribution) so they may fix it. Or it may be a bug in a glibc (there where a fixed in november 2006 bug: glibc 264884 globfree() double-frees). So I suggest you to ask a question in a 'distribution' forum and recommend the developers to upgrade glibc package. Typically it's a paintfull upgrade and that's why your glibc (openfiler 2.2 distribution glibc) may be obsolete and have this bug.
Also I found one advice to run 'export MALLOC_CHECK_=1' or 'MALLOC_CHECK_=0' before starting rpc.mountd (try either 1 or 0 on failure and run rpc.mountd directly from command line, not with a 'service' script).
Another advice - write a small 'monitor' script that will check every 1 second for rpc.mountd. If it's not running - restart it again. This may be a workaround for a short time until this problem will be fixed by developers of the openfiler distro.
Business Accounts
Answer for Membership
by: NopiusPosted on 2007-07-17 at 01:26:40ID: 19502997
Mountd doesn't start if you have no exported filesystems.
To export FS you should edit /etc/exports (man exports), then run 'exportfs -a' and only then you may run mountd:
/usr/sbin/rpc.mountd