zmcontrol restart stucked after renewing certificate about letsencrypt-zimbra HOT 6 CLOSED

Hi,

First of all, thanks for the project.

you are welcome. Nice to hear that.

As far I read, the script restarts the zimbra service.

Yes, the script should restart zimbra services when a cert is renewed.

1. What version of letsencrypt-zimbra tool are you using?

   /opt/letsencrypt-zimbra/obtain-and-deploy-letsencrypt-cert.sh -V
   

2. Is that problem occur only after renewing the cert? Or is it more often?
3. Are you able to receive e-mail notification about failed cron job? If so, the script should report any error via e-mail
4. It is possible to renew the cert manually by this command (do not do this during rush hours as it will restart zimbra service):

   sudo -iu zimbra /opt/letsencrypt-zimbra/obtain-and-deploy-letsencrypt-cert.sh -vf
   

   -f is to force-renew and -v is for verbose, so you will see detailed output what the script is doing.

Vojtech

from letsencrypt-zimbra.

Hi Vojtech,

I answer the questions:

1. The version used is letsencrypt-zimbra version 0.3

2. Just when renewing, yes. We monitor some parts of zimbra server, the certs durability and the queues, so it seems to happen when renewing the cert.

3. Not really or not easy to see, because when experiencing problems, email server does not recieve mails (until the manual zmcontrol restart). And later, I can see some zimbra-admin messages probably of the restarting tried by the script. Anyway, the cert is renewed.

4. I will take this into consideration for debugging. Thanks for the tip.

Kind regards.
--C.

from letsencrypt-zimbra.

Hello,

1. The latest version is 0.4.1 (I am just preparing 0.4.2). You should keep it up-to-date, although I see no changes relevant to your issue.
2. ok
3. I see. I should implement some logging feature to the script for such cases.
4. Let me know if you discover something new
   Vojtech

from letsencrypt-zimbra.

Thanks for the feedback Vojtech.
I updated the project, but I found no changes except version in shell script.

Kind regards.
--C.

from letsencrypt-zimbra.

I have added logging to syslog feature in #64. You can checkout the branch syslog and you will be able to see information messages in /var/log/syslog then (or /var/log/messages, depending on your syslog configuration).

It should help to isolate the problem.

from letsencrypt-zimbra.

Closing this as the thread seems to be dead.

Feel free to reopen if you have some new info about that.

from letsencrypt-zimbra.