Description of problem: If running the distributed monit, it checks process name instead of pid file, and thus creates a problem when trying to run a sandboxed version. See example below. If monit minded the pid instead of the process name, as it does in certain other distros, this would not be a problem. How reproducible: Fully reproducible Steps to Reproduce: After a first boot, monit is running: Sandbox Server [root.179.24:~] # ps uxaww|grep monit root 1665 0.0 0.0 13396 1148 ? Sl 18:52 0:00 /opt/rightscale/sandbox/bin/monit -c /opt/rightscale/etc/monitrc root 2580 0.0 0.0 1856 508 pts/0 R+ 18:53 0:00 grep monit Sandbox Server [root.179.24:~] # yum install monit Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * addons: ec2-us-east-mirror1.rightscale.com * base: ec2-us-east-mirror1.rightscale.com * centosplus: ec2-us-east-mirror1.rightscale.com * epel: ec2-us-east-mirror1.rightscale.com * extras: ec2-us-east-mirror1.rightscale.com * rightscale-epel: ec2-us-east-mirror1.rightscale.com * updates: ec2-us-east-mirror1.rightscale.com rightscale-epel | 951 B 00:00 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package monit.i386 0:4.10.1-8.el5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================================================================================ Package Arch Version Repository Size ============================================================================================================================================================================================================================ Installing: monit i386 4.10.1-8.el5 epel 233 k Transaction Summary ============================================================================================================================================================================================================================ Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 233 k Is this ok [y/N]: y Downloading Packages: monit-4.10.1-8.el5.i386.rpm | 233 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : monit 1/1 Installed: monit.i386 0:4.10.1-8.el5 Complete! Sandbox Server [root.179.24:~] # ps uxaww|grep monit root 1665 0.0 0.0 13396 1148 ? Sl 18:52 0:00 /opt/rightscale/sandbox/bin/monit -c /opt/rightscale/etc/monitrc root 2601 0.0 0.0 1856 556 pts/0 S+ 18:54 0:00 grep monit Sandbox Server [root.179.24:~] # service monit restart Shutting down monit: [ OK ] Starting monit: [ OK ] If one runs a "monit restart", the sandbox'd version gets killed. Sandbox Server [root.179.24:~] # ps uxaww|grep monit root 2619 0.0 0.0 5900 1032 ? S 18:54 0:00 monit root 2622 0.0 0.0 1852 512 pts/0 S+ 18:54 0:00 grep monit Sandbox Server [root.179.24:~] # ps uxaww|grep monit root 2619 0.0 0.0 5900 1032 ? S 18:54 0:00 monit root 2624 0.0 0.0 1852 512 pts/0 S+ 18:54 0:00 grep monit
monit-4.10.1-9.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/monit-4.10.1-9.el5
Sorry, I missed this bug. I've put an updated version out, can you please test it and give it karma if it works for you. If you are still interested in getting this fixed, that is.
Package monit-4.10.1-9.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing monit-4.10.1-9.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6384/monit-4.10.1-9.el5 then log in and leave karma (feedback).
monit-4.10.1-9.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.