Setup agent node without connecting to the master

Icinga 2
21

This now led me down the problem of there being no debug log: apparently that is a known error in windows (https://community.icinga.com/t/windows-agent-enable-debug-log/5735)

[2021-10-13 15:45:27 +0200] information/FileLogger: 'debug-file' started.
[2021-10-13 15:45:27 +0200] information/FileLogger: 'main-log' started.
[2021-10-13 15:45:27 +0200] information/ApiListener: 'api' started.
[2021-10-13 15:45:27 +0200] information/ApiListener: Started new listener on '[::]:5665'
[2021-10-13 15:45:27 +0200] debug/ApiListener: Not connecting to Endpoint 'xxx' because that's us.
[2021-10-13 15:45:27 +0200] debug/ApiListener: Not connecting to Endpoint 'xx' because the host/port attributes are missing.
[2021-10-13 15:45:27 +0200] notice/ApiListener: Current zone master: xxx
[2021-10-13 15:45:27 +0200] notice/ApiListener: Connected endpoints: 
[2021-10-13 15:45:27 +0200] information/ConfigItem: Activated all objects.
[2021-10-13 15:45:27 +0200] notice/ApiListener: Updating object authority for objects at endpoint 'xxx'.
[2021-10-13 15:45:27 +0200] debug/IcingaApplication: In IcingaApplication::Main()
[2021-10-13 15:45:37 +0200] information/WorkQueue: #4 (ApiListener, RelayQueue) items: 0, rate:  0/s (0/min 0/5min 0/15min);
[2021-10-13 15:45:37 +0200] information/WorkQueue: #5 (ApiListener, SyncQueue) items: 0, rate:  0/s (0/min 0/5min 0/15min);
[2021-10-13 15:45:37 +0200] debug/ApiListener: Not connecting to Endpoint 'xxx' because that's us.
[2021-10-13 15:45:37 +0200] notice/ApiListener: Updating object authority for objects at endpoint 'xxx'.
[2021-10-13 15:45:37 +0200] debug/ApiListener: Not connecting to Endpoint 'xx' because the host/port attributes are missing.
[2021-10-13 15:45:37 +0200] notice/ApiListener: Current zone master: xxx
[2021-10-13 15:45:37 +0200] notice/ApiListener: Connected endpoints: 
[2021-10-13 15:45:47 +0200] notice/ApiListener: Updating object authority for objects at endpoint 'xxx'.
22

It’s not a windows error but an error caused by the old powershell module as found out here.

23

I was on vacation last week, but now im back and the problem still exists for one host.
Is there maybe something that can be gathered from the debuglog?

24

Is there noone that can maybe understand the debug log? I really dont know why this host isnt working.

25

Anyone, please? I really need to find a solution, because this probably wont be the last host with this problem.

26

Typical reasons:

  • Firewall on agent
  • date/time out of range

BTW: This thread is marked as solved. Maybe that’s the reason why no one is answering.

27

That might explain it :slight_smile:

The firewall doesn’t seem to be the issue, the port is open.
How could i see if date/time are out of range? The time and date is the same on the master and the host if thats what you mean.

28

The date/time deviation between master and agent must no be too much.

Another reason might be: API is not enabled

29

Oh ok. Like i said time and date are the same on both systems.
API is also enabled

30

Any hints in the logs?

32

I’ve posted the host’s log here earlier. I cant gather anything useful from there, but maybe you can?
The master log is even less useful, it just says that it cant connect.