Ad Widget

Collapse

Zabbix Proxy Upgrade Failure - 5.4 to 6.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • remwin
    Junior Member
    • May 2023
    • 1

    #1

    Zabbix Proxy Upgrade Failure - 5.4 to 6.0

    I have upgraded my Zabbix Server from 6.4.2 already, but when attempting to upgrade one of my proxy servers, the log file shows only:

    1055:20230512:054817.129 Zabbix Proxy stopped. Zabbix 5.0.31 (revision f64a07aefca).
    2399:20230512:054817.218 Starting Zabbix Proxy (passive) [Zabbix_Proxy_102]. Zabbix 6.0.17 (revision c81d82859a8).
    2399:20230512:054817.219 **** Enabled features ****
    2399:20230512:054817.219 SNMP monitoring: YES
    2399:20230512:054817.219 IPMI monitoring: YES
    2399:20230512:054817.219 Web monitoring: YES
    2399:20230512:054817.219 VMware monitoring: YES
    2399:20230512:054817.219 ODBC: YES
    2399:20230512:054817.219 SSH support: YES
    2399:20230512:054817.219 IPv6 support: YES
    2399:20230512:054817.219 TLS support: YES
    2399:20230512:054817.219 **************************
    2399:20230512:054817.220 using configuration file: /etc/zabbix/zabbix_proxy.conf
    2399:20230512:054817.272 current database version (mandatory/optional): 05000000/05000007
    2399:20230512:054817.273 required mandatory version: 06000000
    2399:20230512:054817.273 optional patches were found
    2399:20230512:054817.273 starting automatic database upgrade
    2399:20230512:054817.288 [Z3005] query failed: [1118] Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [alter table `config` add `default_lang` varchar(5) default 'en_GB' not null]
    2399:20230512:054817.288 database upgrade failed
    2428:20230512:054829.543 Starting Zabbix Proxy (passive) [Zabbix_Proxy_102]. Zabbix 6.0.17 (revision c81d82859a8).
    2428:20230512:054829.543 **** Enabled features ****
    2428:20230512:054829.543 SNMP monitoring: YES
    2428:20230512:054829.543 IPMI monitoring: YES
    2428:20230512:054829.544 Web monitoring: YES
    2428:20230512:054829.544 VMware monitoring: YES
    2428:20230512:054829.544 ODBC: YES
    2428:20230512:054829.544 SSH support: YES
    2428:20230512:054829.544 IPv6 support: YES
    2428:20230512:054829.544 TLS support: YES
    2428:20230512:054829.544 **************************​

    Now the log file only repeats the same errors over and over and will not start. How can I move forward here?

    Ubuntu server version 22.04.2

    Thanks
  • LenR
    Senior Member
    • Sep 2009
    • 1005

    #2
    Added, is the proxy mysql version a supported version?

    I'm not sure proxy database upgrade is supported. Unless your proxy had data that wasn't sent to Zabbix, you don't need anything it contains, proxy restart will pull a new config from the server. Just delete it and follow the procedures to create a new proxy database. My DR process for proxy servers was to just let our automation rebuild the server from scratch.

    Even if you have unsent data, at this point, it may not be recoverable anyway.

    Comment

    • Hamardaban
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • May 2019
      • 2713

      #3
      If you use sqlite, it is enough to delete the database file - at the start, the proxy will create a new one.

      Comment

      Working...