Univention Bugzilla – Bug 31573
Nagios check cannot read notifier_id on a memberserver
Last modified: 2017-04-24 11:45:48 CEST
A fresh installation of a member server, installed with 3.1-0, upgraded to 3.1-1 errata 112 shows the following error in Nagios after joining the system: CRITICAL: no change of listener transaction id for last 10 checks (nid=8571 lid=cat: /var/lib/univention-directory-listener/notifier_id: Permission denied) Filepermissions are 600, all other systems have 644.
same after a fresh installation of a ucs 3.2-2 errata128 (Borgfeld) member server: root@dc1337-01:~# stat /var/lib/univention-directory-listener/notifier_id File: „/var/lib/univention-directory-listener/notifier_id“ Size: 4 Blocks: 8 IO Block: 4096 reguläre Datei Device: fe00h/65024d Inode: 135676 Links: 1 Access: (0600/-rw-------) Uid: ( 105/listener) Gid: (65534/ nogroup) Access: 2014-07-01 16:22:46.676481744 +0200 Modify: 2014-07-01 22:00:35.137225590 +0200 Change: 2014-07-01 22:00:35.137225590 +0200
Ticket#: 2014090521000178 Observed again after a rejoin of a DC-Backup (UCS 3.2-3 e185)
Again at 2014101521002369
(In reply to Tim Petersen from comment #3) > Again at 20141015210023 After rejoin
2015021721000719
(In reply to Tim Petersen from comment #5) > 2015021721000719 reported on a 4.0 memberserver and backup
Hit a customer again: 2015031021000159
new mentions in http://forum.univention.de/viewtopic.php?f=48&t=3893&p=14033#p14033 http://forum.univention.de/viewtopic.php?f=56&t=3871&p=14059#p14059
http://forum.univention.de/viewtopic.php?t=4767
The bug could happen when UDL was started the first time with a umask like 0077. This most likely happend during installation in the chroot environment, where this often are initialized differently. With Bug #41261 fixed the file /var/lib/univention-directory-listener/notifier_id is now created newly and renamed after each transaction; thus the file now has the correct permissions since UCS-4.1-2 errata