Hi Guys,
Due to reasons I wont get into - I have over 100 hosts running Debian 6 (Please don't stop reading - they are in the process of being eliminated, this is part of that project) - but I need to keep an eye on these guys for a while still.
Digging through old packages, I found the 2.2.9 agent that works on Debian 6. I read around here, and confirmed that this agent should work with Zabbix 6 - https://www.zabbix.com/forum/zabbix-...ts-and-servers
I am testing this on one host to start with. I have the Zabbix Server up and running - it seems quite happy.
We are getting issues with the connectivity between the agent and the server. I have been assured that the firewall is open between the two hosts when testing. The network engineer who is managing this side of things assured me he troubleshot with the appropriate firewall rules in place. Due to security, these rules have now been removed, but can be put back in place as needed (all traffic between the two hosts are allowed when these rules are in place)
In the /var/log/zabbix/zabbix_server.log file - I see something of much interest (I am changing the IP (192.168.0.10) and zabbix server hostname (zabbix-master) for sake of company policy):
*************************
root@zabbix-master:/etc/apparmor.d# grep 192.168.0.10 /var/log/zabbix/zabbix_server.log
458970:20220725:142545.443 Message from 192.168.0.10 is missing header. Message ignored.
458971:20220725:142640.535 Message from 192.168.0.10 is missing header. Message ignored.
458971:20220725:144311.682 Message from 192.168.0.10 is missing header. Message ignored.
root@zabbix-master:/etc/apparmor.d#
*************************
In other posts, I have seen this error is due to the agent being of a newer, incompatible version as the server - so agent version higher than server version - but this is not the case here. This is an "old" agent, talking to a "new" server.
Am I missing something? Do I need to change anything to get the agent to talk to the server?
Any suggestions or advise would be very appreciated.
EDIT: Adding the log line from the agent logs that looks suspicious (replaced IP with Zabbix Server hostname as to obfuscate the real IP):
*************************
17019:20220725:144354.930 active check configuration update from [zabbix-master:10051] started to fail (ZBX_TCP_READ() failed: [4] Interrupted system call)
*************************
Due to reasons I wont get into - I have over 100 hosts running Debian 6 (Please don't stop reading - they are in the process of being eliminated, this is part of that project) - but I need to keep an eye on these guys for a while still.
Digging through old packages, I found the 2.2.9 agent that works on Debian 6. I read around here, and confirmed that this agent should work with Zabbix 6 - https://www.zabbix.com/forum/zabbix-...ts-and-servers
I am testing this on one host to start with. I have the Zabbix Server up and running - it seems quite happy.
We are getting issues with the connectivity between the agent and the server. I have been assured that the firewall is open between the two hosts when testing. The network engineer who is managing this side of things assured me he troubleshot with the appropriate firewall rules in place. Due to security, these rules have now been removed, but can be put back in place as needed (all traffic between the two hosts are allowed when these rules are in place)
In the /var/log/zabbix/zabbix_server.log file - I see something of much interest (I am changing the IP (192.168.0.10) and zabbix server hostname (zabbix-master) for sake of company policy):
*************************
root@zabbix-master:/etc/apparmor.d# grep 192.168.0.10 /var/log/zabbix/zabbix_server.log
458970:20220725:142545.443 Message from 192.168.0.10 is missing header. Message ignored.
458971:20220725:142640.535 Message from 192.168.0.10 is missing header. Message ignored.
458971:20220725:144311.682 Message from 192.168.0.10 is missing header. Message ignored.
root@zabbix-master:/etc/apparmor.d#
*************************
In other posts, I have seen this error is due to the agent being of a newer, incompatible version as the server - so agent version higher than server version - but this is not the case here. This is an "old" agent, talking to a "new" server.
Am I missing something? Do I need to change anything to get the agent to talk to the server?
Any suggestions or advise would be very appreciated.
EDIT: Adding the log line from the agent logs that looks suspicious (replaced IP with Zabbix Server hostname as to obfuscate the real IP):
*************************
17019:20220725:144354.930 active check configuration update from [zabbix-master:10051] started to fail (ZBX_TCP_READ() failed: [4] Interrupted system call)
*************************
Comment