Ad Widget

Collapse

AgentD 1.8.1 stops responding on Ubuntu 10.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mike@vtg
    Junior Member
    • Jan 2011
    • 28

    #1

    AgentD 1.8.1 stops responding on Ubuntu 10.4

    Greetings, hope someone can give me a pointer on this issue. I have an agent (1.8.1) running on Ubuntu 10.4 which stops responding after running for 10-15 minutes. I can restart the agent and it continues humming along for another 10-15 minutes prior to crashing. This system is also a Zabbix 1.8.1 proxy. The server is 1.8.3. I suppose I could try upgrading the proxy/agent to 1.8.3, but wondering if anyone has an idea why the daemon is crashing? I'm somewhat of a newbie to both Zabbix and Linux, but experienced admin. None of the log detail points me in an obvious direction.

    Regards,
    Mike

    PS: I don't have active checks configured on the server for this device, however they are enabled on the agent.

    In the agent log I find:


    27864:20110123:100118.271 One child process died (PID:27871). Exiting ...
    27864:20110123:100120.271 Zabbix Agent stopped. Zabbix 1.8.1 (revision 9702).
    14185:20110123:100130.405 zabbix_agentd started. Zabbix 1.8.1 (revision 9702).

    So I restart and get:

    14189:20110123:100130.407 zabbix_agentd listener started
    14190:20110123:100130.407 zabbix_agentd listener started
    14188:20110123:100130.407 zabbix_agentd listener started
    14191:20110123:100130.407 zabbix_agentd listener started
    14192:20110123:100130.408 zabbix_agentd active check started [192.168.2.14:10051]
    14187:20110123:100130.408 zabbix_agentd listener started
    14186:20110123:100130.408 zabbix_agentd collector started
    14185:20110123:103506.404 One child process died (PID:14192). Exiting ...
    14185:20110123:103508.404 Zabbix Agent stopped. Zabbix 1.8.1 (revision 9702).
    16520:20110123:103512.899 zabbix_agentd started. Zabbix 1.8.1 (revision 9702).
    16524:20110123:103512.901 zabbix_agentd listener started
    16525:20110123:103512.901 zabbix_agentd listener started
    16526:20110123:103512.901 zabbix_agentd listener started
    16527:20110123:103512.901 zabbix_agentd active check started [192.168.2.14:10051]
    16523:20110123:103512.902 zabbix_agentd listener started
    16522:20110123:103512.902 zabbix_agentd listener started
    16521:20110123:103512.902 zabbix_agentd collector started
    16520:20110123:112900.968 One child process died (PID:16527). Exiting ...
    16520:20110123:112902.968 Zabbix Agent stopped. Zabbix 1.8.1 (revision 9702).
    19947:20110123:112906.359 zabbix_agentd started. Zabbix 1.8.1 (revision 9702).
    19951:20110123:112906.361 zabbix_agentd listener started
    19952:20110123:112906.361 zabbix_agentd listener started
    19950:20110123:112906.362 zabbix_agentd listener started
    19953:20110123:112906.362 zabbix_agentd listener started
    19954:20110123:112906.362 zabbix_agentd active check started [192.168.2.14:10051]
    19949:20110123:112906.362 zabbix_agentd listener started
    19948:20110123:112906.363 zabbix_agentd collector started
  • joho
    Junior Member
    • Feb 2011
    • 3

    #2
    We had this issue too. Not on a Zabbix Proxy but on the Zabbix Server itself. We simply changed the name of the server in Zabbix to "monitor.ourdomain.com", and used the same name in the Agent configuration, and these problems disappeared.


    -joho

    Comment

    Working...