Ad Widget

Collapse

zabbix-server not starting after update from 2.2 -> 3.4

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Zaolisbbix
    Junior Member
    • Aug 2018
    • 6
    #1

    zabbix-server not starting after update from 2.2 -> 3.4

    After zabbix update from 2.2 - 3.4 I can't start zabbix-server.

    sudo service zabbix-server start = Job is already running: zabbix-server

    sudo service zabbix-server status = zabbix-server start/running


    logs :
    sudo tail -10 /var/log/zabbix/zabbix_server.log :
    1564:20180814:140655.541 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1430:20180814:140655.562 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1461:20180814:140655.575 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1436:20180814:140655.592 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1500:20180814:140655.610 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1481:20180814:140655.620 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1002:20180814:140655.645 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    1002:20180814:140657.684 syncing history data...
    1002:20180814:140657.776 syncing history data done
    1002:20180814:140657.776 syncing trends data...

    sudo tail -50 /var/log/zabbix-server/zabbix_server.log :

    2105:20150420:120826.207 Starting Zabbix Server. Zabbix 2.2.2 (revision 42525). Trying to start wrong verion !
    2105:20150420:120826.207 ****** Enabled features ******
    2105:20150420:120826.207 SNMP monitoring: YES
    2105:20150420:120826.207 IPMI monitoring: YES
    2105:20150420:120826.207 WEB monitoring: YES
    2105:20150420:120826.207 VMware monitoring: YES
    2105:20150420:120826.207 Jabber notifications: YES
    2105:20150420:120826.207 Ez Texting notifications: YES
    2105:20150420:120826.207 ODBC: YES
    2105:20150420:120826.207 SSH2 support: YES
    2105:20150420:120826.207 IPv6 support: YES
    2105:20150420:120826.207 ******************************
    2105:20150420:120826.207 using configuration file: /etc/zabbix/zabbix_server.conf
    2105:20150420:120826.215 The server does not match Zabbix database. Current database version (mandatory/optional): 02040000/02040000. Required mandatory version: 02020000.


    zabbix_server --version
    zabbix_server (Zabbix) 3.4.12
    Revision 83229 30 July 2018, compilation time: Jul 30 2018 11:50:46


    Any ideas ?

    Regards
    Last edited by Zaolisbbix; 14-08-2018, 21:53.
    Tags: None
    • Atsushi
      Senior Member
      • Aug 2013
      • 2028
      #2
      The log of 2015 is unnecessary.
      Please check the log when it can not be started at the present time.
      The cause that can not be activated should be output.

      Also, please tell me the distribution and detailed version of OS being used.

        Comment

        • Zaolisbbix
          Junior Member
          • Aug 2018
          • 6
          #3
          Yeah the 2015 log is old my bad.
          OS: Ubuntu 14.04.2

          This is strange i am not getting anything in the /var/log/zabbix/zabbix_server.log
          These are the latest, just before updateing the server.

          1555:20180814:140655.492 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1449:20180814:140655.508 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1401:20180814:140655.508 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1428:20180814:140655.536 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1564:20180814:140655.541 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1430:20180814:140655.562 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1461:20180814:140655.575 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1436:20180814:140655.592 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1500:20180814:140655.610 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1481:20180814:140655.620 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1002:20180814:140655.645 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
          1002:20180814:140657.684 syncing history data...
          1002:20180814:140657.776 syncing history data done
          1002:20180814:140657.776 syncing trends data...

          Regards
          Last edited by Zaolisbbix; 15-08-2018, 02:42.

            Comment

            • Atsushi
              #3.1
              Atsushi commented
              15-08-2018, 03:48
              Editing a comment
              It should be outputting a log identifying the problem before the time you gave it.
              Please check a wider range of logs.
            Previous template Next
            Working...