Problem on CentOS with PaceMaker: certbot wants to gracefully restart Apache

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: certbot --apache certonly -d --tekst --redirect

It produced this output:
Action ‘graceful’ failed.
And that’s the problem i think. httpd is no longer controlled by systemctl manager anymore, but PaceMaker is holding it in control.

My web server is (include version): Apache 2.4

The operating system my web server runs on is (include version): CentOS 7.6

My hosting provider, if applicable, is: Prominic

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): Always the latest.

1 Like

Certbot’s Apache plugin probably can’t deal with your environment.

Better to use a more stateless approach to avoid stepping on Pacemaker’s feet:

certbot certonly -d --webroot -w /path/to/webroot \
--deploy-hook "pcs resource restart www-apache" --dry-run

Oh, wow… that looks good. I will try this asap when i get home from work.

1 Like

If this test works, you’ll also then want to remove the --dry-run so that you actually get your certificates in the future! :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.