Remote check execution doesn't work, even though locally it does

Hello everyone,

I have an Icinga 2 master running with multiple agents. I’ve set up a custom check command that checks if a windows service is runnning or not. Some times, I get a critical even though the service is running. If I run the check script locally, the result is a success. However, as soon as I restart the Icinga2 Agent Service, the check works as usual again.

I have already tried changing the Property “Log on as” in the Icinga 2 service properties to “Local System Account” (it was Network Service before), without any success.

Does anyone have previous experience with this issue or any idea, where to the issue could be?

  • Version used: r2.11.2-1
  • Operating System: Debian 9
  • Enabled features: api checker debuglog ido-mysql mainlog
  • Icinga Web 2 version and modules: 2.7.3, [director, doc, incubator, ipl, jira, monitoring,reactbundle]
  • Config validation:
    [2022-10-07 16:57:36 +0200] information/cli: Icinga application loader (version: r2.11.2-1) [2022-10-07 16:57:36 +0200] information/cli: Loading configuration file(s). [2022-10-07 16:57:37 +0200] information/ConfigItem: Committing config item(s). [2022-10-07 16:57:37 +0200] information/ApiListener: My API identity: Icinga2Master [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 2 FileLoggers. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 IcingaApplication. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 CheckerComponent. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 3 Zones. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 Endpoint. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 ApiUser. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 ApiListener. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 1 IdoMysqlConnection. [2022-10-07 16:57:37 +0200] information/ConfigItem: Instantiated 235 CheckCommands. [2022-10-07 16:57:37 +0200] information/ScriptGlobal: Dumping variables to file '/var/cache/icinga2/icinga2.vars' [2022-10-07 16:57:37 +0200] information/cli: Finished validating the configuration file(s).

does any other check behaves like that? maybe the problem is the check script, but it’s difficult to evaluate without the content.

I don’t think the check is the problem, because I have it deployed on multiple other servers where it works without any issues.