Turns out to be a denial of service on a machine in the same subnet. Machine in question has been sequestered.
All of my puppet clients are hung. Fortunately there are only a few dozen as I'm having to touch each one, stop the puppet service, kill the hung process and rerun manually. On Monday, March 17, 2014 8:43:54 AM UTC-7, JonY wrote: > > Over the weekend there were some intermittent outages at our data center. > The puppet server would let clients connect but they would eventually time > out. > > Unf this timeout wasn't handled gracefully and the clients would hang. > Doing a 'ps -ax | grep puppet' would show the service and the 'puppet > agent: applying configuration'. No activity available in the message log > for many hours though which indicated an unhappiness. > > If I killed the process and did 'puppet agent --test --debug' I could see > it get to where it tried to download the configuration. Doing this > interactively it would exit properly. If I restarted the service it would > stop and hang there. > > Server: CentOS 6.4 (x64). > puppet 3.4.0 > apache 2 / Passenger > > Clients: Debian 6.x > puppet 3.4.0 > -- 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/eddc84e8-fd2b-4517-ace2-8a190c3819a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
