Hi,
I just made a 1.8->2.0.0 migration on a dedicated server made to test the migration and notice any time I activate monitoring of a host, all items have an interface id set to null.
I followed the recommendations of the jira bug report : https://support.zabbix.com/browse/ZBX-4640
That's how I noticed every items had no interface id.
The only way I managed to set them was to "unlink and clear" every templates on the host and re associate them. but this isn't really a good solution for a migration on production environment.
I'll try a 1.8->2.0.1 migration see if this changes anything. But this problem seem ackward I looks familiar with the bug report : https://support.zabbix.com/browse/ZBX-4997 (fixed for 2.0.0rc5)
has anybody got similar problem ? did it got resolved on 2.0.1 ?
thanks
UPDATE : found the reason. I updated the database with the 'zabbix' user instead of the 'postgres' user. The patch creates a function using plpgsql and the zabbix user isn't allowed to do that. I made another upgrade using postgres user and things went fine.
I just made a 1.8->2.0.0 migration on a dedicated server made to test the migration and notice any time I activate monitoring of a host, all items have an interface id set to null.
I followed the recommendations of the jira bug report : https://support.zabbix.com/browse/ZBX-4640
That's how I noticed every items had no interface id.
The only way I managed to set them was to "unlink and clear" every templates on the host and re associate them. but this isn't really a good solution for a migration on production environment.
I'll try a 1.8->2.0.1 migration see if this changes anything. But this problem seem ackward I looks familiar with the bug report : https://support.zabbix.com/browse/ZBX-4997 (fixed for 2.0.0rc5)
has anybody got similar problem ? did it got resolved on 2.0.1 ?
thanks
UPDATE : found the reason. I updated the database with the 'zabbix' user instead of the 'postgres' user. The patch creates a function using plpgsql and the zabbix user isn't allowed to do that. I made another upgrade using postgres user and things went fine.