Zabbix 1.8.3 Postgres Failure

[anrstone]

We are running zabbix 1.8.3 with a postgres backend. The system is split so that we have a separate DB server, Zabbix Server and Zabbix web interface box. In terms of load we are collecting about 12000 parameters over 130 servers. What seems to happen is that all is fine for a few days and then we see a number of entries containing:

duplicate key value violates unique constraint "trends_uint_pkey"

After which the DB server then reports a number of fatal errors and the zabbix server though up is then unable to connect. The only fix is restarting the DB server and the Zabbix - which at 2 in the morning is starting to be pretty dull! To be be fair I cannot with any certainty confirm that this is always the message before the failure as the log files on days with a failure are huge...

Does anyone have any similar problems or ideas as to how we can stop this happening (i.e. "you've configured it all wrong and do this to fix it" - that would be great!)

Thanks

Nick

[anrstone]

So I'm not sure whether this is related but having read about postgres optimisation elsewhere I decided to dump and recreate the zabbix DB at which point I discoved that a few tables had duplicate entries which must have come in during the upgrade process from 1.6.

The offending tables where responsible for storing the ids for various functions and I'm speculating that as a result there appears to be insret issues throughout the logs (and probably data not been added). I have manually edited the tablesd (which I hope I've done correctly) and added the missing primary keys - I hope this will solve the issue....

Nick