Icinga2 from stretch-backports

Meta Icinga
1

I am running a Debian system which has to stay at Stretch for now and I want to install an icinga2 as client. As it should/has to be the same version as the master I wanted to use stretch-backports. Unfortunately I’m not able to do this as apt exits with an error:

$ apt install icinga2 -t stretch-backports
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 icinga2 : Depends: icinga2-bin (= 2.6.0-2+deb9u1) but it is not going to be installed
           Depends: icinga2-common (= 2.6.0-2+deb9u1) but 2.10.3-2~bpo9+1 is to be installed
E: Unable to correct problems, you have held broken packages.

These are my sources:

$ cat /etc/apt/sources.list
deb http://ftp.debian.org/debian stretch main contrib non-free
deb http://ftp.debian.org/debian/ stretch-updates main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb http://apt.osmc.tv stretch main
deb http://ftp.debian.org/debian stretch-backports main contrib non-free

What am I doing wrong?

2

I am running a Debian system which has to stay at Stretch for now

Just out of interest, why?

and I want to install an icinga2 as client. As it should/has to be the same
version as the master I wanted to use stretch-backports.

That’ll be far too old - in fact anything in the standard Debian
repositories will be too old.

These are my sources:

$ cat /etc/apt/sources.list
deb http://ftp.debian.org/debian stretch main contrib non-free
deb http://ftp.debian.org/debian/ stretch-updates main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb http://apt.osmc.tv stretch main
deb http://ftp.debian.org/debian stretch-backports main contrib

non-free

What am I doing wrong?

You’re not following the Icinga installation instructions :slight_smile:

https://icinga.com/docs/icinga2/latest/doc/02-installation/

Regards,

Antony.

3

Hi Antony,

the RasPi is running the OSMC distro to always start into Kodi. Still I want to monitor it, and it’s not OSMC’s priority to upgrade to Buster :frowning:

Thanks for your quick answer! :slight_smile: So I am upgrading to 2.11 with your packages now.

On caveat that I stumbled upon: I am checking my router to filter some DNS responses like “facebook.com.” and answer them with NXDOMAIN. The 2.11 dns check command doesn’t support this anymore. When looking into this I noticed that the service definition and my monitoring-plugins are now out of sync (they are version 2.2-6 on the Buster system):

Check command:

    "-n" = {
        set_if = "$dns_accept_cname$"
        description = "Optionally accept cname responses as a valid result to a query. The default is to ignore cname responses as part of the result"
    }

check_dns help:

 -n, --expect-nxdomain
    Expect the DNS server to return NXDOMAIN (i.e. the domain was not found)
    Cannot be used together with -a

Perhaps you should also ship the latest monitoring-plugins etc. you are defining the commands for?

4

Hi Antony,

the RasPi is running the OSMC distro to always start
into Kodi. Still I want to monitor it, and it’s not OSMC’s priority to
upgrade to Buster :frowning:

Ah, okay.

Thanks for your quick answer! :slight_smile: So I am upgrading to 2.11 with your
packages now.

Well, they’re not my packages - they’re just the official packages from the
Icinga developers.

I noticed that the service definition and my monitoring-plugins are now out
of sync (they are version 2.2-6 on the Buster system):

Perhaps you should also ship the latest monitoring-plugins etc. you are
defining the commands for?

Note that “you” in that sentence doesn’t refer to me :slight_smile:

I am nothing to do with Icinga development - I’m just a user here helping
others become as experienced as I am, and learning from those who are more
experienced :slight_smile:

Antony.

5

I’ll pick up on the you then, from the “official” Icinga side :slight_smile:
I’m forwarding this conversation over to the developers, who also deal with the packaging usually.
Have a nice day!
Feu

6

Hi,

@Pooh: Thank you for this really quick community support :slight_smile: Now almost everything is running nicely
@theFeu: Thank you too! :slight_smile:

1 Like
7

Oh well, I just noticed that my master (now running v2.11) looses the connection to the new agent on stretch repeatedly. Now I learned that for raspbian stretch there is only icinga 2.11 available, and obviosly that’s not compatible with the icinga for buster :frowning:
Is there a chance that 2.11 is made available here, too?

8

Please could be a little more explicit about exactly which versions you are
running on which machines? Saying “the icinga for buster” doesn’t tell us
which version you’re referring to, for example.

Also, bear in mind that Icinga:

a) supports Master version >= Satellite version >= Agent version

b) but only where the difference at each stage is no greater than 1 release.

Regards,

Antony.

9

I’m gonna assume you meant 2.10 there. That should still be compatible with your 2.11 master.

It currently doesn’t look like we’re gonna build packages for Raspbian Stretch again, because we had a lot of problems with GCC on there.

10

I’m gonna assume you meant 2.10 there

True, I mixed things up :slight_smile:
My master (“Izzie”) is running on a Raspbian Buster: r2.11.4-1
The agent (“Grey”) is running on a Raspbian Stretch: r2.10.5-1

a) supports Master version >= Satellite version >= Agent version
b) but only where the difference at each stage is no greater than 1 release.

That’s interesting! So my constellation should work. With debug logging enabled I found this message on the master’s log:

[2020-06-25 20:18:48 +0200] notice/JsonRpcConnection: Error while reading JSON-RPC message for identity 'Grey.pi.lan': Error: stream truncated
    (0) icinga2: icinga::NetString::ReadStringFromStream(std::shared_ptr<icinga::AsioTlsStream> const&, boost::asio::basic_yield_context<boost::asio::executor_binder<void (*)(), boost::asio::executor> >, int) (+0x324) [0x5ce784]
    (1) icinga2: icinga::JsonRpc::ReadMessage(std::shared_ptr<icinga::AsioTlsStream> const&, boost::asio::basic_yield_context<boost::asio::executor_binder<void (*)(), boost::asio::executor> >, int) (+0x40) [0x4ac43c]
    (2) icinga2: icinga::JsonRpcConnection::HandleIncomingMessages(boost::asio::basic_yield_context<boost::asio::executor_binder<void (*)(), boost::asio::executor> >) (+0xc8) [0x4be2c0]
    (3) /usr/lib/arm-linux-gnueabihf/icinga2/sbin/icinga2() [0x4a1a48]
    (4) /usr/lib/arm-linux-gnueabihf/icinga2/sbin/icinga2() [0x4780e0]
[2020-06-25 20:18:48 +0200] warning/JsonRpcConnection: API client disconnected for identity 'Grey.pi.lan'
11

Sounds a lot like this: https://github.com/Icinga/icinga2/issues/7533
But that issue was resolved.