Ad Widget

Collapse

Updrage 5.4.4 to 6.0.0 - Zabbix Server Service HS

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • contact@proserv.fr
    Junior Member
    • May 2022
    • 6

    #1

    Updrage 5.4.4 to 6.0.0 - Zabbix Server Service HS

    Hi there,

    I've a problem after upgrade zabbix 5.4.4 to 6.0.0

    zabbix.server.service don't start

    Code:
    déc. 05 17:07:20 PS-SRV-EYES1 systemd[1]: Started Zabbix Server.
    déc. 05 17:07:20 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Main process exited, code=exited, status=1/FAILURE
    déc. 05 17:07:20 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
    déc. 05 17:07:30 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
    déc. 05 17:07:30 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 42.
    déc. 05 17:07:30 PS-SRV-EYES1 systemd[1]: Stopped Zabbix Server.
    déc. 05 17:07:30 PS-SRV-EYES1 systemd[1]: Starting Zabbix Server...
    déc. 05 17:07:30 PS-SRV-EYES1 systemd[1]: Started Zabbix Server.
    déc. 05 17:07:31 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Main process exited, code=exited, status=1/FAILURE
    déc. 05 17:07:31 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
    déc. 05 17:07:41 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
    déc. 05 17:07:41 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 43.
    déc. 05 17:07:41 PS-SRV-EYES1 systemd[1]: Stopped Zabbix Server.
    déc. 05 17:07:41 PS-SRV-EYES1 systemd[1]: Starting Zabbix Server...
    déc. 05 17:07:43 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
    déc. 05 17:07:43 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Failed with result 'protocol'.
    déc. 05 17:07:43 PS-SRV-EYES1 systemd[1]: Failed to start Zabbix Server.
    déc. 05 17:07:53 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
    déc. 05 17:07:53 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 44.
    déc. 05 17:07:53 PS-SRV-EYES1 systemd[1]: Stopped Zabbix Server.
    déc. 05 17:07:53 PS-SRV-EYES1 systemd[1]: Starting Zabbix Server...
    déc. 05 17:07:55 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
    déc. 05 17:07:55 PS-SRV-EYES1 systemd[1]: zabbix-server.service: Failed with result 'protocol'.
    déc. 05 17:07:55 PS-SRV-EYES1 systemd[1]: Failed to start Zabbix Server.


    Zabbix_server_log :

    Code:
      1380:20221205:172543.097 Starting Zabbix Server. Zabbix 6.0.12 (revision 126aa2f53e9).
      1380:20221205:172543.097 ****** Enabled features ******
      1380:20221205:172543.097 SNMP monitoring:           YES
      1380:20221205:172543.097 IPMI monitoring:           YES
      1380:20221205:172543.097 Web monitoring:            YES
      1380:20221205:172543.097 VMware monitoring:         YES
      1380:20221205:172543.097 SMTP authentication:       YES
      1380:20221205:172543.097 ODBC:                      YES
      1380:20221205:172543.097 SSH support:               YES
      1380:20221205:172543.097 IPv6 support:              YES
      1380:20221205:172543.097 TLS support:               YES
      1380:20221205:172543.097 ******************************
      1380:20221205:172543.097 using configuration file: /etc/zabbix/zabbix_server.conf
      1380:20221205:172543.108 current database version (mandatory/optional): 05050090/05050090
      1380:20221205:172543.108 required mandatory version: 06000000
      1380:20221205:172543.108 optional patches were found
      1380:20221205:172543.108 starting automatic database upgrade
      1380:20221205:172543.199 [Z3005] query failed: [1118] Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs [alter table `config` add `geomaps_attribution` varchar(1024) default '' not null]
      1380:20221205:172543.199 database upgrade failed
      1380:20221205:172543.201 database could be upgraded to use primary keys in history tables
    ​

    Do you have an idea ?
    Last edited by [email protected]; 05-12-2022, 18:27.
  • contact@proserv.fr
    Junior Member
    • May 2022
    • 6

    #2
    I've upgrade MariaDB 10.3 to 10.6.

    Update all zabbix tables to utf8mb4 with official zabbix script : https://www.zabbix.com/documentation...b_charset_coll

    And database :

    Code:
    MariaDB [zabbix]> SELECT @@character_set_database, @@collation_database;
    +--------------------------+----------------------+
    | @@character_set_database | @@collation_database |
    +--------------------------+----------------------+
    | utf8mb4                  | utf8mb4_bin          |
    +--------------------------+----------------------+
    1 row in set (0,000 sec)

    Tables and columns remain in utf8mb3 (exemple column "_Key" to "item" table).
    The following error occurs
    Code:
    ERROR 1071 (42000): Specified key was too long; max key length is 3072 bytes



    I've tried convert config table row format : https://www.zabbix.com/forum/zabbix-...size-too-large
    Code:
    mariadb -u root -p zabbix
    ALTER TABLE config ROW_FORMAT=dynamic;
    ​I don't know what to do anymore.
    Last edited by [email protected]; 06-12-2022, 12:02.

    Comment

    • Markku
      Senior Member
      Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
      • Sep 2018
      • 1782

      #3
      Note that the utf8mb4 page you linked explicitly says that the database schema should be Zabbix 6.0+ already before running the script, so that may explain your "key too long" errors when running it (as you are running it against 5.4 or rather some beta version "05050090" database).

      I would start again (using the 5.4 database) by changing the row formats in all tables, unless someone else has a better idea. Here is one example code for changing the tables: https://www.zabbix.com/forum/zabbix-...e-5-4-db-error

      Markku

      Comment

      • contact@proserv.fr
        Junior Member
        • May 2022
        • 6

        #4
        Thanks for your help Markku,

        I've rollback to 5.4.4 with WM snapshot, and process by order. :
        1. Upgrade MariaDB
        2. Upgrade Zabbix 5.4.4 to 6.0.12 with auto zabbix db update
        3. Upgrade Zabbix DB charset utf8mb3 to utf8mb4 with script : https://www.zabbix.com/documentation...b_charset_coll
        4. Upgrade history tables : https://www.zabbix.com/documentation...es-importantes

        Everything is OK.

        I've juste an warning to zabbix frontend : "Database history tables upgraded" on "NO"

        Comment

        • Markku
          Senior Member
          Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
          • Sep 2018
          • 1782

          #5
          That frontend message is originating from a 5.0.0 change: https://www.zabbix.com/documentation...c-float-values

          After upgrading database tables, please also set or update $DB['DOUBLE_IEEE754'] value to true in [/etc/zabbix/web]/zabbix.conf.php.
          Markku

          Comment

          • contact@proserv.fr
            Junior Member
            • May 2022
            • 6

            #6
            Yes.

            I applied double.sql script and added $DB['DOUBLE_IEEE754'] to true.

            This website is a good way to update Zabbix : https://bestmonitoringtools.com/upgr...atest-version/

            Thanks Markku for your help ;-)​

            Comment

            Working...