Services.conf has this stanza.
apply Service "apt" {
check_command = "apt"
vars.apt_upgrade = false
command_endpoint = host.vars.client_endpoint
assign where host.vars.do_apt
}
A typical barely sanitized entry in hosts.conf doing the apt check is:
object Host "xxxx.example.com" {
check_command = "hostalive"
address = "xxx.example.com"
vars.client_endpoint = name
vars.do_apt = true
vars.syslog_ng_cnt = true;
vars.notification["mail"] = {
users = [ "jpenny" ]
}
}
I have monitoring-plugins-basic installed, and check_apt is part of that
package.
So, I think that I am using the icinga2 checker. I am definitely not using
nrpe,
it is not installed on any of the systems. There are no authorized_keys on
master, so I can't be suing ssh.
There is nothing remotely interesting in /var/log/icinga2/icinga2.log.
On host xxx, a failing system, grepping for xxx gives only two lines:
[2022-07-07 12:50:55 -0400] information/JsonRpcConnection: Received certificate
request for CN 'xxx.example.com' signed by our CA.
[2022-07-07 12:50:55 -0400] information/JsonRpcConnection: The certificate for
CN 'xxx.example.com' is valid and uptodate. Skipping automated renewal.
I hope that this is enough information to reproduce the problem.
Also, I have grepped source for "apt-get false upgrade", but I don't find that
string.
________________________________
From: Sebastiaan Couwenberg <sebas...@xs4all.nl>
Sent: Thursday, July 7, 2022 3:19 PM
To: Jim Penny <jimpe...@ykk.com>; 1014...@bugs.debian.org
<1014...@bugs.debian.org>
Subject: Re: [Pkg-nagios-devel] Bug#1014551: icinga2: check_apt not working if
both master and host are running 2.13.4-1
Control: tags -1 moreinfo
On 7/7/22 20:37, Jim Penny wrote:
> It works with master on 2.13.4-1 and hosts on 2.13.3-1+b2. If both are on
> 2.13.4-1, icinga2-web reports "'/usr/bin/apt-get false upgrade' exited with
> non-zero status.".
How do you execute check_apt on the hosts?
Do you use the icinga2 checker feature to run check_apt on the hosts or
check_by_ssh, NRPE, or something else?
In case of icinga2 checker feature, what does
/var/log/icinga2/icinga2.log contain?
How can your issue be reproduced?
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
