Ad Widget

Collapse

Вопрос по обновлению с 3.2 на 3.4

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Newmark
    Junior Member
    • Sep 2015
    • 8
    #1

    Вопрос по обновлению с 3.2 на 3.4

    Добрый вечер!
    Прощу помощи и совета по следующему вопрос.
    Проводил обновления с 3.2.10 на 3.4.4
    Вроде все нормально, без ошибок, но при рестарте zabbix сервера вылезла следующая ерунда:
    HTML Code:
      2351:20171210:195922.084 Starting Zabbix Server. Zabbix 3.4.4 (revision 74338).
  2351:20171210:195922.084 ****** Enabled features ******
  2351:20171210:195922.084 SNMP monitoring:           YES
  2351:20171210:195922.084 IPMI monitoring:           YES
  2351:20171210:195922.084 Web monitoring:            YES
  2351:20171210:195922.084 VMware monitoring:         YES
  2351:20171210:195922.084 SMTP authentication:       YES
  2351:20171210:195922.084 Jabber notifications:      YES
  2351:20171210:195922.084 Ez Texting notifications:  YES
  2351:20171210:195922.084 ODBC:                      YES
  2351:20171210:195922.084 SSH2 support:              YES
  2351:20171210:195922.084 IPv6 support:              YES
  2351:20171210:195922.084 TLS support:               YES
  2351:20171210:195922.084 ******************************
  2351:20171210:195922.084 using configuration file: /etc/zabbix/zabbix_server.conf
  2351:20171210:195922.090 current database version (mandatory/optional): 03030019/03030019
  2351:20171210:195922.090 required mandatory version: 03040000
  2351:20171210:195922.090 optional patches were found
  2351:20171210:195922.090 starting automatic database upgrade
  2351:20171210:195922.090 [Z3005] query failed: [1091] Can't DROP 'data_type'; check that column/key exists [alter table items drop column data_type]
  2351:20171210:195922.090 database upgrade failed
    Куда копать и что делать для исправления ситуации? :-)
    Last edited by Newmark; 10-12-2017, 20:01.
    Tags: None
    • Newmark
      Junior Member
      • Sep 2015
      • 8
      #2
      Небольшая ремарка

      Не досмотрел логи. Судя по всему обновление базы прошло не совсем корректно.
      HTML Code:
       19896:20171210:172117.591 Zabbix Server stopped. Zabbix 3.2.10 (revision 74337).
  2004:20171210:195255.687 Starting Zabbix Server. Zabbix 3.4.4 (revision 74338).
  2004:20171210:195255.690 ****** Enabled features ******
  2004:20171210:195255.690 SNMP monitoring:           YES
  2004:20171210:195255.690 IPMI monitoring:           YES
  2004:20171210:195255.690 Web monitoring:            YES
  2004:20171210:195255.691 VMware monitoring:         YES
  2004:20171210:195255.691 SMTP authentication:       YES
  2004:20171210:195255.691 Jabber notifications:      YES
  2004:20171210:195255.691 Ez Texting notifications:  YES
  2004:20171210:195255.691 ODBC:                      YES
  2004:20171210:195255.691 SSH2 support:              YES
  2004:20171210:195255.691 IPv6 support:              YES
  2004:20171210:195255.691 TLS support:               YES
  2004:20171210:195255.691 ******************************
  2004:20171210:195255.691 using configuration file: /etc/zabbix/zabbix_server.conf
  2004:20171210:195255.693 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
  2004:20171210:195255.693 database is down: reconnecting in 10 seconds
  2004:20171210:195305.693 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
  2004:20171210:195305.693 database is down: reconnecting in 10 seconds
  2004:20171210:195315.694 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
  2004:20171210:195315.694 database is down: reconnecting in 10 seconds
  2004:20171210:195325.694 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
  2004:20171210:195325.694 database is down: reconnecting in 10 seconds
  2004:20171210:195335.702 database connection re-established
  2004:20171210:195335.704 current database version (mandatory/optional): 03020000/03020001
  2004:20171210:195335.704 required mandatory version: 03040000
  2004:20171210:195335.704 optional patches were found
  2004:20171210:195335.704 starting automatic database upgrade
  2004:20171210:195335.714 completed 0% of database upgrade
  2004:20171210:195335.961 completed 1% of database upgrade
  2004:20171210:195336.001 completed 2% of database upgrade
  2004:20171210:195336.033 completed 3% of database upgrade
  2004:20171210:195336.056 completed 4% of database upgrade
  2004:20171210:195336.090 completed 5% of database upgrade
  2004:20171210:195336.128 completed 6% of database upgrade
  2004:20171210:195336.153 completed 7% of database upgrade
  2004:20171210:195336.188 completed 8% of database upgrade
  2004:20171210:195336.429 completed 9% of database upgrade
  2004:20171210:195336.534 Got signal [signal:15(SIGTERM),sender_pid:2608,sender_uid:0,reason:0]. Exiting ...
  2004:20171210:195338.617 syncing history data...
  2004:20171210:195338.617 syncing history data done
  2004:20171210:195338.617 syncing trend data...
  2004:20171210:195338.618 syncing trend data done

        Comment

        • Newmark
          Junior Member
          • Sep 2015
          • 8
          #3
          Всем спасибо!
          Сам дурак. Сделал некорректную настройку СУБД, которая стопила MySQL через некоторое время после запуска. Соответственно криво прошло обновление базы.
          Откатил БД и повторно запустил обновление. Все прошло на ура.

            Comment

            Previous template Next
            Working...