Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-31-2009, 10:02 AM
|
#1
|
|
LQ Newbie
Registered: Mar 2004
Distribution: Ubuntu 6.06.1
Posts: 8
Rep:
|
NFS share in fstab fails to mount, but where is the log?
Hello.
I have two RHEL 5 systems, one has an NFS export and the other has that share listed in its fstab file. The client system should be trying to mount the NFS share upon bootup, correct?
It seems the last time the client system was restarted the NFS share didn't mount - however I don't see anything in /var/log/messages about it. I was able to mount the share manually.
I'm not as concerned at the moment about the fact that the share didn't mount automatically as much as I am concerned about the fact that I can't seem to find any log entries about the failure. Where should such failures appear? Or are they not logged by default??
Thanks!
|
|
|
|
07-31-2009, 10:18 AM
|
#2
|
|
LQ 5k Club
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian Squeeze (server), Slackware 13.37 (netbook), Slackware64 14.0 (desktop),
Posts: 8,357
|
Hello gumpish
There might be something in the /var/log boot log file.
Best
Charles
|
|
|
|
08-01-2009, 10:26 PM
|
#3
|
|
LQ Newbie
Registered: Mar 2004
Distribution: Ubuntu 6.06.1
Posts: 8
Original Poster
Rep:
|
Nope, the /var/log/boot file for the time period in question is empty...
|
|
|
|
08-02-2009, 11:40 AM
|
#4
|
|
Senior Member
Registered: Oct 2003
Location: Bonaire
Distribution: Debian Lenny/Squeeze/Wheezy/Sid
Posts: 3,799
|
Since I assume the server was running at the time of the reconnection attempt, you should check /var/log/messages in the server. Those messages provide more information than the client's.
Most of the times when an NFS share doesn't mount (which usuall does) is because of a network issue. For example because the reverse DNS wasn't working (yet).
jlinkels
|
|
|
|
08-02-2009, 12:05 PM
|
#5
|
|
LQ 5k Club
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian Squeeze (server), Slackware 13.37 (netbook), Slackware64 14.0 (desktop),
Posts: 8,357
|
Hello gumpish
I write from an ubuntian perspective so you may need to translate into RedHatish.
Check that network, portmap and nfs-common init scripts are called before mountall.sh; if they are not, the only thing that makes NFS mounts in /etc/fstab work at all is that NFS keeps trying long enough for the network to come up later.
One possible cause of the network coming up slowly is switches which may queue certain types of packets (I say "certain" because I'm not certain which!). I've seen similar threads in which the solution has been to re-configure Cisco switches.
There may be timeouts available on the NFS options in /etc/fstab which you could extend.
Another solution may be to remove the NFS entries from /etc/fstab and to program their mounting into a later init script like rc.local.
Best
Charles
|
|
|
|
08-02-2009, 12:08 PM
|
#6
|
|
LQ 5k Club
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian Squeeze (server), Slackware 13.37 (netbook), Slackware64 14.0 (desktop),
Posts: 8,357
|
Another thought; you may be able to solve/improve the situation by using IP addresses rather than names when specifying the NFS mounts in the fstab or, if you really want names, using the hosts file rather than a DNS server for name resolution. This way you are not dependent on network facilities to get the IP address of the NFS server.
|
|
|
|
08-19-2009, 03:45 PM
|
#7
|
|
LQ Newbie
Registered: Jun 2009
Location: Rochester, NY, USA
Posts: 9
Rep:
|
look in /var/logs/secure?
You might want to look in /var/logs/secure. RHEL 5 writes a bunch of messages there which I would have otherwise looked for in /var/logs/messages. I think that's because it's 'security enabled' SELinux.
|
|
|
|
08-19-2009, 07:22 PM
|
#8
|
|
Guru
Registered: Aug 2004
Location: Brisbane
Distribution: Centos 6.4, Centos 5.9
Posts: 15,021
|
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 06:07 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|