Ad Widget

Collapse

zabbix_server 1.8.4 crashes/exits

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bdm56840
    Junior Member
    • Mar 2011
    • 2

    #1

    zabbix_server 1.8.4 crashes/exits

    I'm evaluating zabbix 1.8.4 on a CentOS x64 system.

    I just completed the install using mysql and have just fired up the server and configured the web interface. I haven't added any hosts or changed any configuration yet. But I've found that the zabbix server has crashed or existed twice with in an hour.

    The server log file contains the following on the last exit:


    8467:20110306:023437.081 Sleeping for 5 seconds
    8474:20110306:023437.148 Syncing ...
    8474:20110306:023437.148 In DCsync_history(history_first:0 history_num:0)
    8474:20110306:023437.148 DB syncer spent 0.000200 second while processing 0 items. Nextsync after 5 sec.
    8476:20110306:023437.149 Syncing ...
    8476:20110306:023437.149 In DCsync_history(history_first:0 history_num:0)
    8476:20110306:023437.149 DB syncer spent 0.000103 second while processing 0 items. Nextsync after 5 sec.
    8470:20110306:023437.149 Syncing ...
    8470:20110306:023437.149 In DCsync_history(history_first:0 history_num:0)
    8470:20110306:023437.149 DB syncer spent 0.000073 second while processing 0 items. Nextsync after 5 sec.
    8478:20110306:023437.149 Syncing ...
    8478:20110306:023437.149 In DCsync_history(history_first:0 history_num:0)
    8478:20110306:023437.149 DB syncer spent 0.000074 second while processing 0 items. Nextsync after 5 sec.
    8482:20110306:023437.149 In process_proxy()
    8482:20110306:023437.149 In DCconfig_get_proxypoller_hosts()
    8482:20110306:023437.149 End of DCconfig_get_proxypoller_hosts():0
    8482:20110306:023437.149 End of process_proxy()
    8482:20110306:023437.150 In DCconfig_get_proxy_nextcheck()
    8482:20110306:023437.150 End of DCconfig_get_proxy_nextcheck():-1
    8482:20110306:023437.150 Poller spent 0.000316 seconds while processing 0 proxies. Sleeping for 5 seconds
    8482:20110306:023437.408 Got signal [signal:15(SIGTERM),sender_pid:8644,sender_uid:0,re ason:0]. Exiting ...
    8431:20110306:023437.427 One child process died (PID:8482,exitcode/signal:255). Exiting ...
    8431:20110306:023437.458 zbx_on_exit() called
    8436:20110306:023437.458 Got signal [signal:15(SIGTERM),sender_pid:8431,sender_uid:500, reason:0]. Exiting ...
    8437:20110306:023437.460 Got signal [signal:15(SIGTERM),sender_pid:8431,sender_uid:500, reason:0]. Exiting ...
    8438:20110306:023437.462 Got signal

    finally

    8431:20110306:023439.470 Connect to the database
    8431:20110306:023439.471 Query [txnlev:0] [SET NAMES utf8]
    8431:20110306:023439.471 Query [txnlev:0] [SET CHARACTER SET utf8]
    8431:20110306:023439.472 In free_database_cache()
    8431:20110306:023439.472 In DCsync_all()
    8431:20110306:023439.472 In DCsync_history(history_first:0 history_num:0)
    ...
    ending with:

    8431:20110306:023439.473 End of free_configuration_cache()
    8431:20110306:023439.474 Zabbix Server stopped. Zabbix 1.8.4 (revision 16604).

    Anything I can change in the configuration or update to make the server stay running?

    thanks.
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    Code:
    Got signal [signal:15(SIGTERM),sender_pid:8644,sender_uid:0
    here it looks like somebody with root privileges has killed zabbix server process on purpose
    Zabbix 3.0 Network Monitoring book

    Comment

    • bdm56840
      Junior Member
      • Mar 2011
      • 2

      #3
      Yes. that is strange, but I was the only one logged in and I don't believe I did that.

      Anyhow I turned up the logging level and will post if I see it happen again.

      thanks.

      Comment

      Working...