Need some help on how to recover from a problem. Not a fatal one at this point, although I am concerned it might become one over time.
I recently migrated my Zabbix server to a new virtual machine running under VMware. That server is CentOS 5.7 running Zabbix 1.8.7 on MySQL 5.077. I performed the migration by first restoring the MySQL database from the physical server (same MySQL version but Zabbix 1.8.2), then running replication until I was ready to perform a flash cut over. At cutover I made the new DB the master and dropped the slave.
Most everything seems to work as expected. However, I get errors about a duplicate on profileid when accessing some pages with the Zabbix frontend. These errors are not fatal and data is presented normally. When I examine the profiles table, I find that profileid is no longer an autoimcrement value. I suspect the same may be true for other tables that have an autoimcrement primary key.
I've seen several references to this error in Google, but I've not found a single fix listed. In one case, it appears that this problem occurred with an older 4.x version of mysqldump. I suspect the restore from the dump was how my problems started. But again, even in that thread no fix is listed.
Can anyone provide me with some guidance on identifying all of the autoincrement primary fields that should exist in 1.8.7 and advice on how to go about fixing those columns? I know how to do this if it is only the profileid column in profiles. But my concern is that are many others that are incorrect (and those are the ones I worry about breaking things). Is there a way I can quickly identify all primary keys that should be autoincrmement and fix them?
Thanks.
I recently migrated my Zabbix server to a new virtual machine running under VMware. That server is CentOS 5.7 running Zabbix 1.8.7 on MySQL 5.077. I performed the migration by first restoring the MySQL database from the physical server (same MySQL version but Zabbix 1.8.2), then running replication until I was ready to perform a flash cut over. At cutover I made the new DB the master and dropped the slave.
Most everything seems to work as expected. However, I get errors about a duplicate on profileid when accessing some pages with the Zabbix frontend. These errors are not fatal and data is presented normally. When I examine the profiles table, I find that profileid is no longer an autoimcrement value. I suspect the same may be true for other tables that have an autoimcrement primary key.
I've seen several references to this error in Google, but I've not found a single fix listed. In one case, it appears that this problem occurred with an older 4.x version of mysqldump. I suspect the restore from the dump was how my problems started. But again, even in that thread no fix is listed.
Can anyone provide me with some guidance on identifying all of the autoincrement primary fields that should exist in 1.8.7 and advice on how to go about fixing those columns? I know how to do this if it is only the profileid column in profiles. But my concern is that are many others that are incorrect (and those are the ones I worry about breaking things). Is there a way I can quickly identify all primary keys that should be autoincrmement and fix them?
Thanks.