On Mon, Sep 3, 2012 at 2:07 AM, David Schmitt <da...@dasz.at> wrote: > On 03.09.2012 09:45, Jan Ziegler wrote: >> >> 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. > > > > 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.
Did this issue get resolved? If not, what did --evaltrace show? Are you managing file owner and group? Josh -- Josh Cooper Developer, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
