On Tue, Dec 11, 2012 at 11:08 AM, Andy Parker <[email protected]> wrote: > That stacktrace is it trying to execute the start command for some service > and failing. It should be providing a message like "Could not #{type} > #{@resource.ref}: #{detail}". Do you get anything like at in the logs?
Yes I do. In fact, let me do a couple more runs on a 100% clean VMs so that we can be certain that there's no interference from anything else. > Is your catalog maybe installing a new puppet package? That looks like the > puppet process is being sent the HUP signal. Nope. Nothing like that. And given that these are EC2 VMs I control 100% I doubt there's something else going on. But, as I said -- I'll do a couple more runs today to make 100% sure. Thanks for all your help so far! Thanks, Roman. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
