The same happened to me upon upgrading to 2.3.7. Truncating the icinga_endpointstatus fixed the issue.
Markus, the issue link you sent points to an unrelated issue... On Thu, Jul 16, 2015 at 11:05 AM, Markus Joosten <markus.joos...@plumbe.de> wrote: > Hi list, > > i just upgraded my central icinga2 instance to 2.3.7 and discovered that > my icinga2.log was showing a lot errors like this one: > > [2015-07-16 09:56:40 +0200] critical/IdoPgsqlConnection: Error "ERROR: > duplicate key value violates unique constraint "uq_endpointstatus" > DETAIL: Key (endpoint_object_id)=(2864) already exists. > " when executing query "INSERT INTO icinga_endpointstatus > (endpoint_object_id, identity, instance_id, is_connected, node, > status_update_time) VALUES (2864, E'my.satellite.1', 1, E'1', E'my.master', > TO_TIMESTAMP(1437033400))" > Context: > (0) Reconnecting to PostgreSQL IDO database 'ido-pgsql' > > [2015-07-16 09:56:40 +0200] warning/IdoPgsqlConnection: Exception during > database operation: Verify that your database is operational! > [2015-07-16 09:56:49 +0200] information/IdoPgsqlConnection: pgSQL IDO > instance id: 1 (schema version: '1.13.0') > > Icingaweb2 (which connects to the icinga2 instance via ido-pgsql) did not > update anymore of course. > > I was able to use the following workaround: > 1. tail -f /var/log/icinga2/icinga2.log > 2. delete the offending line from psql table icinga_endpointstatus > 3. repeat until no more errors appear in icinga2.log > > (dropping all lines in the table at once didn't work for me) > > To answer my own question, there is already a bugreport for this: > https://dev.icinga.org/issues/9436 > > Regards, > Markus > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users >
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
