Bug 8985

Summary:	nagios-check_* packages cause nagios to fail to start with errors eg Error: Could not add object property in file '/etc/nagios/plugins.d/check_ping.cfg' on line 4.
Product:	Mageia	Reporter:	claire robinson <eeeemail>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	Normal	CC:	stormi-mageia
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	nagios	CVE:
Status comment:

Description claire robinson 2013-02-07 14:35:38 CET

See also bug 8799

Installing eg. nagios-check_ssh causes it to restart the nagios daemon which
then fails to restart.

nagios[17462]: Warning: Duplicate definition found for command 'check_ssh'
(config file '/etc/nagios/plugins.d/check_ssh.cfg', starting on line 3)

Same for others tested such as nagios-check_http

nagios: Warning: Duplicate definition found for command 'check_http' (config
file '/etc/nagios/plugins.d/check_http.cfg', starting on line 3)
nagios: Error: Could not add object property in file
'/etc/nagios/plugins.d/check_http.cfg' on line 4.

After installing task-nagios

Running nagios -v /etc/nagios/nagios.cfg shows ...

Warning: Duplicate definition found for command 'check_ping' (config file
'/etc/nagios/plugins.d/check_ping.cfg', starting on line 3)
Error: Could not add object property in file
'/etc/nagios/plugins.d/check_ping.cfg' on line 4.
   Error processing object config files!

It's necessary to remove the following files to get the -v option to not show errors.
-rw-r--r-- 1 root root  456 Mar 29  2012 check_dhcp.cfg
-rw-r--r-- 1 root root  211 Mar 29  2012 check_hpjd.cfg
-rw-r--r-- 1 root root 2403 Mar 29  2012 check_http.cfg
-rw-r--r-- 1 root root  253 Mar 29  2012 check_nt.cfg
-rw-r--r-- 1 root root 2210 Mar 29  2012 check_ping.cfg
-rw-r--r-- 1 root root  201 Mar 29  2012 check_smtp.cfg
-rw-r--r-- 1 root root  460 Mar 29  2012 check_ssh.cfg
-rw-r--r-- 1 root root 3607 Mar 29  2012 check_tcp.cfg

Comment 1 claire robinson 2013-02-07 14:41:03 CET

See also bug 8986 which may be related.

Comment 2 Guillaume Rousse 2013-02-07 21:24:57 CET

That's just a default configuration issue, easily fixable on user side, which isn't worth an update. I just fixed it in cauldron by removing commands definition in default configuration.

Status: NEW => RESOLVED
CC: (none) => guillomovitch
Resolution: (none) => FIXED

Comment 3 claire robinson 2013-02-07 22:21:13 CET

Packages are expected to work out of the box without having to correct issues
like this.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 4 Guillaume Rousse 2013-02-07 22:38:45 CET

This problem has never been reported since this package exist in mandrake. Which means than either no ones uses this package, or rather than anyone using it is perfectly able to fix it himself.

Anyway, the actual issue is just about the interest of pushing an update to the stable release, and I repeat that's not worth the effort for me. Feel free to do it yourself, there is no acces restriction on the subversion repository.

CC: guillomovitch => (none)

Comment 5 Samuel Verschelde 2013-08-29 16:40:20 CEST

Closing, there's little hope there will be an update for Mageia 2, and it's fixed in Mageia 3.

Status: REOPENED => RESOLVED
CC: (none) => stormi
Resolution: (none) => FIXED

Comment 6 Samuel Verschelde 2013-08-29 16:40:46 CEST

fixing status

Resolution: FIXED => WONTFIX