Re: Re: Auto-reload of configuration files

Sorry for the delayed reply, and thank you for the responses.

In my case, I had been running monit as a non-root user for testing.  I'll
try it out again as root when we come back around to it.

Thanks, and best regards
Eric





On Fri, May 29, 2020 at 3:12 AM Robert Ehrenleitner <[email protected]>
wrote:

> To add to @Lutz' response to make it somewhat more clear:
>
> What user is the process running with? "monit reload" must be executed
> with the same user, usually root. So, it is necessary to do "sudo monit
> reload" if you are not already root.
>
> Kind regards,
> rexkogitans
>
> *Gesendet:* Mittwoch, 27. Mai 2020 um 22:37 Uhr
> *Von:* "Lutz Mader" <[email protected]>
> *An:* "This is the general mailing list for monit" <
> [email protected]>
> *Betreff:* Re: Auto-reload of configuration files
> Hello Eric,
> are you using the command to reload in the same user context you used to
> start monit.
>
> > I didn't have luck calling 'monit reload' from within monit.
>
> All the time I try to reload the configuration from a different user, I
> get an error message (I use MacOS).
>
> Reinitializing monit daemon
> Cannot signal the monit daemon process -- Operation not permitted
>
> With regards,
> Lutz
>
>