Issue #1709 has been updated by ssm.
I'll reproduce the problem in a lab setup, and gather some Useful Information. ---------------------------------------- Bug #1709: Using ldap provider on user and group types hangs puppetd on next run when ldap server restarts http://projects.reductivelabs.com/issues/show/1709 Author: ssm Status: Needs more information Priority: Normal Assigned to: community Category: LDAP Target version: unplanned Complexity: Unknown Affected version: 0.24.5 Keywords: node ldap user group h1. Environment The puppet nodes are using some local accounts, and some LDAP accounts. The "user" and "group" types detect a working LDAP setup, and select "ldap" as their provider. h1. Problem description When puppetd starts, it connects to the LDAP server, and keeps this TCP connection to the LDAP server open. If the LDAP server is restarted, the TCP connection between puppetd on each puppet node and the LDAP server is closed normally. On the next scheduled puppetd run, or if given a SIGUSR1 signal, puppetd will start working, and then hang. It will not respond to SIGTERM, but must be killed by SIGKILL. ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
