search

Icinga / icinga-core

Icinga 1.x, the old core (EOL 31.12.2018)
GNU General Public License v2.0
45 stars 27 forks source link

[dev.icinga.com #11593] Icinga Classic w/ NagiosBackend: Sorry, command expander only available using Icinga 1.x #1579

Closed icinga-migration closed 8 years ago

icinga-migration commented 8 years ago

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11593

Created by Flingo on 2016-04-14 10:25:18 +00:00

Assignee: (none) Status: Rejected (closed on 2016-06-21 21:30:16 +00:00) Target Version: (none) Last Update: 2016-06-21 21:30:16 +00:00 (in Redmine)

Icinga Version: 1.12.0
OS Version: Centos 6

When using Icinga Classic UI 1.12.0 with a Nagios 3.5.0 Backend (e.g. OMD 1.30) I get an error when I try to use the Command Expander:

"Sorry, command expander only available using Icinga 1.x"

The Command Expander worked fine in Icinga 1.11.4 w/ Nagios 3.5.0 (e.g. OMD 1.20)

This seems to be related to the fix mentioned here [[https://lists.icinga.org/pipermail/icinga-checkins/2014-June/030612.html]]

icinga-migration commented 8 years ago

Updated by mfriedrich on 2016-04-14 14:32:13 +00:00

Well, using Nagios Core and Icinga Classic UI sounds a bit creepy. I would rather switch the monitoring core to Icinga entirely. I also don't like to idea to just add version "3" making that work again, since we might have icinga3 in some years (and if it still exposes status.dat it will again break).

If one comes up with a sensible patch, I'll apply it. Hint: config.c and display_command_expansion()

icinga-migration commented 8 years ago

Updated by Flingo on 2016-04-15 09:44:38 +00:00

dnsmichi wrote:

Well, using Nagios Core and Icinga Classic UI sounds a bit creepy. I would rather switch the monitoring core to Icinga entirely.

Changing the core to Icinga worked for me!

icinga-migration commented 8 years ago

Updated by ricardo on 2016-06-21 21:30:16 +00:00

Problem solved.