In the next interval, monit automatically starts the cron daemon without the administrator interaction as shown in the syslog messages below.ĭec 5 13:06:55 (none) monit: 'crond' process is not runningĭec 5 13:06:55 (none) monit: 'crond' trying to restartĭec 5 13:06:55 (none) monit: 'crond' start: /etc/init.d/cronĭo a ps -ef to make sure the cron job is started automatically by monit, when you killed it. To test this, let us kill the running cron daemon as shown below. With pidfile PIDFILENAME-WITHABSOLUTE-PATHįor example, to monitor the cron daemon, append the following lines to the monitrc file.įor further configurations (for example, restarting a process when it crosses a memory or process limit), refer the HOW TO MONITOR section in “man monit”.Īlso, enable syslog by uncommenting the following line in /etc/monit/monitrc.Įdit the /etc/default/monit file and enable the start up flag, which ensures that the configuration is done so that monit can start. Configure monitĪ sample process monitoring entry in the monit configuration file /etc/monit/monitrc looks like the following. If your distribution don’t have the monit package, download monit source and install it. For example, on Debian (and Ubuntu), install monit using apt-get as shown below. On Fedora, openSUSE, Debian install monit as a package from the distribution repository. We also discuss a specific example related to processes monitoring. This article provides a jumpstart guide on monit installation and configuration. The MMonit package extends the basic (free) monit program by adding a central. Monit is an open source utility that provides several system monitoring functionality that are extremely helpful to sysadmins. You may then install mmonit on a central monitoring management server.