Univention Bugzilla – Bug 22700
nfsmounts sollte Erreichbarkeit des NFS Server vor dem mount prüfen
Last modified: 2020-07-03 20:51:37 CEST
Über /usr/lib/univention-directory-policy/nfsmounts (per /etc/cron.d/univention-directory-policy gestartet) werden NFS Shares in der /etc/fstab ergänzt und gemountet. Wenn nun der NFS Server nicht erreichbar ist, hängt dieser mount Befehl. Durch Cron wird das Skript nach gewisser Zeit auch wieder gestartet und somit sammeln sich diese Aufrufe in der Prozessliste. -> ps aux | grep nfsmount |wc -l 153 Vor dem mount sollte zumindest geprüft werden, ob der NFS Server überhaupt erreichbar ist.
Die vielen nfsmount Prozesse führen u.a. zu: -> top 13:18:31 up 36 days, 4:38, 3 users, load average: 201.46, 166.79, 156.41
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
mentioned here: 2017072121000261
/usr/lib/univention-directory-policy/nfsmounts forks "mount" processes for each mount, but does not wait for them. As such the are re-parented to init when that intermediate process terminates. In my test the "mount.nfs" times out after some time (but there can be situations, were they don't) This is another case of Bug #39824
(In reply to Philipp Hahn from comment #4) > This is another case of Bug #39824 and more specifically of Bug #29219
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.