D4Science Infrastructure

OK thanks. I'm going to run the playbook as requested

After the restart I see the same error on mongo2-d-d4s and mongo4-d-d4s

Roberto Cirillo wrote:

After the restart I see the same error on mongo2-d-d4s and mongo4-d-d4s

But mongodb on mongo1-d-d4s and mongo3-d-d4s was not restarted.

Andrea Dell'Amico wrote:

Roberto Cirillo wrote:

After the restart I see the same error on mongo2-d-d4s and mongo4-d-d4s

But mongodb on mongo1-d-d4s and mongo3-d-d4s was not restarted.

You are right. After the restart it works properly.

Andrea Dell'Amico wrote:

On the other mongo instances is installed the wrong hook script too.
A recap: mongodb does not support a service reload, so after a certificate change a restart is required. The cron job that renews the certificates runs at different times on the various servers to avoid downtimes.

So we should manually restart the production instances after the certificate renew?

Roberto Cirillo wrote:

Andrea Dell'Amico wrote:

On the other mongo instances is installed the wrong hook script too.
A recap: mongodb does not support a service reload, so after a certificate change a restart is required. The cron job that renews the certificates runs at different times on the various servers to avoid downtimes.

So we should manually restart the production instances after the certificate renew?

After you run the playbook as indicated above, the mongo servers will be restarted by the letsencrypt hook itself.