I installed monit on IPFire. There was no previous pakfire monit installed. [root@ipfireAPU ~] # /etc/rc.d/init.d/monit start Starting monit... /etc/monitrc:251: Include failed -- No such file or directory '/etc/monit.d/*' Starting Monit 5.33.0 daemon with http interface at [localhost]:2812 [ OK ] [root@ipfireAPU ~] #
Funny that this didn't came up before. It seems like you and I are the only ones using 'monit' this way... ;-) => https://lists.ipfire.org/pipermail/development/2023-August/016318.html
it *may* have happened when I started using monit. I was probably to new to understand! Thank you!
I am using monit and I just checked by stopping and restarting monit and I don't see that error message. I have the directory /etc/monit.d/ but there is nothing in the directory. In the monitrc at the end I have the line include /etc/monit.d/*
I checked back to an actual reboot and the monit message i9s the same as for stopping and starting it with the services table. So I( don't see what you see. Not sure what I am doing different. I am only using it to monitor IPFire at the moment so not a lot of monitoring options set.
for me this was a fairly new IPFire install. And then I installed monit for the first time on Aug 15.
I think I installed monit more than a year ago. I probably saw the error message about a missing /etc/monit.d/ directory and as monit is a console program I probably just created the missing directory myself and didn't think anything further about it.
Because it just came to my mind: How do we ship this fix for existing 'monit'-installations? Something like this in 'update.sh'? ... # Create missing 'monit.d'-directory if [ -f /usr/bin/monit.rc ]; then mkdir -p /etc/monit.d fi ...
Sorry, typo! I meant: # Create missing 'monit.d'-directory if [ -f /usr/bin/monit ]; then mkdir -p /etc/monit.d fi ...
This sounds OK to me. But honestly I'd rather have one of the Developers chime in...
this works for me.