<Original post below> Hi agn, and thanks to all who replied - got the first replies 5 minutes after my posting, :-) I delayed the summary, since I did want to see if the daemon survives the night - well, it did, so, here's the solution: There was a script running at 4 o'clock, searching for coredumps, .bak-files, etc. This script starts its search in the root-dir, and descends into every dir. It seems the automountd doesn't likes this, :-) So, I deactivated the script, and voila - the daemon runs stable! Now, I only have to figure out why the script crashes - I had it running for abt. 2 years, without any problems. Hm... Maybe I should stop automountd before starting the script, wait until it's finished, and start the daemon again. Special thanks to Casper Dik, who pointed me in the right direction, and Mark Cain, Francois Legal, Rajeev Jain and Tom Crummey for helpful hints! Have a nice hackin', Harald ============================================ Harald Husemann Systems Engineer Teammanager Unix administration and Configuration Management Materna Gmbh - Vo_kuhle 37 - D-44141 Dortmund, Germany Phone: +49-231-5599-8684 Mobile: +49-179-2300651 Hi Gurus, we're having a BIG problem here: In the last two nights, our complete network has failed. We're using NIS, with one NIS-Master and a slave, and NFS to mount the home-dirs. It seems that every night at 4 o' clock the automountd on all servers stops, and we're unable to restart it. The following is a screenshot of what happens when I try to restart the automountd: ========================/snip/================== Last login: Tue May 6 10:23:26 2003 Sun Microsystems Inc. SunOS 5.8 Generic February 2000 Sun Microsystems Inc. SunOS 5.8 Generic February 2000 You have mail. # bash bash-2.03# /usr/lib/autofs/automountd -T -v bash-2.03# t1 READDIR REQUEST : -xfn/_x500 @ 100000 bash-2.03# ps -ef | grep auto root 9774 9729 0 10:29:31 pts/1 0:00 grep auto bash-2.03# ====================/snap/======================================== As it shows, the automountd does a readdir request to an xfn-dir - and that's it, its gone... The content of our /etc/auto_master is: ========================/snip/================================= # Master map for automounter # +auto_master /net -hosts -nosuid,nobrowse /home_nfs auto_home -nobrowse /xfn -xfn =========================/snap/================================ I've commented out both the /home_nfs and the /xfn entry, but without success - same behaviour, the daemon starts, and fails a few seconds later with the above message. When I reboot the machines, the automountd comes up and runs - until 4 o' clock... (There are some cronjobs, e.g. a quota-checker running at 4 o' clock - but I can't imagine that this is the problem...) Any ideas?? Hope someone can help us, since it's a real severe problem which blocks our complete network... Thanks, and have a nice hackin', Harald ============================================ Harald Husemann Systems Engineer Teammanager Unix administration and Configuration Management Materna Gmbh - Vo_kuhle 37 - D-44141 Dortmund, Germany Phone: +49-231-5599-8684 Mobile: +49-179-2300651 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed May 7 07:05:21 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:10 EST