I think I'm past that version already: # rpm -qa | grep puppet puppetdb-1.6.3-1.el6.noarch puppet-3.5.1-1.el6.noarch puppet-server-3.5.1-1.el6.noarch vim-puppet-2.7.20-1.el6.rf.noarch puppetlabs-release-6-10.noarch puppetdb-terminus-1.6.3-1.el6.noarch
On Saturday, April 26, 2014 7:44:43 AM UTC-7, Ken Barber wrote: > > Sorry, the URL for the Puppet bug is really here: > https://tickets.puppetlabs.com/browse/PUP-1524 > > On Sat, Apr 26, 2014 at 3:44 PM, Ken Barber > <k...@puppetlabs.com<javascript:>> > wrote: > > It sounds like this Puppet bug: > https://tickets.puppetlabs.com/browse/PDB-349 > > > > You can usually solve this by upgrading to Puppet 3.4.3. > > > > ken. > > > > On Sat, Apr 26, 2014 at 3:39 PM, JonY <ethr...@gmail.com <javascript:>> > wrote: > >> 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 puppet-users...@googlegroups.com <javascript:>. > >> 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. > -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8fb6f967-8d30-479b-a86d-47c1b01ad55b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
