Here is the problem. When I stop zimbra with,
su - zimbra
I get the following,
the MTA returns it failed to stop. But in /var/log/zimbra.log I get the following,
Jun 15 12:42:46 courriel zimbramon: 29471:info: Stopping mta
Jun 15 12:44:06 courriel zimbramon: 30161:info: 2006-06-15 12:44:01, STATUS: courriel.mydomain.ca: mta: Stopped
Jun 15 12:44:32 courriel zimbramon: 29636:info: Starting mta
Jun 15 12:46:06 courriel zimbramon: 31188:info: 2006-06-15 12:46:02, STATUS: courriel.mydomain.ca: mta: Running
so indeed, there is no problem. Then if I issue zmcontrol start, all is ok and the server works.
My problem with this is that when the zmcontrol script terminates it returns a false error code 1 to what ever called it instead of 0.
What I'm trying to do is to get zimbra backed up with bacula and get bacula to stop zimbra before the backup, back it up and then start zimbra.
I tested it in VMware on an the same os as what I have on the real server and it works perfectly. Zimbra is stoped and restarted by bacula flawlessly. But in VMware, I don't get the error that MTA failed to stop so zmcontrol returns a0 to bacula.
So How can I get zmcontrol to get the correct infos about the status of the MTA so that bacula will not cancel the job because it receaved an error message from the script used to stop zimbra?
Or how can I check if there is a real problem stopping the MTA?