Problem with proxy after upgrade from 2.0.8 to 2.2.2

[Ruud Baart]

I upgraded without any problem Zabbix server, frontend and agents. Really simple, thanks. Only after the upgrade of a proxy I have a problem. The proxy logfile:

The proxy does not match Zabbix database. Current database version (mandatory/optional): UNKNOWN. Required mandatory version: 02020000.

The Zabbix server completed the database upgrade without any actions:

...
12635:20140406:172927.418 completed 97% of database upgrade
...
12635:20140406:172927.422 completed 100% of database upgrade
12635:20140406:172927.422 database upgrade fully completed

As far as I can see in the documentation the proxy database -- in my case sqlite3 -- should be upgraded automatically. But this does not happen. Do I miss something? And if it is not done automatically what is the best way to upgrade the database?

[sckif]

i Have this problem too!!! how you solved the problem?
Edit/Delete Message

[Ruud Baart]

Simpel solution

Stop the proxy, delete de sqlite database and start the monitoring. A new database will be created. There is no script to modify the proxy sqlite database but the database contains no important information which should be saved. All information is send to the zabbix server.

[sckif]

Stop the proxy, delete de sqlite database and start the monitoring. A new database will be created. There is no script to modify the proxy sqlite database but the database contains no important information which should be saved. All information is send to the zabbix server.

i not use zabbix proxy...(

[Ruud Baart]

What database do you use in combination with your Zabbix server? As far as I know all databases except for sqlite are automatically upgraded. If you use sqlite database with the Zabbix server I assume you have a problem. Consider a different database engine: MySQL or Posgres.

[sckif]

What database do you use in combination with your Zabbix server? As far as I know all databases except for sqlite are automatically upgraded. If you use sqlite database with the Zabbix server I assume you have a problem. Consider a different database engine: MySQL or Posgres.

i use mysql... 5.0.95
mysql -uroot -p --database=zabbix <patch.sql
ERROR 1060 (42S21) at line 54: Duplicate column name 'listen_ip'

./upgrade -uroot -p --database=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
Patching the database

ERROR 1060 (42S21) at line 54: Duplicate column name 'listen_ip'
Failed to patch Zabbix database. Restore from backup

i upgrading from 2.0.2 to 2.2.3

[Ruud Baart]

Your question in something else then my question. I upgraded without any problems Zabbix server, front end and agents. Only the proxy sqlite database was a problem. In my case the Postgres database was upgraded without any user intervention and without any problem. As written in the documentation.

Logfiles shows:
...
12635:20140406:172927.418 completed 97% of database upgrade
...
12635:20140406:172927.422 completed 100% of database upgrade
12635:20140406:172927.422 database upgrade fully completed

I assume that with a MySQL database there should be no difference. If not, I can't help you. Sorry.