|Subject:||Re: Problem starting my monit|
|Date:||Sun, 13 May 2012 14:10:23 -0700|
I seem to recall that the 5.2 and 5.3 rpm's on repoforge pre 5.3.2-3 have some issues with the monit configuration file and creating the /var/monit directory. One of the versions would also erase your monit.conf files and reset it to defaults. The issues were fixed in monit-5.3.2-3.
However, I can understand if you are unable to update your monit agents to 5.3.2. To use the fixes that were applied in the -3 release of monit without updating your monit version you can grab the spec file on rpmforge from either the src rpm (monit-5.3.2-3.rf.src.rpm) or the github account (https://github.com/repoforge/rpms/blob/master/specs/monit/monit.spec). Once you have the patched spec file from the new version you can then just rebuild the rpm for monit-5.2 using the monit sources of 5.2. If you need help building an rpm fedora has a good article on the subject (http://fedoraproject.org/wiki/How_to_create_an_RPM_package#Building_the_binary_package).
When using the updated rpm spec file for monit-5.3.2-3 the config file will be /etc/monit.conf, the includes directory will be /etc/monit.d, and the init script will be /etc/init.d/monit. They are using those naming conventions for the conf, includes, and init files to adhere to the standards of RHEL, CentOS, and Scientific Linux.
On May 13, 2012, at 12:28 PM, Martin Pala wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|