Hi everyone, thank R.I.P. for the pointers. I already planed to add more monitoring to ActiveMQ, so I'll take this as a chance. I dont think Amazon network settings are the root cause in my case, as I have registration agent enabled on all machines. This should keep the connection busy.
I filed a bug regarding the exit-code. Is there any chance the fix will make it in 1.2.2? Thanks, Jens -- Jens Bräuer Senior Systems Engineer Dipl. Inf. NumberFour AG Schönhauser Allee 8 10119 Berlin Germany Mobile: +49 175 221 88 34 Phone: +49 30 40505411 Fax: +49 30 40505410 j...@numberfour.eu numberfour.eu facebook.com/NumberFour twitter.com/numberfourag -- 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.