Starting and stopping zimbra through ssh doesn't always work

[timwiel]

Hi

We are running several instances (for different clients) Open Source zimbra and one network edition zimbra.

We have a dedicated backup server than runs the backups (including other directories on those servers) as described in the open source back procedure (allbeit slightly modified).

All the zimbra versions are in the 5.0.XX version series.

The modified backup script is a bashscript run on a crontab job from the back server.

Basically the zimbra portion of the backups run a hot sync of zimbra using rsync as such:

rsync -avzHkh --delete --progress --inplace <root>@<remote_host>:/opt/zimbra /<path_to_local_backup_of_zimbra>/

then the backup scripts calls

ssh <root>@<remote_host> sudo -u zimbra /opt/zimbra/bin/zmcontrol stop

then the script cold syncs then we restart the zimbra using

ssh <root>@<remote_host> sudo -u zimbra /opt/zimbra/bin/zmcontrol start

This is where the problem is - sometimes zimbra doesn't always come back up and ssh'ing into the server and running zmcontrol restart as zimbra locally on the machine always fixes the problems.

There are two zimbra's that never restart the logger process and I have to log in and run:

zmswatchctl start
zmloggerctl start

for all the zimbra processes to be up and going again.

Is running ssh <root>@<remote_host> sudo -u zimbra /opt/zimbra/bin/zmcontrol start a problem and if so how can it be fixed. Should I load this as a bug against zimbra.

[uxbod]

Which specific version of ZCS ? 5.0.14 (IIRC) had a logger issue then when running a zmcontrol stop some processes were left running. If indeed you are on this version then I would recommend upgrading.

[timwiel]

The server that has the problem not restarting properly is 5.0.11GA-FOSS on an ubuntu 8.04.2 LTS

[timwiel]

this problem also presents itself on the 5.0.13_GA_2791.UBUNTU8.FOSS server.
When running ssh root@<zimbra_server> sudo -u zimbra /opt/zimbra/bin/zmlogswatchctl start and we tail the log using tail -fn20 /opt/zimbra/log/zmlogswatch.out I get:

Can't locate Date/Parse.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /opt/zimbra/libexec/logswatch line 30.
BEGIN failed--compilation aborted at /opt/zimbra/libexec/logswatch line 30.

[gkra]

I'm having this same problem on 5.0.15 (NE, RHEL 5.3, 64-bit) right now. Whenever we reboot the server (i.e., kernel updates) the init script starts everything up just fine. Trying to use zmcontrol or zmlogswatchctl nets me the same perl module error in /opt/zimbra/log/zmlogswatch.out.

If I need to restart the Zimbra services, I'm finding that I have to use the init script instead of zmcontrol if I want it to reliably start up.

[phoenix]

The obvious answer would be the perl module isn't installed:

[SOLVED] logger & snmp not starting

[uxbod]

Though should that not be in the /opt/zimbra tree Phoenix ? It certainly is not specified as part of the prereqs in the documentation. As zmcontrol works when in a interactive shell then I think it is more to do with the environment. Could somebody post the following?

ssh <root>@<remote_host> sudo -u zimbra "env ; /opt/zimbra/bin/zmcontrol start"

[Brian.huang]

This is the command I used to start zimbra manually:
$sudo su zimbra -c "source /opt/zimbra/.bashrc ; /opt/zimbra/bin/zmcontrol start"
It worked for me.

[sikander]

Hello Brian,

If i tried to run this command given below. It is asking me for the password but not taking any password. Can you please give me idea which password it is asking to stop or start zimbra service.

$sudo su zimbra -c "source /opt/zimbra/.bashrc ; /opt/zimbra/bin/zmcontrol start"

Thanks,

Sikander

[Brian.huang]

Hello Brian,

If i tried to run this command given below. It is asking me for the password but not taking any password. Can you please give me idea which password it is asking to stop or start zimbra service.

$sudo su zimbra -c "source /opt/zimbra/.bashrc ; /opt/zimbra/bin/zmcontrol start"

Thanks,

Sikander

I don't use the user zimbra directly. The sudoer is the current user, not zimbra in this case. That is, you should enter the password of the sudoer. By the way, the prompt message should show the user name.