FWIW: I tried to remove all the db files and restart in hopes of removing the constraint issue. It immediately came back so I'm assuming that this is a bug in the version of puppetdb I have installed (1.6.3.1)
On Saturday, April 26, 2014 6:03:22 AM UTC-7, JonY wrote: > > It seems that puppetdb has run itself into a corner. It starts (albeit > briefly) and then stops soon afterwards with this error: > > 2014-04-25 20:38:30,242 ERROR [command-proc-65] [puppetdb.command] > [6c141db1-eeac-4c3f-be08-d03e5f445a19] [store report] Retrying after > attempt 13, due to: java.sql.SQLIntegrityConstraintViolationException: > integrity constraint violation: unique constraint or index violation; > CONSTRAINT_RESOURCE_EVENTS_UNIQUE table: RESOURCE_EVENTS > java.sql.SQLIntegrityConstraintViolationException: integrity constraint > violation: unique constraint or index violation; > CONSTRAINT_RESOURCE_EVENTS_UNIQUE table: RESOURCE_EVENTS > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.JDBCPreparedStatement.fetchResult(Unknown > Source) > at org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate(Unknown > Source) > > .. lots more stack after that. > > > How do I go about cleaning this up? All of my agent processes are frozen. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/053ee518-b48f-44bb-b0e8-f68a09092fd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
