...
Please run the following commands to check the state of the agent controller and the port states:
For Linux
Code Block |
---|
|
ss -tulpn | grep 6556
ps waux | grep cmk-agent-ctl
cmk-agent-ctl status
systemctl status check-mk-agent.socket
systemctl status cmk-agent-ctl-daemon.service |
For Windows
Code Block |
---|
|
netsh interface ipv4 show excludedportrange protocol=tcp |
Solution
For Linux
If the registration is good, but cmk-agent-ctl cannot be started. This might be a bug.
You might then switch to xinetd mode:
Code Block |
---|
|
apt install xinetd |
Disable the systemd services:
Code Block |
---|
|
systemctl stop check-mk-agent.socket
systemctl disable check-mk-agent.socket
systemctl stop cmk-agent-ctl-daemon.service
systemctl disable cmk-agent-ctl-daemon.service |
Install the xinetd service:
Code Block |
---|
|
/var/lib/cmk-agent/scripts/super-server/1_xinetd/setup deploy
/var/lib/cmk-agent/scripts/super-server/1_xinetd/setup trigger |
Disable TLS registration on the CMK Server: Properties of host → menu → entry Host → Remove TLS registration
Afterwards ss should show xinetd claiming the connection
Code Block |
---|
|
ss
systemctl status check-mk-agent.socket |
Related articles
Filter by label (Content by label) |
---|
showLabels | false |
---|
max | 5 |
---|
spaces | KB |
---|
showSpace | false |
---|
sort | modified |
---|
reverse | true |
---|
type | page |
---|
cql | label in ("agent","agent_controller") and type = "page" and space = "KB" |
---|
labels | agent agent_controller |
---|
|
...