I noticed that a number of my Windows hosts had stopped dialing in, and upon closer inspection I found that Puppet was crashing in Ruby and wevtapi.dll. I can't find any reference to this in the issue tracker, although I've got over a dozen occurrences in my environment, all with the same descriptions as below. I checked to see if the times were similar, in case the server presented some bad data to cause the issue, but the crashes occurred at all different times and days.
My question is, has anyone else seen this? Is this a known issue? If it is fixed in 3.2.1, can I install 3.2.1 clients against a 3.1.x server? In the meantime, I will be rolling back to an older 2.7.x version that we'd run for some time without issue. Thanks in advance. Fault details below. Faulting application name: ruby.exe, version: 1.8.7.371, time stamp: 0x5083a46c Faulting module name: wevtapi.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bdb2d Exception code: 0xc0000005 Fault offset: 0x00001360 Faulting process id: 0xa48 Faulting application start time: 0x01ce5e0840c39580 Faulting application path: C:\Program Files (x86)\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe Faulting module path: C:\Windows\system32\wevtapi.DLL Report Id: 487d9720-c9fc-11e2-8a25-0a252c8f038f -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
