Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I’ve following this article but I’m getting an “Execution failed” status for apache. It doesn’t look like the PID file exists in: /usr/local/apache/logs/httpd.pid
(Ubuntu 12.04)
There was a typo in the configuration. I have corrected it, please let me know if you continue having issues.
Hi.
I installed monit as above on 12.04 & it’s running but I get this (names changed to protect the innocent):
`$ ps aux | grep monit root 1193 0.0 0.0 5492 832 ? S Sep12 1:27 /usr/bin/monit -c /etc/monit/monitrc fubar 12127 0.0 0.0 4372 812 pts/1 S+ 02:05 0:00 grep --color=auto monit
$ sudo monit status [sudo] password for fubar: monit: error connecting to the monit daemon`
I’ve checked /etc/monit/monitrc & it looks good enough to get things going & as seen above I think it’s running…
Any help appreciated
sorry to answer my own question but in order to get rid of that error message & see monit’s status, I had to enable the httpd section in /et/monit/monitrc even though I wasn’t using the web interface (apparently you have to set the monit httpd process to allow connections from localhost).
Hope this helps someone else late at night while searching Google (it’s 02:42 in London ;-)
I have followed this tutorial and I keep getting this message:
monit: activation failed – There is no service by that name monit: activation failed – There is no service by that name
I copied and pasted the congfig for apache and mysql and tried again and still got the same messages.
do you have any ideas about what I have done wrong.
Excellent article, got a test forum running on Digital Ocean in around 1h and used this command to keep thin running after the terminal window closes which I found useful:
thin start -d
macrus.hann6: after your make changes to the config file, don’t forget to run $ monit reload. Also make sure the actual pid files exist at that location.
When I login as a user and run Monit I get “monit: The control file ‘/etc/monit/monitrc’ must be owned by you.”
The file is owned by root, and when I login as root and run monit nothing happens.
So then I change the file to be owned by the user and then get “monit: Error opening the log file ‘/var/log/monit.log’ for writing – Permission denied”
After changing the owners on a lot of files eventually I don’t get any errors, and I also don’t see Monit.
Running monit status gives me “monit: error connecting to the monit daemon”
I am puzzled.
I’m experiencing some troubles with firewall configuration for the web access. i’ve set firewall as described here: https://www.digitalocean.com/community/articles/how-to-set-up-a-firewall-using-ip-tables-on-ubuntu-12-04
if i try to add sudo iptables -A INPUT -p tcp --dport 2812 -j ACCEPT (output too)
i’m unable to access. if i flush the firewall and remove all rules i’m able to access.
any idea? what i’m doing wrong?