Upgrading to zabbix 1.9.6 beta failed

[frater]

Upgrading from 1.8.5 to 1.8.6, 1.8.7, 1.8.8beta and 1.8.8rc1 went smooth each time.
But my latest upgrade just now to 1.9.6beta failed after I used the supplied script to upgrade the database.

Maybe someone knows what I'm doing wrong or how I can fix this.

I know "This is an UNSUPPORTED Zabbix upgrade script from 1.8 to 2.0". Does this mean I'm #$% ??

I guess I need to do a fresh install of 1.9.6 and import all the XML-files

root@zabbix:/opt/zabbix-1.9.6/upgrades/dbpatches/2.0/mysql# ./upgrade -p zabbix
 WARNING: backup your database before performing upgrade

 This is an UNSUPPORTED Zabbix upgrade script from 1.8 to 2.0 for MySQL
 It does the following things:
  1. Updates indexes that might require changes;
  2. Patches the database from 1.8 schema to 2.0 schema;
  3. Adds 'Disabled' and 'Debug' usergroup if any missing;
  4. Checks for hosts not belonging to any group and adds them to one if any found.

 Usage: pass required MySQL parameters to this script (like database, user, password etc).

Continue ? (y/n) y
Dropping indexes that might need re-creation...
Enter password:
 ... dropping of indexes took 0:00:05
Creating possibly missing indexes...
Enter password:
creating of indexes took 0:00:05
Patching the database
Enter password:
ERROR 1005 (HY000) at line 6: Can't create table 'zabbix.#sql-1e3_414' (errno: 121)
Failed to patch Zabbix database. Restore from backup

[frater]

I completely configured a new server, but I need to add all my custom items by hand because the old installation is a bit #$%^#^.
I can't see the triggers anymore and the export files are incomplete...

If someone knows how I can get that server going somehow, please let me know.

[richlv]

first, 1.9.6 is a development release. it has some hundred serious bugs - and i'm serious.
additionally, there is no guaranteed database compatibility with further 1.9 releases.

nevertheless, the db patch should work fine... was that an unmodified 1.8 database ? did you run the upgrade patch only once ?

can you paste line 6 from patch.sql, just to be completely sure ?

as for solving your current situation - you restore a db backup you made right before attempting to patch the database.

[frater]

Embarrassed to admit that I don't have a backup of the database...

I lost all the trigger information and I had to create all the custom items by hand. The historical data is not that important really, but I had a nice balanced item/trigger set-up with dependencies.

I really wanted the feature {HOST.CONN}.. in trigger names which wasn't added to 1.8.8rc1, so I upgraded.

The first thing I noticed after upgrading:

• External scripts get the parameters in a different way
• API access is disabled or different (MoZBX doesn't work anymore)

[richlv]

External scripts get the parameters in a different way

yep, as briefly noted in the draft document at http://www.zabbix.com/documentation/...ameter_changes

API access is disabled or different (MoZBX doesn't work anymore)

it's enabled for all users by default now, but probably something has changed. all changes are supposed to be documented at http://www.zabbix.com/documentation/...nges_1.8_-_2.0

[frater]

yep, as briefly noted in the draft document at http://www.zabbix.com/documentation/...ameter_changes

OK, that's an improvement...

But I already wrote some workaround to handle the behaviour on CLI and zabbix.

Could you set an environment variable (for instance ZABBIX=1.96) which will enable me to write scripts that work in both 1.8 and newer versions....

I'm now using the current path...

[richlv]

OK, that's an improvement...

But I already wrote some workaround to handle the behaviour on CLI and zabbix.

Could you set an environment variable (for instance ZABBIX=1.96) which will enable me to write scripts that work in both 1.8 and newer versions....

I'm now using the current path...

please, split out this question in a separate thread
also, clarify what is the workaround, um, working around exactly.

[frater]

please, split out this question in a separate thread
also, clarify what is the workaround, um, working around exactly.

I'm sitting on a terrace celebrating my birthday but still nerd enough to check this thread. I Can explain better tomorrow, but meanwhile this thread could already explain things.

t

http://www.zabbix.com/forum/showthread.php?t=23268

i