Hello Wyatt,
I think I have ran into an issue with large structured facts. I posted a
new message about it, but I was wondering if you have a solution for large
partitions and disks facts? I am not sure what to do as I cannot disable
facts, and I have a large number of nodes. Your help is a
On 9/29/15 12:20 AM, Matt Jarvis wrote:
count | name
---+-
1 | macaddress_qvb34470225_cd
1 | mtu_qbr2fb476b3_ff
1 | speed_qvbfa2ec4e3_15
1 | macaddress_qvo547572f9_14
1 | speed_qvo2e200191_c0
1 | mtu_qbr5ea
count | name
---+-
1 | macaddress_qvb34470225_cd
1 | mtu_qbr2fb476b3_ff
1 | speed_qvbfa2ec4e3_15
1 | macaddress_qvo547572f9_14
1 | speed_qvo2e200191_c0
1 | mtu_qb
On 09/28/2015 10:39 AM, Wyatt Alt wrote:
On 09/28/2015 05:40 AM, Matt Jarvis wrote:
We seem to have hit a bit of an issue with puppetdb garbage
collection. Initial symptoms were exceptions in the puppetdb logs :
Retrying after attempt 6, due to: org.postgresql.util.PSQLException:
This connect
On 09/28/2015 05:40 AM, Matt Jarvis wrote:
We seem to have hit a bit of an issue with puppetdb garbage
collection. Initial symptoms were exceptions in the puppetdb logs :
Retrying after attempt 6, due to: org.postgresql.util.PSQLException:
This connection has been closed.
And on the postgre
We seem to have hit a bit of an issue with puppetdb garbage collection.
Initial symptoms were exceptions in the puppetdb logs :
Retrying after attempt 6, due to: org.postgresql.util.PSQLException: This
connection has been closed.
And on the postgres side :
LOG: incomplete message from clien
