[Bug 1216148] New: monitoring-plugins, check_load is broken ("Error opening")
https://bugzilla.suse.com/show_bug.cgi?id=1216148 Bug ID: 1216148 Summary: monitoring-plugins, check_load is broken ("Error opening") Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: jgonzalez@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870104 --> https://bugzilla.suse.com/attachment.cgi?id=870104&action=edit Packages updated on 2023-10-11 Until the updated that got applied on openSUSE MicroOS last night, `/usr/lib/nagios/plugins/check_load -r -w 15,10,05 -c 30,25,20` worked fine. But since that update: microos:/var/log/zypp # /usr/lib/nagios/plugins/check_load -r -w 15,10,05 -c 30,25,20 CRITICAL - You need more args!!! Error opening I am not sure where the problem is, I see `monitoring-plugins-load` got updated, but the last changelog entry is from 2022, so I'd assume this was the result of some kind of mass rebuild (as the update as big, see the attached log with all the packages that got installed/updated). Last change on the package happened 1 year ago, according to https://build.opensuse.org/package/show/openSUSE:Factory/monitoring-plugins Seems Fedora had a bug that caused the same output years ago: https://bugzilla.redhat.com/show_bug.cgi?id=1470823, but it seems it got fixed by bumping their package to a 2018 commit based on 2.2.1 (https://src.fedoraproject.org/rpms/nagios-plugins/c/97402353898e984baebc50ad...), so I'd say this is maybe not related. I reviewed apparmor changelogs, but could not see anything relevant either. Checking check_load's code, I'd say this is the line causing this: https://github.com/nagios-plugins/nagios-plugins/blob/master/plugins/check_l... But the fact that CRITICAL error about args is showing confuses me. Checking https://github.com/nagios-plugins/nagios-plugins/blob/bade01b453b012af8c7120..., I see `PATH_TO_UPTIME` is... well, basically seems to be the path to the `uptime` binary, that I can find and it works: microos:/var/log/zypp # which uptime /usr/bin/uptime microos:/var/log/zypp # uptime 17:31:47 up 13:01, 2 users, load average: 0.04, 0.01, 0.00 And given I am executing check_load as root and uptime has rights 755... I don't think this is a problem with the permissions. Can't see anything on any logs. I am out of ideas, so happy to debug a bit more if someone can provide a hint :-) -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com