Zabbix upgrade from 2.2 to 3.2

[xergiopd]

Hi @ll,

I'm thinking of upgrading my Zabbix server from version 2.2.9 to 3.2, is it possible or there are incompatibility issues? Is a too big jump?

[SBO]

Hi,

Direct upgrade to Zabbix 3.2 is possible from Zabbix 3.0.x, 2.4.x, 2.2.x and 2.0.x.

You have the upgrade procedure available in the zabbix official documentation : https://www.zabbix.com/documentation...lation/upgrade

[nick0909]

If I could trust the documentation to be true I would simply go along with that, but I am wondering if anyone has done this and run in to any issues.

For instance, there is a note in the upgrade steps about having to manually remove the maintenance status condition in actions and instead checking the pause operations checkbox. It appears this is actually done for you during the upgrade and does not have to be done manually.

But then there is also a warning about service_state being deprecated and you have to use service.info instead, however this conversion is not done for you.

And I believe the discovery rules logic changed between 2 and 3? Are those rewritten for you or do you have to do them all manually?

[mkdr27]

Hi, I've done the upgrade successfully, but from zabbix 2.4 to 3.2.

The error that i faced was,



As mentioned earlier, if you follow the procedures according to this link, migration can be done effortlessly.

The changes after migration have been mentioned in

https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320

[Atsushi]

Hi mkdr27,

If you are upgrading from a previous version,
the database upgrade process will start when you start the zabbix_server.

Until the database upgrade process is completed, the new version of the Web frontend is not available.

However, in the case of the environment you are using systemd, please make sure the information in the following URL.

ZBX-11203 : database upgrade from Zabbix 3.0 to Zabbix 3.2 fails

https://support.zabbix.com/browse/ZBX-11203

I first start of zabbix_server has to be performed manually.
ex.

# sudo -u zabbix /usr/sbin/zabbix_server -f -c /etc/zabbix/zabbix_server.conf

It is output the following type of log will be made to upgrade the database.
ex.

 30488:20160916:103655.733 current database version (mandatory/optional): 02040000/02040000
 30488:20160916:103655.733 required mandatory version: 03020000
 30488:20160916:103655.733 starting automatic database upgrade
 30488:20160916:103655.836 completed 1% of database upgrade
 30488:20160916:103655.852 completed 2% of database upgrade

 30488:20160916:103657.732 completed 97% of database upgrade
 30488:20160916:103657.736 completed 98% of database upgrade
 30488:20160916:103657.737 completed 100% of database upgrade
 30488:20160916:103657.737 database upgrade fully completed

If you manually start the above command line and ends with Ctrl-C.

[Clifra Jones]

Hi mkdr27,

If you are upgrading from a previous version,
the database upgrade process will start when you start the zabbix_server.

Until the database upgrade process is completed, the new version of the Web frontend is not available.

However, in the case of the environment you are using systemd, please make sure the information in the following URL.

ZBX-11203 : database upgrade from Zabbix 3.0 to Zabbix 3.2 fails

https://support.zabbix.com/browse/ZBX-11203

I first start of zabbix_server has to be performed manually.
ex.

# sudo -u zabbix /usr/sbin/zabbix_server -f -c /etc/zabbix/zabbix_server.conf

It is output the following type of log will be made to upgrade the database.
ex.

 30488:20160916:103655.733 current database version (mandatory/optional): 02040000/02040000
 30488:20160916:103655.733 required mandatory version: 03020000
 30488:20160916:103655.733 starting automatic database upgrade
 30488:20160916:103655.836 completed 1% of database upgrade
 30488:20160916:103655.852 completed 2% of database upgrade

 30488:20160916:103657.732 completed 97% of database upgrade
 30488:20160916:103657.736 completed 98% of database upgrade
 30488:20160916:103657.737 completed 100% of database upgrade
 30488:20160916:103657.737 database upgrade fully completed

If you manually start the above command line and ends with Ctrl-C.

Yes, makes sense. I did not get a clear idea of why systemd would stop zabbix from the bug report, although I did not do a thorough read.

You still have to take into account the changes such as system.state[] vs system.info[]. As we use system state checks extensively that is a lot of manual changes.

[burn1024]

If I could trust the documentation to be true I would simply go along with that, but I am wondering if anyone has done this and run in to any issues.

No need to trust, if you have backups.

[nick0909]

I have backups, I just don't like wasting my time banging my head on things that someone else has already figured out.

[HarryKalahan]

Migration from 2.2 to 3.2

Hello,

I'm trying to migrate from 2.2 from 3.2 but I receive the following error during the database upgrade:

 17402:20161117:111931.601 Starting Zabbix Server. Zabbix 3.2.1 (revision 62890).
 17402:20161117:111931.602 ****** Enabled features ******
 17402:20161117:111931.602 SNMP monitoring:           YES
 17402:20161117:111931.602 IPMI monitoring:           YES
 17402:20161117:111931.602 Web monitoring:            YES
 17402:20161117:111931.602 VMware monitoring:         YES
 17402:20161117:111931.602 SMTP authentication:       YES
 17402:20161117:111931.602 Jabber notifications:      YES
 17402:20161117:111931.602 Ez Texting notifications:  YES
 17402:20161117:111931.602 ODBC:                      YES
 17402:20161117:111931.602 SSH2 support:              YES
 17402:20161117:111931.602 IPv6 support:              YES
 17402:20161117:111931.602 TLS support:               YES
 17402:20161117:111931.602 ******************************
 17402:20161117:111931.602 using configuration file: /etc/zabbix/zabbix_server.conf
 17402:20161117:111931.608 current database version (mandatory/optional): 03010010/03010010
 17402:20161117:111931.609 required mandatory version: 03020000
 17402:20161117:111931.644 [B][Z3005] query failed: [1215] Cannot add foreign key constraint [alter table event_tag add constraint c_event_tag_1 foreign key (eventid) references events (eventid) on delete cascade]
 17402:20161117:111931.645 database upgrade failed[/B]

Do you know how can I solve it?

I installed Zabbix Server from repository by apt-get. Previous version was compiled from sources. Could it be important using the same method?

I'm using Debian 8 Jessie.

Thanks in advanced. Best regards.

[HarryKalahan]

Migration from 2.2 to 3.2

Hi all,

I answer myself. The key to solve this situation is drop the partitions of table events. It seems not compatible with Zabbix 3.2.

Refs.: https://support.zabbix.com/browse/ZBX-10876

After that Zabbix Server completes the database upgrade and it's able to start all the poollers correctly.

Then you can use the built-in housekeeping for alerts and events.

Best regards!!