Thanks for the quick reply! yes, I actually thought that feature got removed since it's not usuable and > never really worked at all. > > Don't use it. >
It seems to work okay most of the time, as far as I can tell. The trouble comes if it is used when the daemon is: 1) Still getting initialised 2) Trying to re-connect to the rabbitmq server. At either of those times, it seems unreliable. Do you have any suggestion for what we could do instead, to cause new agents to come into effect? We used "restart" in the past, but that caused other issues due to the way that in-flight RPC calls get discarded. If there were some way of detecting when the reload-agents doesn't work properly we could then re-try it. But I can't see a way of detecting the problem (except by looking for errors later on, which is hard to automate...) Again, thanks. -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/12327365-4d03-49c9-8f2c-e45b173bef00%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
