Zabbix Agent stopped working after reboot ???

[whausler]

Hi All,

I've just spent a confusing few hours attempting to work out why a zabbix-agentd process has stopped working on a Fedora Core 6 Xen host after we installed more RAM and rebooted it. The zabbix-agentd process was working correctly before this upgrade and reboot, and the only thing that has changed is that we have installed more RAM and rebooted...

Basically, it seems that the Zabbix server is getting a bad response from the client, but the client is reporting that it is returning the details correctly. Here are some log file details:

"""
[server]
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [system.cpu.util[,user]@vortex.lan] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [proc.num[ntpd,ntp]@vortex.lan] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [vfs.fs.size[/tmp,free]@vortex.lan] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [system.cpu.load[,avg15]@vortex.lan] having type [0]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [io[disk_wio]@vortex.lan] having type [0]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [vfs.fs.size[/boot,total]@vortex.lan] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [[email protected]] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [vm.memory.size[free]@vortex.lan] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [agent.ping@vortex] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
020345:20070621:114326 Type of received value [ZBXD] is not sutable for [[email protected]] having type [3]
020345:20070621:114326 Returning NOTSUPPORTED
....

[client]
18101:20070621:114326 Processing request.
18101:20070621:114326 In check_security()
18101:20070621:114326 Requested [system.cpu.util[,user]]
18101:20070621:114326 Sending back [0.000000]
18102:20070621:114326 Processing request.
18102:20070621:114326 In check_security()
18102:20070621:114326 Requested [proc.num[ntpd,ntp]]
18102:20070621:114326 Sending back [1]
18103:20070621:114326 Processing request.
18103:20070621:114326 In check_security()
18103:20070621:114326 Requested [vfs.fs.size[/tmp,free]]
18103:20070621:114326 Sending back [3713608]
18101:20070621:114326 Processing request.
18101:20070621:114326 In check_security()
18101:20070621:114326 Requested [system.cpu.load[,avg15]]
18101:20070621:114326 Sending back [0.000000]
18102:20070621:114326 Processing request.
18102:20070621:114326 In check_security()
18102:20070621:114326 Requested [io[disk_wio]]
18102:20070621:114326 Sending back [ZBX_NOTSUPPORTED]
18103:20070621:114326 Processing request.
18103:20070621:114326 In check_security()
18103:20070621:114326 Requested [vfs.fs.size[/boot,total]]
18103:20070621:114326 Sending back [253743]
18101:20070621:114326 Processing request.
18101:20070621:114326 In check_security()
18101:20070621:114326 Requested [proc.stat.cpu.idle]
18101:20070621:114326 Before
18101:20070621:114326 Run remote command [cat /proc/stat|grep 'cpu '|cut -d ' ' -f 6] Result [8] [29611154]
18101:20070621:114326 Sending back [29611154]
18102:20070621:114326 Processing request.
18102:20070621:114326 In check_security()
18102:20070621:114326 Requested [vm.memory.size[free]]
18102:20070621:114326 Sending back [73142272]
18103:20070621:114326 Processing request.
18103:20070621:114326 In check_security()
18103:20070621:114326 Requested [agent.ping]
18103:20070621:114326 Sending back [1]
18101:20070621:114326 Processing request.
18101:20070621:114326 In check_security()
18101:20070621:114326 Requested [system.users.num]
18101:20070621:114326 Before
18101:20070621:114326 Run remote command [who|wc -l] Result [1] [1]
18101:20070621:114326 Sending back [1.000000]
...
"""

Client is
"""
ZABBIX Agent (daemon) v1.4 (29 May 2007)
Compilation time: Jun 1 2007 14:42:47
"""

Server is (CentOS 4.5)
"""
ZABBIX Server (daemon) v1.1.7 (30 March 2007)
Compilation time: May 18 2007 12:39:44
"""

Both the client and the server are using Fedora Core 6 source RPMs for the zabbix install. The server is currently recording details for 3 other hosts successfully (being a RH9, CentOS and Windows machine).

I've been looking over these forums for the last few hours to see if anyone else has seen this type of issue before, and attempting debugging procedures (like ensuring that the correct zabbix-agentd process is running on the client, ensuring that the zabbix-server is storing the returned values correctly, etc). From what I can tell, everything should be working fine (and originally was before the system rebooted), but now everything has broken for that client....

Any assistance or further debugging procedures that could be suggested would be great.

Kindest Regards,

William Hausler

[Coder]

I think are incompatible ZABBIX Agentv1.4 and ZABBIX Server v1.1.7

I try ZABBIX Agentv1.4 with ZABBIX Server v1.1.6 and also have NOTSUPPORTED on all items.

[whausler]

I think are incompatible ZABBIX Agentv1.4 and ZABBIX Server v1.1.7

I try ZABBIX Agentv1.4 with ZABBIX Server v1.1.6 and also have NOTSUPPORTED on all items.

Wow... silly me... Thanks for pointing this out, I'll recompile the agent from the 1.1.7 source and install again.

But as another random question, why would the 1.4 agent work fine until the machine was rebooted? It should have failed at the time I originally installed the RPM and configured it (which was weeks ago)....

[Coder]

Its strange that works after installation.

I build from source and at once had an error.

[Alexei]

But as another random question, why would the 1.4 agent work fine until the machine was rebooted?...

Because obviously you ran 1.1.x agent prior to the upgrade. You may check what "ZABBIX Agent version" (agent.version) reported before and now.

[whausler]

Because obviously you ran 1.1.x agent prior to the upgrade. You may check what "ZABBIX Agent version" (agent.version) reported before and now.

Yep, that would be it

"""
messages:Jun 19 18:04:43 vortex Updated: zabbix-agent.x86_64 1.4-2.fc6
"""

Thanks for your assistance in this issue.