ideas?

[windly]

Could anyone tell me the possible problems? Thanks head.

The agentd.log is shown:

013298:20050805:142120 zabbix_agentd 13298 started
013294:20050805:142129 In check_security()
013294:20050805:142129 Connection from [191.168.1.47]. Allowed servers [191.168.1.47]
013294:20050805:142129 Before read()
013294:20050805:142129 After read() 2 [20]
013294:20050805:142129 Got line:cksum[/usr/bin/ssh]
013293:20050805:142129 One child process died. Exiting ...
013295:20050805:142129 Got signal. Exiting ...
013296:20050805:142129 Got signal. Exiting ...
013297:20050805:142129 Got signal. Exiting ...
013298:20050805:142129 Got signal. Exiting ...

[Alexei]

You're running ZABBIX 1.0, aren't you? I recall a problem related to cksum[] on 64 platforms which led to crash of the agent. As a quick workaround, you may disable monitoring of cksum[].

[windly]

Thanks Alexei. yes, I am running zabbix1.0. I disabled the cksum. The host is moitored.

Could we change ListenPort using zabbix1.0? I did as following in agentd.conf :

Server=serverIP
# Listen port. Default is 10000

ListenPort=10061

# IP address to bind agent
# If missing, bind to all available IPs

#ListenIP=127.0.0.1

Changed host port to 10061 and restarted agentd. Did I miss anything? The host is unreachable now.
Is Listenport=10000 hardcorded in zabbix1.0? or Did I do something wrong???

[Alexei]

Have you changed port number on server side?

[windly]

Thank for fast response . Yes I have changed but still not working