>
> it really doesn't, in ways you cant even see or debug and cannot work.
> Don't use it.
>
> Only option is to restart the daemon.
>
Okay, we'll just have to figure out a way to live with that, I guess.
Thanks.
--
This email and any files transmitted with it are confidential and intended
- Original Message -
> From: "Lorcan Hamill"
> To: "puppet-users"
> Sent: Thursday, November 19, 2015 10:41:34 AM
> Subject: Re: [Puppet Users] mcollective reload-agents unreliable?
> Thanks for the quick reply!
>
> yes, I actually though
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 initial
- Original Message -
> From: "Lorcan Hamill"
> To: "puppet-users"
> Sent: Wednesday, November 18, 2015 7:02:31 PM
> Subject: [Puppet Users] mcollective reload-agents unreliable?
> Is reload-agents known to be unreliable, if mcollective has lost its S
Is reload-agents known to be unreliable, if mcollective has lost its STOMP
connection?
Let me explain...:
When I run "/etc/init.d/mcollective reload-agents", it sends a USR1 signal
to mcollectived
to cause it to reload its agents.
Usually, this works fine. But if I do this when the mcollecti
