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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
not the problem, I need to protect my customer
I ran this command:
certbot --apache -d www.domain.tld -d domain.tld
It produced this output:
all fine
My web server is (include version):
httpd-2.4.6-93.el7.centos.x86_64
The operating system my web server runs on is (include version):
CentOS 7
My hosting provider, if applicable, is:
me
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): 1.4.0
Hi,
I’m running a two node cluster on corosync pacemaker and all worked fine until I used the certbot to use https for two of my domains on this machine. The certbot install and afterwards the implementation/configuration of the two domains worked like a charm. But now the pacemaker is not longer able to detect if the apache is running or not. As far as I know it uses the apache status-page which is extra for this purpose configured:
Listen 127.0.0.1:8089
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 127.0.0.1
Log of the cluster:
Jul 6 16:55:18 bachi2 apache(apache)[7182]: INFO: waiting for apache /etc/httpd/conf/httpd.conf to come up
Jul 6 16:55:19 bachi2 apache(apache)[7182]: INFO: apache not running
Jul 6 16:55:19 bachi2 apache(apache)[7182]: INFO: waiting for apache /etc/httpd/conf/httpd.conf to come up
Jul 6 16:55:20 bachi2 apache(apache)[7182]: INFO: apache not running
Jul 6 16:55:20 bachi2 apache(apache)[7182]: INFO: waiting for apache /etc/httpd/conf/httpd.conf to come up
Jul 6 16:55:21 bachi2 lrmd[8756]: warning: apache_start_0 process (PID 7182) timed out
Jul 6 16:55:21 bachi2 lrmd[8756]: warning: apache_start_0:7182 - timed out after 40000ms
Jul 6 16:55:21 bachi2 crmd[8759]: error: Result of start operation for apache on bachi2: Timed Out
Jul 6 16:55:21 bachi2 apache(apache)[8416]: INFO: apache is not running.
All is working perfectly when the apache is not controlled by the cluster.
The resource is configured like this:
Resource: apache (class=ocf provider=heartbeat type=apache)
Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://127.0.0.1:8089/server-status
Operations: start interval=0s timeout=40s (apache-start-interval-0s)
stop interval=0s timeout=60s (apache-stop-interval-0s)
monitor interval=1min (apache-monitor-interval-1min)
Any suggestions are welcome
Kind regards
fatcharly