Bug 45186 – UNIVENTION_NSCD NRPE: Unable to read output

Bug 45186 - UNIVENTION_NSCD NRPE: Unable to read output


Summary:	UNIVENTION_NSCD NRPE: Unable to read output

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Monitoring (Prometheus or Nagios)
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.2-1-errata
Assigned To:	Felix Botner
QA Contact:	Jürn Brodersen

URL:
Keywords:

Depends on:	42812
Blocks:	45187
	Show dependency tree / graph

Reported:	2017-08-11 11:10 CEST by Stefan Gohmann
Modified:	2017-08-11 15:28 CEST (History)
CC List:	9 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.137
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017081021000093 2017081121000313
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2017-08-11 11:10:25 CEST

After updating to errata 129, we received several customer reports with the nagios message: UNIVENTION_NSCD NRPE: Unable to read output



+++ This bug was initially created as a clone of Bug #42812 +++

After installing a docker appbox app, the Nagios check for nscd shows a warning:

[1447873023] SERVICE NOTIFICATION: root@localhost;master411.deadlock41.intranet;UNIVENTION_NSCD;WARNING;notify-service-by-email;PROCS WARNING: 5 processes with command name nscd

root@master411:~# ps aufwx 
[...]
root     11342  0.0  1.5 186176 15916 ?        Sl   15:04   0:06 /usr/bin/docker -d -p /var/run/docker.pid --storage-driver=overlay --bip=172.17.42.1/16
root     11474  0.0  0.1  10676  1408 ?        Ss   15:04   0:00  \_ init [2]  
[...]
root     16614  0.0  0.1  99312  1832 ?        Ssl  15:05   0:00  |   \_ /usr/sbin/nscd
root     16628  0.0  0.1  10460  1488 ?        Ss   15:05   0:00  |   \_ /usr/sbin/inetd
daemon   16698  0.0  0.0  16684   144 ?        Ss   15:05   0:00  |   \_ /usr/sbin/atd
root     16720  0.0  0.1  10484  1640 ?        Ss   15:05   0:00  |   \_ /usr/sbin/cron
[...]

Comment 1 Felix Botner

2017-08-11 12:41:10 CEST

Server:
* Reverted changes for UNIVENTION_NSCD during this update (JOIN_VERSION==5)
  not updated hosts can continue to use this service
* Always add new UNIVENTION_NSCD2

Client:
* Add host to UNIVENTION_NSCD and UNIVENTION_NSCD2 (only is the exists)
* If host is in UNIVENTION_NSCD2 and in UNIVENTION_NSCD, remove host from
  UNIVENTION_NSCD

Added Bug #45187 for 4.2-2 "cleanup".

univention-nagios 10.0.1-7A~4.2.0.201708111206 errata4.2-1

Comment 2 Jürn Brodersen

2017-08-11 14:26:56 CEST

Looks good :)
What I tested:
with broken master:
  update master first -> UNIVENTION_NSCD on member is green again -> OK
    now update member -> member uses UNIVENTION_NSCD2 -> OK
  update member first -> member uses UNIVENTION_NSCD2 -> OK

with master that had the broken update not yet applied:
  update master and "jump" over broken package -> UNIVENTION_NSCD2 is used -> OK

YAML -> OK

-> Verified

Comment 3 Erik Damrose

2017-08-11 15:28:05 CEST

<http://errata.software-univention.de/ucs/4.2/133.html>