After upgrade from 15.5 15.6 Apache fails to start

Apache 2.4.58-150600.5.29.1

I upgraded LEAP 15.5 to 15.6. Everything looked good until I tried to load a local webpage. It seems Apache2 (httpd) will not start.

If there are any useful messages somewhere, I cannot find them.

Any help is appreciated.

Here is what I could find.

# systemctl status apache2.service 
× apache2.service - The Apache Webserver
     Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sun 2025-01-12 10:43:15 MST; 51s ago
    Process: 12507 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE)
   Main PID: 12507 (code=exited, status=1/FAILURE)
     Status: "Reading configuration..."
        CPU: 145ms

Jan 12 10:43:15 sma-server3 systemd[1]: Starting The Apache Webserver...
Jan 12 10:43:15 sma-server3 systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
Jan 12 10:43:15 sma-server3 systemd[1]: apache2.service: Failed with result 'exit-code'.
Jan 12 10:43:15 sma-server3 systemd[1]: Failed to start The Apache Webserver.
# journalctl -xeu apache2.service
Jan 12 10:45:41 sma-server3 systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 12 10:45:41 sma-server3 systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jan 12 10:45:41 sma-server3 systemd[1]: Failed to start The Apache Webserver.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit apache2.service has finished with a failure.
░░ 
░░ The job identifier is 24026 and the job result is failed.

@jimbobrae:

There are two methods to discover what’s happening here:

  1. Check the contents of ‘/var/log/apache2/error_log’ …
  2. Manually execute the “ExecStart” command in ‘/usr/lib/systemd/system/apache2.service’ …

# ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start

Finally found the error.

Oh-so-long ago (2016) I had been experimenting with a “cloud” site implementation and had two conf files for it, one each for secured and unsecured. I had disabled the unsecured site but had not disabled the secured conf.

When the upgraded apache started, it used a stricter requirement for SSL certificates.

After disabling that secured site, apache started normally.

[Mon Jan 13 10:53:01.860116 2025] [ssl:emerg] [pid 30670] AH02562: Failed to configure certificate cloud.sma.com:443:0 (with chain), check /data01/t-drv/websites/.conf/ssl/cloud-site.crt
[Mon Jan 13 10:53:01.860879 2025] [ssl:emerg] [pid 30670] SSL Library Error: error:0A00018E:SSL routines::ca md too weak

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