Zabbix 1.6 upgrade

[Melkor]

Hi,
I'm using zabbix server 1.5 and wan't to upgrade to 1.61, the problem is that this zabbix server is monitoring our IDC and I can't upgrade in the same server for the risk of crash.

My idea is to create another Zabbix Server with the new version and import the old data base:

In the old server:
mysqldump -u username -ppassword zabbix > zabbix152.sql

In the new server (after copy the file):
mysql -u username -ppassword zabbix < zabbix152.sql

The select works but the server doesn't work fine...

After do that I have try to update de data base in the new server:
cat patch.sql |mysql zabbix -uzabbix -p

Mysql returns error:
ERROR 1091 (42000) at line 14: Can't DROP 'triggerid'; check that column/key exists

And I still receive the same errors in the front end
* Error in query [UPDATE sessions SET status=1 WHERE sessionid=''] [Unknown column 'status' in 'field list']
* Undefined index: authentication_type[/home/zabbix/public_html/index.php:59]

And, when I try to insert the identification fields:
* Error in query [UPDATE sessions SET status=1 WHERE sessionid=''] [Unknown column 'status' in 'field list']
* Undefined index: authentication_type[/home/zabbix/public_html/index.php:59]
* Error in query [SELECT u.userid,u.attempt_failed, u.attempt_clock, u.attempt_ip FROM users u WHERE u.alias='admin'] [Unknown column 'u.attempt_failed' in 'field list']
* mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource[/home/zabbix/public_html/include/db.inc.php:519]

Can somebody help me?

Thank you in advance

Jorge

[xs-]

Your main problem is that your 'live' database is running against a patched 1.5.x version.
1.5 is a development version which is not supported for upgrade. The reason for this is that all patches available are based on an upgrade from a stable (1.4.x in this case) version.

You will have to manually upgrade patch your database using:

• 1.4 schema.sql
  As a baseline on which the 1.6 patch.sql is based.
• patch.sql of the 1.5 version you are running now
  To see which changes are already made on the 1.4 tree (this can include changes which have been rolled back in 1.6 or are implemented differently)
• 1.6 patch.sql / schema.sql
  To see what the database schema should look like

Bottom line.
Upgrades are only supported stable->stable.
Only use development releases for development / testing purposes.

[Melkor]

XS
Than you for the answer. I'm gonna try that... but I don't really know how to do it

Jorge