Puppet runs extremly slow on 1 of 18 Windows Server

[Jan Ziegler]

Hi,

We have 18 Windows Server in the same environment. All Windows Server are build with an individual Windows Image, we created before, which means, that all Windows Machines have the same configuration except ip/mac address and hostname.
17 of those Windows Server run Puppet within 120 seconds per run. But one of those Server took 49 hours for the run...the second one wasn't faster.

We already installed this machine from bottom up several times, to be sure, that this server has the same configuration as the other ones... but without success.

The last lines before it takes some hours are:

info: Loading facts in C:\...... and so on
info: Loading facts in C:\...... and so on
info: Caching catalog for windowstest.domain
info: Applying configuration version '1346550140'


Any idea why this machine is so slow? It uses the same puppet classes as the other 17 server.

[David Schmitt]

use --evaltrace to see which resources are evaluated. Maybe this gives
you a hint what's happening.

Since you seem to be pretty sure this is not a problem rooted in the
machine itself, the attentions focuses on the environment: Perhaps there
is an IP-collision with another device on the network? Perhaps the
switchport is faulty? The underlying virtualisation has something fishy
configured? The nameserver is acting up? etc.



Good hunting, D.

[Josh Cooper]

Did this issue get resolved? If not, what did --evaltrace show? Are
you managing file owner and group?

Josh

--
Josh Cooper
Developer, Puppet Labs

[Sean Wolf]

I ran into this same problem, and pe_compliance was the culprit-- took 120 seconds.  Removing this class from the default group and re-running puppet made it run quickly again.