HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Automounter is hung up
Operating System - HP-UX
1832955
Members
2763
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 06:50 AM
03-20-2001 06:50 AM
HP-UX 11.0 automounter has caused a problem and I can't "ls -l /" - it's complaining, saying "NFS server (pid585@/net) not responding still trying". I have tried killing all the NFS daemons, rpc.lockd, etc using /sbin/init.d/nfs.core,client, and server. I have seen this before and fixed by rebooting. Anyone know how to fix without rebooting?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 07:36 AM
03-20-2001 07:36 AM
Solution
Greg,
Does ps -ef |grep 585 show process ID 585 still running? If not, you have to reboot.
If there is an automount PID 585 running, then
send a SIGUSR2 (kill -17 585) to see if anything shows up in /var/adm/automount.log
If that does not wake up the automounter, most like a reboot is in order.
As an FYI, the automount process "fakes out" the kernel into its process as managing the automount points, emulating an NFS Server. In this case, it is the /net indirect "-hosts" map. If the process "goes away" without the kernel being told to close out the Virtual Filesystem mountpoint, then any process that tries to access that mountpoint will block (sleep) forever, since the process is no longer there to answer the request.
Hope this helps,
-> Brian Hackley
Does ps -ef |grep 585 show process ID 585 still running? If not, you have to reboot.
If there is an automount PID 585 running, then
send a SIGUSR2 (kill -17 585) to see if anything shows up in /var/adm/automount.log
If that does not wake up the automounter, most like a reboot is in order.
As an FYI, the automount process "fakes out" the kernel into its process as managing the automount points, emulating an NFS Server. In this case, it is the /net indirect "-hosts" map. If the process "goes away" without the kernel being told to close out the Virtual Filesystem mountpoint, then any process that tries to access that mountpoint will block (sleep) forever, since the process is no longer there to answer the request.
Hope this helps,
-> Brian Hackley
Ask me about telecommuting!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 07:41 AM
03-20-2001 07:41 AM
Re: Automounter is hung up
Yes, the automounter has been restarted, so the PID is no longer 585. This answers my question, although it's not what I wanted to hear. I wonder what the effect would be if I could get automount to start again at PID 585?.... just out of curiosity.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP