After LEAP 15 Apache2 will not start

English Install/Boot/Login
#1

LEAP 15
apache2 2.4.33

On Leap 42.3 apache2 2.4.23 worked fine. On Leap 15 v2.4.33 refuses to start.

Below is all of the info I could find regarding its failure to start. The bit about “unit configuration” seems helpful, if only I knew what it meant.

The part about “<whatever>_module is already loaded, skipping” was listed in LEAP 42.3 as well. I could never find why apache would try to load the modules twice but it was not a deal breaker.

Suggestions?

$ systemctl start apache2.service
Job for apache2.service failed because the service did not take the steps required by its unit configuration.
See "systemctl  status apache2.service" and "journalctl  -xe" for details.


2018-07-16T10:14:23-0700 sma-server3 systemd[1]: Starting The Apache Webserver...
2018-07-16T10:14:23-0700 sma-server3 start_apache2[13613]: [Mon Jul 16 10:14:23.519154 2018] [so:warn] [pid 13613] AH01574: module authz_host_module is already loaded, skipping
2018-07-16T10:14:23-0700 sma-server3 start_apache2[13613]: [Mon Jul 16 10:14:23.519239 2018] [so:warn] [pid 13613] AH01574: module actions_module is already loaded, skipping
  .... a bunch more ...
2018-07-16T10:14:23-0700 sma-server3 start_apache2[13613]: httpd (pid 13464) already running
2018-07-16T10:14:23-0700 sma-server3 systemd[1]: Failed to start The Apache Webserver.
2018-07-16T10:14:23-0700 sma-server3 systemd[1]: apache2.service: Unit entered failed state.
2018-07-16T10:14:23-0700 sma-server3 systemd[1]: apache2.service: Failed with result 'protocol'.


$ systemctl status apache2.service
● apache2.service - The Apache Webserver
   Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled)
   Active: failed (Result: protocol) since Mon 2018-07-16 10:14:23 MST; 2min 36s ago
  Process: 13613 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=0/SUCCESS)
 Main PID: 13613 (code=exited, status=0/SUCCESS)

Jul 16 10:14:23 sma-server3 start_apache2[13613]: [Mon Jul 16 10:14:23.519400 2018] [so:warn] [pid 13613] AH01574: module rewrite_m>
  .... a bunch more ...
Jul 16 10:14:23 sma-server3 start_apache2[13613]: httpd (pid 13464) already running
Jul 16 10:14:23 sma-server3 systemd[1]: Failed to start The Apache Webserver.
Jul 16 10:14:23 sma-server3 systemd[1]: apache2.service: Unit entered failed state.
Jul 16 10:14:23 sma-server3 systemd[1]: apache2.service: Failed with result 'protocol'.
#2

There are detailed notes at Apache.org about changing between versions and th alterations required to the configuration files. I cannot remember exactly what I had to do, but it only took a few minutes to update the .conf files.

If this is a simple set-up and you are not involved in commercial hosting, it might be simpler to delete/rename /etc/apache2 , reinstall and use yast to set up your host(s)

You need to use “systemctl status -l apache2” to read the full output.

P.S. This is about an application, not installing or booting openSUSE

#3

After re-installing the package, an additional error was shown regarding a missing SSL certificate listed in
</etc/apache2/vhosts.d/ssl-global.conf>. Fixing that allowed apache2 to load.