I've got a server running on Debian X86 Testing with PostgreSQL for the database backend, and two Lenny test clients. One is 1.4.x on X86; the other is 1.8.1 (via lenny-backports.) on AMD64
-I'm unable to monitor the network statistics on eth0 on the 64 bit machine. "Not supported by agent". What? The x86 Lenny client works just fine...
Second part:
I couldn't figure out why my AMD64 client was refusing our server connection until I saw:
Listener error: Connection from [::ffff:10.200.12.130] rejected. Allowed server is [10.200.12.130]
I added ::ffff: in agentd.conf and it started working. Why does Zabbix use a convention nobody else does for specifying IP addresses? And why is this undocumented?
I've also been experiencing problems with the Zabbix server no longer checking clients or retrieving data after a few days. A restart fixes it. The only mention I could find was a post in the bugs section where several users report this problem in 1.5. A developer responds saying he's fixed it, the users disagree, and the developer closes the ticket and insists it's fixed unless he receives proof.
-I'm unable to monitor the network statistics on eth0 on the 64 bit machine. "Not supported by agent". What? The x86 Lenny client works just fine...
Second part:
I couldn't figure out why my AMD64 client was refusing our server connection until I saw:
Listener error: Connection from [::ffff:10.200.12.130] rejected. Allowed server is [10.200.12.130]
I added ::ffff: in agentd.conf and it started working. Why does Zabbix use a convention nobody else does for specifying IP addresses? And why is this undocumented?
I've also been experiencing problems with the Zabbix server no longer checking clients or retrieving data after a few days. A restart fixes it. The only mention I could find was a post in the bugs section where several users report this problem in 1.5. A developer responds saying he's fixed it, the users disagree, and the developer closes the ticket and insists it's fixed unless he receives proof.
Comment