Getting error on agent monitoring on checkmk raw-ubuntu 20.04

Troubleshooting
1

Hi All,

I have installed the checkmk agent on Microsoft Exchange server, But when I added to the host and tested the connection, I am getting below error messages on agent:

API Error:Your request timed out after 110 seconds. This issue may be related to a local configuration problem or a request which works with a too large number of objects. But if you think this issue is a bug, please send a crash report.

Best Regards,
Sharaf

2

Is the firewall configured correctly on your target Exchange server to allow connections on the port 6556?

3

i can telnet to the port 6556.

4

Can you show the configuration of your Exchange from the monitoring server?

cmk -D HOSTNAME

here the lines starting with

Agent mode: 
Type of agent:

are relevant.
If you think this configuration is right you can do a

cmk --debug -vvI HOSTNAME

The messages here depends on the used CMK version. But if you get an error message the complete message would be good to know.

5

Hi,

Sorry for the delay. Please see the output below:
OMD[hsmcc]:~$ cmk -D mailsrv2

mailsrv2
Addresses: 192.168.3.3
Tags: [address_family:ip-v4-only], [agent:cmk-agent], [criticality:prod], [ip-v4:ip-v4], [networking:lan], [piggyback:auto-piggyback], [site:hsmcc], [snmp_ds:no-snmp], [tcp:tcp]
Labels:
Host groups: check_mk
Contact groups: all, Servers, check-mk-notify, SuperAdmin
Agent mode: Normal Checkmk agent, or special agent if configured
Type of agent:
TCP: 192.168.3.3:6556
Process piggyback data from /omd/sites/hsmcc/tmp/check_mk/piggyback/mailsrv2
Services:
checktype item params description groups

OMD[hsmcc]:~$

OMD[hsmcc]:~$ cmk --debug -vvI mailsrv2
Discovering services and host labels on: mailsrv2
mailsrv2:

  • FETCHING DATA
    Source: SourceType.HOST/FetcherType.TCP
    [cpu_tracking] Start [7f20858a6fd0]
    Connecting via TCP to 192.168.3.3:6556 (5.0s timeout)
    [TCPFetcher] Fetch with cache settings: DefaultAgentFileCache(path=PosixPath(’/omd/sites/hsmcc/tmp/check_mk/cache/mailsrv2’), max_age=0, disabled=False, use_outdated=False, simulation=False), Cache enabled: True
    Not using cache (Does not exist)
    [TCPFetcher] Execute data source
    Reading data from agent

After this noting happening. Its taking too long to complete. I terminated the service and i got below error:

Closing TCP connection to 192.168.3.3:6556
[cpu_tracking] Stop [7f20858a6fd0 - Snapshot(process=posix.times_result(user=0.0, system=0.0, children_user=0.0, children_system=0.0, elapsed=306.25))]

6

This is a firewall issue on your target machine or in between.
Please check if the connection on 6556 is allowed on the target machine.
If you do a “telnet 192.168.3.3 6556” you should also see the agent output.

7

Dear Andreas,

telnet is working fine.

OMD[hsmcc]:~$ telnet 192.168.3.3 6556
Trying 192.168.3.3…
Connected to 192.168.3.3.
Escape character is ‘^]’.

8

That

That is not working - what happens after the line “Escape character…”?

9

Connection is established

OMD[hsmcc]:~$ telnet 192.168.3.3 6556
Trying 192.168.3.3…
Connected to 192.168.3.3.
Escape character is ‘^]’.
^]
telnet>

10

You see no output - that means the connection is not established.
I don’t know what answers your connection on the other side but it is no CMK agent.

Sample connection to 6556 looks like this

telnet 192.168.188.77 6556
Trying 192.168.188.77...
Connected to 192.168.188.77.
Escape character is '^]'.
<<<check_mk>>>
Version: 2.0.0p1
BuildDate: Mar 16 2021
AgentOS: windows

followed by a huge amount of text

1 Like
11

Dear Andreas,

I can see the output you have mentioned from other servers and switches. Only this particular server, i am experiencing this issue. Any idea where to check?

12

try on the “Agent” Server,

telnet localhost 6556

If that work check the firewall.

see also the output of ss -ntlp check the 6556 port.

13

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.