Ad Widget

Collapse

Zabbix_Server stops immediately when started

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ucs75
    Junior Member
    • Mar 2012
    • 14

    #1

    Zabbix_Server stops immediately when started

    Zabbix Version: 2.0.2

    I have a server that has been in service for some time now, until I realized I had set it up as a standalone, and needed to enable Distributed Monitoring (DM).

    I followed the instructions:

    (made a copy of my database)

    updated the zabbix_server.conf, changing node id from 0 to 1

    ran zabbix_server -n 1 -c /usr/local/etc/zabbix_server.conf

    [waited many hours for the 60 million rows (per history table) to be updated]

    Saw that the process reported success...

    Launched the web interface. Went to Configuration-->DM and set the node ID to 1, local_node, and set the IP address as my public IP.

    The server is in a DMZ, there is no NATing involved.

    Then I start up the zabbix_server service, only to see it immediately stop again! This happens every time I start the server after conversion. Reverting to the old database allows the server to run, but conversion always results in an immediate stop. I updated the logging level to 4 and am finding:

    Code:
    [B]22573[/B]:20130305:081548.133 server #18 skipped [node watcher #1]
     22554:20130305:081548.135 One child process died ([B]PID:22573,exitcode/signal:0[/B]). Exiting ...
     22554:20130305:081548.136 zbx_on_exit() called
     22556:20130305:081548.136 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22557:20130305:081548.138 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22558:20130305:081548.140 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22561:20130305:081548.140 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22559:20130305:081548.140 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22566:20130305:081548.142 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22560:20130305:081548.144 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22564:20130305:081548.145 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22563:20130305:081548.147 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22562:20130305:081548.149 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22565:20130305:081548.149 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22572:20130305:081548.151 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22571:20130305:081548.154 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22567:20130305:081548.154 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22570:20130305:081548.156 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22569:20130305:081548.158 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
     22568:20130305:081548.159 Got signal [signal:15(SIGTERM),sender_pid:22554,sender_uid:500,reason:0]. Exiting ...
    It seems that "server 18 [node watcher #1]" is always the culprit in the shutdown. But WHY?!!!? And how do I fix it?
  • ZehEmEe
    Junior Member
    • Feb 2013
    • 17

    #2
    strace

    what does strace report? The zabbix log files are often not meaningful enought to find problems in an acceptable time.

    Cheers

    Zeh

    Comment

    Working...