https://bz.apache.org/bugzilla/show_bug.cgi?id=57360
--- Comment #1 from Michael Herold <[email protected]> --- I ran into the same problem on a production system. I did not expect apache2 to crash during a reload operation. Such behavior does not really help in expanding the adoption of encryption. With imminent automation through "Let's encrypt" this can even break systems without an admin directly being involved. However, I do get a syslog entry > [ssl:emerg] [pid 10249] AH02565: Certificate and private key 127.0.0.1:443:0 > from /etc/apache2/ssl/test.crt and /etc/apache2/ssl/test.key do not match with configured "ErrorLog syslog:user". But I think that "emergency" is _not_ the correct severity level. Possible Solutions (without knowing if it is technically feasible): 1. Catch the Openssl signal and disable vhost and log 2. Catch the Openssl signal and recover with emergency key and certificate (config values) and log, disable vhost if emergency key/cert are not available or cause error with openssl 3. Involve Openssl in the configtest and let reload fail if there is any kind of cert problem -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
