Created attachment 3490 [details] Screenshot See also bug 8799 Bug 8985 and bug 8986 are probably related. Every service on localhost shows as failed with reason (Return code of 127 is out of bounds - plugin may be missing) # service nagios status nagios.service - LSB: Starts and stops the Nagios monitor. Loaded: loaded (/etc/rc.d/init.d/nagios) Active: active (running) since Thu, 07 Feb 2013 13:51:06 +0000; 5min ago Process: 13382 ExecStart=/etc/rc.d/init.d/nagios start (code=exited, status=0/SUCCESS) Main PID: 13398 (nagios) CGroup: name=systemd:/system/nagios.service รข 13398 nagios -d /etc/nagios/nagios.cfg
Misconfiguration issue, not packaging error. Fixed in cauldron.
Status: NEW => RESOLVEDCC: (none) => guillomovitchResolution: (none) => FIXED
Packages are expected to work out of the box without having to correct issues like this.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
CC: guillomovitch => (none)
If it's fixed in cauldron, why not provide an update to Mageia 2?
Keywords: (none) => TriagedCC: (none) => stormiAssignee: bugsquad => guillomovitchSource RPM: (none) => nagios
Because it's a non-issue, only happening with default configuration shipped for demonstration purposes. That's not worth the overhead of a software update, at least for me. Now, feel free to take care of it, I couldn't care less.
Assignee: guillomovitch => bugsquad
Closing like the other 2 nagios default configuration issues then.
Status: REOPENED => RESOLVEDVersion: 2 => CauldronResolution: (none) => FIXED