Univention Bugzilla – Bug 46559
Too many nrpe processes during the UCS 4.3 upgrade
Last modified: 2018-06-21 08:34:28 CEST
I've updated my DC master to UCS 4.3. On my backup, slave and member server, I see a lot of running nrpe processes during the upgrade. root@backup422:~# date Di 6. Mär 07:34:19 CET 2018 root@backup422:~# ps -ef | grep nrp nagios 1688 1 9 07:25 ? 00:00:47 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 1775 1 9 07:25 ? 00:00:46 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 2180 1 0 06:29 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 7050 1 6 07:26 ? 00:00:27 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 7070 1 5 07:26 ? 00:00:26 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 7092 1 5 07:27 ? 00:00:25 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 7526 1 5 07:27 ? 00:00:22 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 9028 1 4 07:27 ? 00:00:18 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 9405 1 4 07:27 ? 00:00:17 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 9802 1 4 07:28 ? 00:00:17 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 10682 1 4 07:28 ? 00:00:15 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 11530 1 3 07:28 ? 00:00:12 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 11537 1 3 07:28 ? 00:00:12 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 11544 1 3 07:28 ? 00:00:12 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 11551 1 3 07:29 ? 00:00:12 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 12564 1 3 07:29 ? 00:00:09 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 12637 1 3 07:29 ? 00:00:09 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 12639 1 3 07:29 ? 00:00:08 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 12661 1 3 07:29 ? 00:00:08 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 12814 1 3 07:30 ? 00:00:08 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 14737 1 2 07:30 ? 00:00:06 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 14739 1 2 07:30 ? 00:00:06 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 14795 1 2 07:31 ? 00:00:06 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 14895 1 2 07:31 ? 00:00:04 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 14969 1 2 07:31 ? 00:00:04 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15313 1 2 07:31 ? 00:00:04 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15543 1 2 07:31 ? 00:00:03 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15546 1 2 07:31 ? 00:00:03 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15552 1 2 07:31 ? 00:00:03 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15561 1 2 07:31 ? 00:00:03 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15984 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15988 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 15997 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16028 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16031 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16043 1 2 07:32 ? 00:00:02 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16758 1 2 07:33 ? 00:00:01 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16765 1 2 07:33 ? 00:00:01 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16787 1 2 07:33 ? 00:00:01 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16793 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16799 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16825 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16827 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16834 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d nagios 16838 1 2 07:33 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d root 16915 5404 0 07:34 pts/0 00:00:00 grep nrp root@backup422:~# root@backup422:~# uptime 07:37:44 up 11:47, 1 user, load average: 60,77, 39,84, 19,12 root@backup422:~#
root@backup422:~# /etc/init.d/nagios-nrpe-server status | less ● nagios-nrpe-server.service - LSB: Start/Stop the Nagios remote plugin execution daemon Loaded: loaded (/etc/init.d/nagios-nrpe-server; generated; vendor preset: enabled) Active: active (running) since Sat 2017-05-27 02:04:48 CEST; 9 months 9 days ago Docs: man:systemd-sysv-generator(8) Main PID: 2180 (nrpe) CGroup: /system.slice/nagios-nrpe-server.service ├─ 1688 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 1775 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 2180 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 7050 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 7070 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 7092 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 7526 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d ├─ 9028 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d [...] ├─18219 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d └─18349 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -d Mär 06 07:21:45 backup422 nrpe[8461]: Error: Request packet type/version was invalid! Mär 06 07:21:45 backup422 nrpe[8461]: Client request was invalid, bailing out... Mär 06 07:21:57 backup422 nrpe[8482]: Error: Request packet type/version was invalid! Mär 06 07:21:57 backup422 nrpe[8482]: Client request was invalid, bailing out... Mär 06 07:22:41 backup422 nrpe[8537]: Error: Request packet type/version was invalid! Mär 06 07:22:41 backup422 nrpe[8537]: Client request was invalid, bailing out... Mär 06 07:23:25 backup422 nrpe[8614]: Error: Request packet type/version was invalid! Mär 06 07:23:25 backup422 nrpe[8614]: Client request was invalid, bailing out... Mär 06 07:23:57 backup422 nrpe[10431]: Error: Request packet type/version was invalid! Mär 06 07:23:57 backup422 nrpe[10431]: Client request was invalid, bailing out...
On my test systems, it works if I simply stop the nrpe daemon before starting the 4.3 upgrade. I think we should add this to the preup script.
[4.3-0 158c940ba6] * Stop nrpe daemon before starting the upgrade to UCS 4.3 (Bug #46559) The daemon is started automatically during the upgrade.
OK - updater
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".