We have several RedHat systems that were patched this weekend where puppetd is quietly going away. I'm still gathering info, but all 64-bit RH 5 systems I've checked are OK, the failing systems seem to be limited to 32 bit systems but both RH4 and 5. We don't have many RH 4 systems left..
Puppet version is 25.5-1 Patches applied (from yum.log) Dec 19 00:13:48 Updated: krb5-libs-1.6.1-36.el5_5.6.i386 Dec 19 00:13:52 Updated: openssl-0.9.8e-12.el5_5.7.i686 Dec 19 00:13:53 Updated: 30:bind-libs-9.3.6-4.P1.el5_5.3.i386 Dec 19 00:13:54 Updated: openldap-2.3.43-12.el5_5.3.i386 Dec 19 00:13:57 Updated: nss_ldap-253-25.el5_5.3.i386 Dec 19 00:14:10 Updated: gtk2-2.10.4-21.el5_5.6.i386 Dec 19 00:14:13 Updated: augeas-libs-0.7.4-1.el5.i386 Dec 19 00:14:16 Updated: m2crypto-0.16-6.1.el5_5.1.i386 Dec 19 00:14:17 Updated: 30:bind-utils-9.3.6-4.P1.el5_5.3.i386 Dec 19 00:14:19 Updated: krb5-workstation-1.6.1-36.el5_5.6.i386 I ran puppetd -Ddv on a sample failing system and got these messages (host names xx'd): Dec 19 15:25:27 xxxxxxxxx puppetd[16494]: Finished catalog run in 3.15 seconds Dec 19 15:55:28 xxxxxxxxx puppetd[16494]: Caching catalog for tsm-admin-62.missouri.edu Dec 19 15:55:29 xxxxxxxxx puppetd[16494]: Applying configuration version '1292753209' Dec 19 15:55:31 xxxxxxxxx puppetd[16494]: Finished catalog run in 1.98 seconds Dec 19 16:25:33 xxxxxxxxx puppetd[16494]: Caching catalog for xxxxxxx Dec 19 16:25:34 xxxxxxxxx puppetd[16494]: nss_ldap: could not get LDAP result - Can't contact LDAP server So, at the next hour, puppet dies. We aren't trying to use LDAP with puppet as far as I know. Looking back in /var/log/messages to before the maintenance, I find similar, but non fatal errors: Dec 12 05:03:02 xx ruby: nss_ldap: could not get LDAP result - Can't contact LDAP server Dec 12 05:03:02 xx ruby: nss_ldap: reconnected to LDAP server ldaps://some-dc:3269 after 1 attempt Dec 12 05:03:17 xx nss_ldap: could not get LDAP result - Timed out Dec 12 05:33:24 xx ruby: nss_ldap: could not get LDAP result - Can't contact LDAP server Dec 12 05:33:24 xx ruby: nss_ldap: could not get LDAP result - Can't contact LDAP server Dec 12 05:33:24 xx ruby: nss_ldap: reconnected to LDAP server ldaps://some-dc:3269 after 1 attempt Dec 12 05:33:38 xx ruby: nss_ldap: could not get LDAP result - Timed out Dec 12 06:03:43 xx ruby: nss_ldap: could not get LDAP result - Can't contact LDAP server Dec 12 06:03:43 xx ruby: nss_ldap: could not get LDAP result - Can't contact LDAP server Dec 12 06:03:43 xx ruby: nss_ldap: reconnected to LDAP server ldaps://some-dc:3269 after 1 attempt The LDAP server is a Windows domain controller, ldap.conf has a list of several alternates. Any thoughts? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
