Thanks Wyatt,
I have sent the tarballs from a couple of instances where we are seeing
this to your inbox.
Cheers
Paul
On Friday, 21 November 2014 17:32:16 UTC, Wyatt Alt wrote:
>
> Manually deleting that row (id=22128) in fact_values might also do the
> trick if it's only one affected node/val
Manually deleting that row (id=22128) in fact_values might also do the
trick if it's only one affected node/value, but wouldn't tell much about
how you got to this state so could be leaving something broken. It would
be interesting to get the discarded tarball in any case.
On Fri, Nov 21, 2014 at
Paul,
Thanks for that. It looks like 22128 has not been cleaned up properly
for some reason, and it's likely being skipped over in the gc process
because the facts cleanup identifies values to delete from that column
in the facts table.
Are there failed commands in your /var/lib/puppetdb/mq/
On Wednesday, 19 November 2014 17:56:23 UTC, Wyatt Alt wrote:
>
> Hey Paul,
>
> That's some kind of DB corruption. Shouldn't be happening. Do you have
> any sense of when this started or whether it was tied to a recent
> upgrade? Is there a stacktrace in your logs that you could gist? Does it
Hey Paul,
That's some kind of DB corruption. Shouldn't be happening. Do you have
any sense of when this started or whether it was tied to a recent
upgrade? Is there a stacktrace in your logs that you could gist? Does it
happen on every agent run or only occasionally? Is it always the same
pat
Hello,
Getting a couple of errors thrown with PuppetDB
2014-11-19 08:03:49,120 ERROR [c.p.p.command]
[22329b48-7c20-4ec4-beb2-15cd02e11bff] [replace facts] Retrying after
attempt 8, due to: org.postgresql.util.PSQLException: ERROR: update or
delete on table "fact_paths" violates foreign key co
