Bug 31573 - Nagios check cannot read notifier_id on a memberserver
Nagios check cannot read notifier_id on a memberserver
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: Philipp Hahn
Depends on: 41261
  Show dependency treegraph
Reported: 2013-05-29 18:51 CEST by Dirk Ahrnke
Modified: 2017-04-24 11:45 CEST (History)
7 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.034
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017011821000331 2014090521000178 2014101521002369 20141015210023 2015021721000719 2015031021000159
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Ahrnke 2013-05-29 18:51:10 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.
Comment 1 Lutz Willek 2014-07-02 11:15:20 CEST
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
Comment 2 Janis Meybohm univentionstaff 2014-09-09 10:17:52 CEST
Ticket#: 2014090521000178

Observed again after a rejoin of a DC-Backup (UCS 3.2-3 e185)
Comment 3 Tim Petersen univentionstaff 2014-10-22 17:47:18 CEST
Again at 2014101521002369
Comment 4 Tim Petersen univentionstaff 2014-10-22 17:47:35 CEST
(In reply to Tim Petersen from comment #3)
> Again at 20141015210023

After rejoin
Comment 5 Tim Petersen univentionstaff 2015-02-18 07:14:27 CET
Comment 6 Tim Petersen univentionstaff 2015-02-18 07:15:14 CET
(In reply to Tim Petersen from comment #5)
> 2015021721000719

reported on a 4.0 memberserver and backup
Comment 7 Janis Meybohm univentionstaff 2015-03-10 11:05:14 CET
Hit a customer again:
Comment 9 Dirk Ahrnke 2016-01-14 16:41:37 CET
Comment 10 Philipp Hahn univentionstaff 2017-04-24 11:45:48 CEST
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