Waiting is ok. You might be able to find the node associated to one of the failing catalogs in the log. You could then either force a puppet run and grab the failed message or look in your puppet cache (in client_data/catalog on the master).
-Ryan On Tue, Nov 11, 2014 at 4:32 PM, Christopher Wood < christopher_w...@pobox.com> wrote: > Embarrassingly, due to disk space issues I purged rather than moved and > don't see any files full of json under /var/lib/puppetdb per the catalog > wire format v5. If you have a hint as to how I might get one I will do > that, otherwise I will send you one as soon as it turns up. > > On Tue, Nov 11, 2014 at 03:25:21PM -0500, Ryan Senior wrote: > > Could you send me one of that catalog commands that is triggering this > > error? You should be able to find this in your mq directory that you > > purged earlier. The contents should look like [1]this. If you'd > rather not > > post the catalog publicly, you can send it to me directly. > > -Ryan > > On Tue, Nov 11, 2014 at 9:13 AM, Christopher Wood > > <[2]christopher_w...@pobox.com> wrote: > > > > Do any of you have troubleshooting tips for the puppetdb error log > > message about violating database constraints? How would I tell which > > constraint and which resource, short of logging all sql queries? > > > > 2014-11-11 08:29:34,814 ERROR [c.p.p.command] > > [6133d0c4-3350-4567-abb0-476980a9616e] [replace catalog] Retrying > after > > attempt 4, due to: org.postgresql.util.PSQLException: ERROR: > duplicate > > key value violates unique constraint "resource_params_pkey" > > > > The full error: > > [3]https://gist.github.com/anonymous/3a169a2b9380196983c6 > > > > More details... > > > > Per our logs, we've been seeing this with puppetdb 1.6.3 and 2.2.2. > > > > So far I've tried, with little success: > > > > -raising the storage log level to debug > > -digging through /var/log/puppetdb/puppetdb.log before/after debug; > > couldn't see a pattern > > -stop puppetdb, purge files under /var/lib/puppetdb/mq, start > puppetdb; > > to start clean and see if maybe something was corrupt/cached, but > didn't > > help > > > > The kahadb page: > > > > [4] > https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.html > > > > We rebuild preprod machines at intervals and we do use some exported > > resources but I'd like to know what's happening before I start > firing > > off "puppet node deactivate randomhost" until the problem fixes > itself. > > > > [5] > https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ > > > > Logging all sql queries: > > > > [6] > http://stackoverflow.com/questions/722221/how-to-log-postgres-sql-queries > > > > The stack: > > > > java 1.7.0 openjdk > > postgresql 8.4 (it came with CentOS) > > puppet 3.7.2 puppetmasters and on puppetdb host, but 3.6.2 on most > nodes > > puppetdb 2.2.2 > > puppetdb-terminus 2.2.2 on all puppetmasters > > -- > > 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 [7]puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > [8] > https://groups.google.com/d/msgid/puppet-users/20141111141320.GA6861%40iniquitous.heresiarch.ca > . > > For more options, visit [9]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 [10]puppet-users+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > [11] > https://groups.google.com/d/msgid/puppet-users/CAGDMwd3nS%3D7LG2_Cv7nQ0sOoUXvRkcYrvqjF6gN0NtmhR%2BeZZw%40mail.gmail.com > . > > For more options, visit [12]https://groups.google.com/d/optout. > > > > References > > > > Visible links > > 1. > https://docs.puppetlabs.com/puppetdb/2.2/api/wire_format/catalog_format_v5.html > > 2. mailto:christopher_w...@pobox.com > > 3. https://gist.github.com/anonymous/3a169a2b9380196983c6 > > 4. > https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.html > > 5. > https://ask.puppetlabs.com/question/88/how-can-i-purge-exported-resources-from-puppetdb/ > > 6. > http://stackoverflow.com/questions/722221/how-to-log-postgres-sql-queries > > 7. mailto:puppet-users%2bunsubscr...@googlegroups.com > > 8. > https://groups.google.com/d/msgid/puppet-users/20141111141320.GA6861%40iniquitous.heresiarch.ca > > 9. https://groups.google.com/d/optout > > 10. mailto:puppet-users+unsubscr...@googlegroups.com > > 11. > https://groups.google.com/d/msgid/puppet-users/CAGDMwd3nS%3D7LG2_Cv7nQ0sOoUXvRkcYrvqjF6gN0NtmhR%2BeZZw%40mail.gmail.com?utm_medium=email&utm_source=footer > > 12. 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/CAGDMwd1VkTLqr4UT70ESRTkb4BqDa_0afD2-1r47fGw91nRPTA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
