Re: [users@httpd] Failure to start apache2 after SSL cert update.

Thanks, Martin, Great advice! I have two virtual hosts. The certificate and key match on one of them but not on the other. The mismatched one is much less important so I guess I'll de-ssl it until I trace down the mismatch and redo the certificate/key. Thanks again, Jack

Re: [users@httpd] Failure to start apache2 after SSL cert update.

Jack, are you sure, the certificate and the key match up? You can do this by looking at the modulus, it must be the same. In OpenSSL this looks like 'openssl x509 -in [YOUR_CERT] -noout -modulus' respectively 'openssl rsa -in [YOUR_KEY] -noout -modulus'. You may pipe this through 'openssl md5'

Re: [users@httpd] Failure to start apache2 after SSL cert update.

After more searching I find that loadmodule.conf calls for loading the mod_socache_shmcb.so module during pre-fork. However, the ssl-global.conf file calls for mod_socache_shmcb.c. Is the source file call rather than the executable that's causing the misconfiguration message? Should I just comme

Re: [users@httpd] Failure to start apache2 after SSL cert update.

I set the error level to debug in vhosts.conf, tried a restart and got this from yesterday; nothing from today. [Fri Jul 10 09:47:37.657510 2020] [mpm_prefork:notice] [pid 7681] AH00173: SIGHUP received. Attempting to restart [Fri Jul 10 09:47:37.899186 2020] [ssl:warn] [pid 7681] AH01873: Init

Re: [users@httpd] Failure to start apache2 after SSL cert update.

The /var/log/apache2/error_log simply lists a set of Configuration Failed lines. apachectl configtest produces Syntax OK What file should I change to set the debug level? > On 11 Jul 2020, at 7:08, Jack M. Nilles wrote: > > If I use: openssl x509 -noout -text -in WWW.SITENAME.COM.crt >

Re: [users@httpd] Failure to start apache2 after SSL cert update.

If I use: openssl x509 -noout -text -in WWW.SITENAME.COM.crt I get a complete readout of the cert file with no obvious errors. The problem seems to be that apache even fails to start so i'll try the debug level next. > On 11 Jul 2020, at 5:30, Jim Albert wrote: > > On 7/11/2020 6:10 AM, Ho

Re: [users@httpd] Failure to start apache2 after SSL cert update.

On 7/11/2020 6:10 AM, Holger Schramm wrote: Am 11.07.20 um 00:32 schrieb Jack M. Nilles: The apache error logs all quit at the point just before I restarted it. User and group permissions for the SSL files are all root, as before. Jack have you checked the files? sometime there are missing

Re: [users@httpd] Failure to start apache2 after SSL cert update.

1st change log level to debug; 2nd run " apachectl -t " . This will check whether you have bad syntax (often overlooked but just as serious). Angel Scotland > On 11 Jul 2020, at 11:10, Holger Schramm wrote: > > Am 11.07.20 um 00:32 schrieb Jack M. Nilles: >> The apache error logs all quit at

Re: [users@httpd] Failure to start apache2 after SSL cert update.

Am 11.07.20 um 00:32 schrieb Jack M. Nilles: The apache error logs all quit at the point just before I restarted it. User and group permissions for the SSL files are all root, as before. Jack have you checked the files? sometime there are missing newlines in cert chains or other malformed th

Re: [users@httpd] Failure to start apache2 after SSL cert update.

The apache error logs all quit at the point just before I restarted it. User and group permissions for the SSL files are all root, as before. Jack > On 10 Jul 2020, at 15:00, Antony Stone > wrote: > > On Friday 10 July 2020 at 23:54:05, Jack M. Nilles wrote: > >> I recently updated two virtu

Re: [users@httpd] Failure to start apache2 after SSL cert update.

Have you checked the apache error logs? En 10 jul. 2020 23:54, en 23:54, "Jack M. Nilles" escribió: >I recently updated two virtual servers with new SSL certificates, >restarted apache and got a failure to load. > >Here is a diagnostic: > > systemctl status apache2.service >● apache2.service - T

Re: [users@httpd] Failure to start apache2 after SSL cert update.

On Friday 10 July 2020 at 23:54:05, Jack M. Nilles wrote: > I recently updated two virtual servers with new SSL certificates, restarted > apache and got a failure to load. > > Here is a diagnostic: Never mind what systemd tells you - what's in your apache log files? Also, have you checked the o

[users@httpd] Failure to start apache2 after SSL cert update.

I recently updated two virtual servers with new SSL certificates, restarted apache and got a failure to load. Here is a diagnostic: systemctl status apache2.service ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: dis