-
as seen on Server Fault
- Search for 'Server Fault'
I cannot seem to get monit status or other CLI commands to work.
I've built monit v5.8 to run on a Raspberry Pi. I'm able to add services to be monitored, and the web interface can be accessed just fine, as I've set it up for public read-only access (it's a test server, not my final production…
>>> More
-
as seen on Server Fault
- Search for 'Server Fault'
I am trying to configure Monit on my local machine to get a taste at how it works, but I have some issues.
What I am trying to do is to get any evidence that Monit is up and running correctly and is actually monitoring something. So my /etc/monit/monitrc looks like
set daemon 60
set logfile /var/log/monit…
>>> More
-
as seen on Server Fault
- Search for 'Server Fault'
after installing monit when i do monit status myproc i get "error connecting to the monit daemon"
I read somewhere that
The status command won't work in the
case that monit is running indaemon
mode without its http support - the
command 'monit status' in such case
tries to get the status…
>>> More
-
as seen on Server Fault
- Search for 'Server Fault'
I have two identical EC2 instances (the second is a replica of the first), running Gentoo.
The first instance has monit running which monitors a single process and some system resources and functions great.
In the second instance, monit runs but quits right away.
The configuration is similar on both…
>>> More
-
as seen on Server Fault
- Search for 'Server Fault'
I just don't get it. monit behaves very strangely...
check process thin with pidfile /var/run/thin.4567.pid
start program = "/srv/Pusher/server start"
stop program = "/srv/Pusher/server stop"
if failed host 127.0.0.1 port 4567 protocol http then restart
group server …
>>> More