Jira (PDB-4094) Investigate query unexpectedly returning 500
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4094 Investigate query unexpectedly returning 500 Change By: Robert Roland Assignee: Robert Roland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276170.153728876.22145.1573069261293%40Atlassian.JIRA.
Jira (PDB-4523) Consider running separate jvms during lein integration tests
Title: Message Title Robert Roland assigned an issue to Unassigned PuppetDB / PDB-4523 Consider running separate jvms during lein integration tests Change By: Robert Roland Assignee: Robert Roland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327424.1569880423000.22158.1573069261394%40Atlassian.JIRA.
Jira (PDB-4488) PuppetDB module uses deprecated http_instance method
Title: Message Title Robert August Vincent II commented on PDB-4488 Re: PuppetDB module uses deprecated http_instance method Austin Blatt – I tried the workaround you described by setting `puppetdb::strict_validation: false` in hiera, but the message persists. Should I also add the following to `/etc/puppetlabs/puppetdb/conf.d/config.ini` ? ``` [puppetdb] strict-validation = 0 ``` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321972.1566497006000.21623.1573053480516%40Atlassian.JIRA.
Jira (PDB-4579) Enable tcpKeepAlive on the postgres driver
Title: Message Title
Taylan Develioglu updated an issue
PuppetDB / PDB-4579
Enable tcpKeepAlive on the postgres driver
Change By:
Taylan Develioglu
Bringing down the network interface link on our the PostgreSQL server causes the connection pool to hold on to connections that were already closed on the database server for (what seems t oe to be) an infinite time.The network stack on the client is never notified these connections have been closed on the peer and PuppetDB's connection pool still believes they are active.This caused us to run out of available connections in the connection pool until restarting PuppetDB. The PDBReadPool_pool_ActiveConnections metric also reports a value of 25 (maximum-pool-size). Can the tcpKeepAlive option of the PostgreSQL JDBC driver be enabled to prevent this class of issue from happening ? h5. Network link going down on the PostgreSQL server {code:java}[di nov 5 12:49:51 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:03 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none[di nov 5 12:55:09 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:10 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none[di nov 5 12:55:11 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:13 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none{code} h5. Connections still in ESTABLISHED state on the client side {code:java}[root@puppetdb ~]# netstat -ntp|grep 10.197.29.74:5432tcp6 0 0 10.198.174.11:39186 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:59996 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:50380 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:60952 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:33536 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:60902 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:35564 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:57950 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:45416 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:33644 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:39678 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:43846 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:55738 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:58098 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:34214 10.197.29.74:5432 ESTABLISH
Jira (PDB-4579) Enable tcpKeepAlive on the postgres driver
Title: Message Title
Taylan Develioglu updated an issue
PuppetDB / PDB-4579
Enable tcpKeepAlive on the postgres driver
Change By:
Taylan Develioglu
Bringing down the network interface on our PostgreSQL server causes the connection pool to hold on to connections that were already closed on the database server for (what seems t oe be) an infinite time.The network stack on the client is never notified these connections have been closed on the peer and PuppetDB's connection pool still believes they are active.This caused us to run out of available connections in the connection pool until restarting PuppetDB. The PDBReadPool_pool_ActiveConnections metric also reports a value of 25 (maximum-pool-size). Can the tcpKeepAlive option of the PostgreSQL JDBC driver be enabled to prevent this class of issue from happening ? h5. Network link going down on the PostgreSQL server {code:java} [di nov 5 12:49:51 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:03 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none[di nov 5 12:55:09 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:10 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none[di nov 5 12:55:11 2019] bnx2x :37:00.0 eno1: NIC Link is Down[di nov 5 12:55:13 2019] bnx2x :37:00.0 eno1: NIC Link is Up, 1 Mbps full duplex, Flow control: none{code} h5. Connections still in ESTABLISHED state on the client side {code:java} [root@puppetdb ~]# netstat -ntp|grep 10.197.29.74:5432tcp6 0 0 10.198.174.11:39186 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:59996 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:50380 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:60952 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:33536 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:60902 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:35564 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:57950 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:45416 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:33644 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:39678 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:43846 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:55738 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:58098 10.197.29.74:5432 ESTABLISHED 47079/java tcp6 0 0 10.198.174.11:34214 10.197.29.74:5432 ESTABLISHED 47079/java
Jira (PUP-3329) Puppet agent can't clear a stale agent_catalog_run.lock file
Title: Message Title Josh Cooper commented on PUP-3329 Re: Puppet agent can't clear a stale agent_catalog_run.lock file This was fixed in PUP-9247 and PUP-9691. Puppet now correctly takes ownership of stale lockfiles on posix and windows. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.52176.1411471145000.21571.1573051500729%40Atlassian.JIRA.
Jira (PUP-10120) resources cron purge fails if resource's name to be purged matches the title of a different resource
Title: Message Title Maximilian Philipps updated an issue Puppet / PUP-10120 resources cron purge fails if resource's name to be purged matches the title of a different resource Change By: Maximilian Philipps Summary: resources cron purge fails if resource's name to be purged matches the title of a different resource Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.333535.1572956409000.21508.1573036620618%40Atlassian.JIRA.
Jira (PUP-10120) resources cron purge fails resource's name to be purged matches the title of a different resource
Title: Message Title Maximilian Philipps commented on PUP-10120 Re: resources cron purge fails resource's name to be purged matches the title of a different resource hi, I can see how it is similiar to PUP-10118. Is the resource purge logic independent from the resource provider? I can't think of how a cron resource wouldn't be idempotent. Another thing to keep in mind, from what I recall the cron purge logic also isn't working correct for when a cron entry exists in the wrong cron user tab. I feel like the user value should be part of the namevar. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.333535.1572956409000.21505.1573036620600%40Atlassian.JIRA.
Jira (PUP-10057) User resource on Windows confuses domain and local accounts
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-10057 User resource on Windows confuses domain and local accounts Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327453.1569921077000.21465.1573033860248%40Atlassian.JIRA.
