Hello all,

We are running Puppet 4.2.2 and PuppetDB 3.2.0 with around 2400 nodes and 
growing.  I am noticing some bad behavior with our PuppetDB, which is only 
going to get worse if what is below is correct.  I see the error below in 
the puppetdb log.

* ERROR [p.p.mq-listener] [cfe52545-29f8-4538-bf32-6ed41922be90] [replace 
facts] Retrying after attempt 8, due to: org.postgresql.util.PSQLException: 
This connection has been closed.*
*org.postgresql.util.PSQLException: This connection has been closed.*


I see this in the postgres log

*incomplete message from client*

and I can see the command queue jumping up after the connection has been 
reset for obvious reasons.  

I searched around and found this article.

https://groups.google.com/forum/#!topic/puppet-users/o_4K-UcuTQQ

I can see that this may be causing the issue I am seeing as we have several 
large array-valued structured facts. 


* count |                name*
*-------+------------------------------------*
* 26848 | partitions*
* 26014 | disks*
*  6141 | mountpoints*
*   494 | networking*
*   133 | processors*
*    22 | os*
*    15 | memory*
*    14 | dmi*
*    13 | ssh*
*     9 | dhcp_servers*
*     5 | system_uptime*
*     5 | identity*
*     4 | ruby*
*     4 | load_average*s



I can't get rid of these facts out of the box.  There doesn't seem to be 
anyway to filter facts, which is what it appears I need to do.  This fact 
also clutters PuppetBoard heavily.  Anyone ran into this issue before and 
found a way around it, or how to fix it?  Thanks in advance,

Mike




-- 
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/5e503d08-ee8b-426b-81a7-ae06e06b01c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to