Ad Widget

Collapse

Stuck at "Starting automatic database upgrade"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GDBJNC
    Junior Member
    • Dec 2017
    • 8

    #1

    Stuck at "Starting automatic database upgrade"

    Hello. I'm trying to upgrade from 3.4.5 to 3.4.7 and I'm stuck at "Starting automatic database upgrade"

    How long should this take? I tried restarting the zabbix-server and am still at the same spot.

    Any help would be greatly appreciated!

    Below is my /var/log/zabbix/zabbix_server.log output.

    1446:20180226:193610.338 syncing trend data done
    1446:20180226:193610.338 Zabbix Server stopped. Zabbix 3.4.5 (revision 76340).
    72574:20180226:193619.610 Starting Zabbix Server. Zabbix 3.4.7 (revision 77720).
    72574:20180226:193619.610 ****** Enabled features ******
    72574:20180226:193619.610 SNMP monitoring: YES
    72574:20180226:193619.610 IPMI monitoring: YES
    72574:20180226:193619.610 Web monitoring: YES
    72574:20180226:193619.610 VMware monitoring: YES
    72574:20180226:193619.610 SMTP authentication: YES
    72574:20180226:193619.610 Jabber notifications: YES
    72574:20180226:193619.610 Ez Texting notifications: YES
    72574:20180226:193619.610 ODBC: YES
    72574:20180226:193619.610 SSH2 support: YES
    72574:20180226:193619.610 IPv6 support: YES
    72574:20180226:193619.610 TLS support: YES
    72574:20180226:193619.610 ******************************
    72574:20180226:193619.610 using configuration file: /etc/zabbix/zabbix_server.conf
    72574:20180226:193619.624 current database version (mandatory/optional): 03040000/03040005
    72574:20180226:193619.624 required mandatory version: 03040000
    72574:20180226:193619.624 optional patches were found
    72574:20180226:193619.624 starting automatic database upgrade
    72574:20180226:203700.562 Got signal [signal:15(SIGTERM),sender_pid:83707,sender_uid:0,r eason:0]. Exiting ...
    83750:20180226:203705.762 Starting Zabbix Server. Zabbix 3.4.7 (revision 77720).
    83750:20180226:203705.762 ****** Enabled features ******
    83750:20180226:203705.762 SNMP monitoring: YES
    83750:20180226:203705.763 IPMI monitoring: YES
    83750:20180226:203705.763 Web monitoring: YES
    83750:20180226:203705.763 VMware monitoring: YES
    83750:20180226:203705.763 SMTP authentication: YES
    83750:20180226:203705.763 Jabber notifications: YES
    83750:20180226:203705.763 Ez Texting notifications: YES
    83750:20180226:203705.763 ODBC: YES
    83750:20180226:203705.763 SSH2 support: YES
    83750:20180226:203705.763 IPv6 support: YES
    83750:20180226:203705.763 TLS support: YES
    83750:20180226:203705.763 ******************************
    83750:20180226:203705.763 using configuration file: /etc/zabbix/zabbix_server.conf
    83750:20180226:203705.842 current database version (mandatory/optional): 03040000/03040005
    83750:20180226:203705.842 required mandatory version: 03040000
    83750:20180226:203705.842 optional patches were found
    83750:20180226:203705.842 starting automatic database upgrade
  • LenR
    Senior Member
    • Sep 2009
    • 1005

    #2
    How big are your events, event_recovery and problem tables?

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #3
      Just check using mysqladmin what kind of query is running on mysql engine.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      Working...