Hi all,

Ran into a weird problem today.  Puppet's been working in a non-daemonized 
environment for several weeks now without issue.  We regularly run puppet with 
the --onetime flag to update our environment.

This is running on Centos 6.2.  Catalogs have been compiling in 1 - 5 seconds 
generally, and today, it's intermittently taking anywhere from 100 seconds to 
timing out.

I've attempted to delete the yaml files and to restart the puppet master 
process.

Restarting the process works for a few minutes, and then the timeouts begin 
again.

Here's an example:

Jul  6 11:52:58 admin2 puppet-master[5420]: Starting Puppet master version 
2.7.17
Jul  6 11:53:13 admin2 puppet-master[5420]: Compiled catalog for 
queue2.prod.keek.com in environment production in 1.12 seconds
Jul  6 11:57:45 admin2 puppet-master[5420]: Compiled catalog for 
queue2.prod.keek.com in environment production in 214.36 seconds
Jul  6 12:01:37 admin2 puppet-master[5420]: Caught TERM; calling stop
Jul  6 12:01:41 admin2 puppet-master[5536]: Reopening log files
Jul  6 12:01:41 admin2 puppet-master[5536]: Starting Puppet master version 
2.7.17
Jul  6 12:01:52 admin2 puppet-master[5536]: Compiled catalog for 
queue2.prod.keek.com in environment production in 1.08 seconds

Compiling it by hand from the master always finishes quickly.

This is happening across the entire environment, multiple nodes, multiple 
different catalogs.

Help?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 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-users?hl=en.

Reply via email to