Bug#863864: release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)

[Johannes Ranke]

Package: release-notes
Severity: normal

I assume that switching to icinga is possible, but I am missing a hint in the
release notes. Will icinga use nagios configuration files?


-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
(x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

[Alexander Wirt]

Post by Johannes Ranke
Package: release-notes
Severity: normal
I assume that switching to icinga is possible, but I am missing a hint in the
release notes. Will icinga use nagios configuration files?

No, and those files are not fully compatible.

You will have to do a manual migration.

Alex

[Bas Couwenberg]

Post by Johannes Ranke
I assume that switching to icinga is possible, but I am missing a hint in the
release notes. Will icinga use nagios configuration files?

Icinga 1.x uses the same configuration syntax as Nagios 3.x, so
switching from Nagios 3 to Icinga 1 should be as simple as copying the
configuration files to the appropriate directory (/etc/icinga/objects).

Icinga 2.x uses a different configuration syntax and migratie to it from
Nagios 3.x is more involved.

Kind Regards,

Bas

[Baptiste Jammet]

Control: tags -1 moreinfo

Hello all,

Post by Alexander Wirt
No, and those files are not fully compatible.
Icinga 1.x uses the same configuration syntax as Nagios 3.x, so
switching from Nagios 3 to Icinga 1 should be as simple as copying the
configuration files to the appropriate directory
(/etc/icinga/objects).

Could you provide some text we will include in the release notes ?
And since there is 2 different answers (and I know nothing about Nagios
nor incinga), ideally find a shared answer/solution !

Thanks

Baptiste

[Johannes Ranke]

Post by Baptiste Jammet
Control: tags -1 moreinfo
Hello all,

Post by Alexander Wirt
No, and those files are not fully compatible.
Icinga 1.x uses the same configuration syntax as Nagios 3.x, so
switching from Nagios 3 to Icinga 1 should be as simple as copying the
configuration files to the appropriate directory
(/etc/icinga/objects).

Could you provide some text we will include in the release notes ?
And since there is 2 different answers (and I know nothing about Nagios
nor incinga), ideally find a shared answer/solution !
Thanks
Baptiste

I just would like to add that I had a dangling symlink in /etc/apache2/conf-
enabled/nagios3.conf after the upgrade, keeping apache2 from starting.
Should I file a bug against the jessie package of nagios3?

The good news is that I was indeed able to easily migrate from nagios3 from
jessie to icinga1.x from stretch by copying the contents of /etc/nagios3 and
/etc/nagios3/conf.d that I had modified over to /etc/icinga and /etc/icinga/
objects, plus some renaming of files named *_nagios2.cfg to *_icinga.cfg.

Cheers,

Johannes

[Debian Bug Tracking System]

tags -1 moreinfo

Bug #863864 [release-notes] release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)
Added tag(s) moreinfo.

[Debian Bug Tracking System]

Your message dated Fri, 09 Jun 2017 22:16:00 +0000
with message-id <59851a39-fa0e-8ced-7cf6-***@thykier.net>
and subject line Re: Bug#863864: [Pkg-nagios-devel] Bug#863864: release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)
has caused the Debian Bug report #863864,
regarding release-notes: Document that nagios is not in stretch and how to switch to icinga (if that is possible)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)