Quote:
Originally Posted by phoenix  What release of Zimbra are you using and which operating system? |
Yes, I should've posted that in the OP, hehe. It's Zimbra 4.5.9 GA, and the OS is Fedora 7.
Quote:
Originally Posted by phoenix I think that sudo may have some problems, try the following format for the command (using su - ): Code: su - zimbra -c "zmcontrol start" |
I altered the script to use the su command you suggested above and it appears to start correctly now.
Although check a further comment below about it.
Quote:
Originally Posted by dwmtractor although zmcontrol status showed all the modules running, the web UI shows red "X" by Spell, SNMP, MTA, and Antivirus as well as Status. Just going from root to su - zimbra and then running zmcontrol stop & start, and the only red X is by Status. I don't know why, or even where to look to find out why, but if I had to guess I wonder whether running the whole command from root results in some odd file permissions issues.
? |
I actually got that issue a few times running the new script too. At one stage only the logger and ldap modules were running according to the admin console, but zmcontrol status said they're all up and running which is odd. I restarted the PC and the script seems to be behaving itself at the moment.
PS On a side note, dwmtractor, for your bash backup script it may be better if you have the rsync lines include the --delete parameter. At the moment it'll backup the zimbra folder into a backup folder then compress that folder into a tarball. The next time the script runs it'll just keep adding and updating new files to the backup folder without deleting old files/folders, which could cause junk to build up over time?
Including the --delete option in the command gets rid of files in the destination folder that don't exist at the source.