Yesterday there was TW update, it didn’t require restart, and then later I noticed that my apache2 stopped. It failed on reboot, too. I get error messages like this:
Apr 28 14:48:48 newtw systemd[1]: Starting The Apache Webserver…
Apr 28 14:48:48 newtw start_apache2[8921]: AH00557: httpd-prefork: apr_sockaddr_info_get() failed for newtw
Apr 28 14:48:48 newtw start_apache2[8921]: AH00558: httpd-prefork: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1. Set the ‘ServerName’ directive globally to suppress this message
Apr 28 14:48:48 newtw systemd[1]: Started The Apache Webserver.
Apr 28 14:48:48 newtw systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a
The warning about ServerName can be solved by adding “ServerName localhost” to /etc/apache2/httpd.conf but apache2 still fails to start. The previous httpd.conf worked just fine before so it shouldn’t have been the problem. Anyway, after setting ServerName I get this:
stan@newtw:~> sudo systemctl status apache2.service --full --no-pager
× apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Sun 2024-04-28 15:16:34 +07; 3s ago
Duration: 58ms
Process: 11908 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=254)
Process: 11923 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS)
Main PID: 11908 (code=exited, status=254)
Status: “Reading configuration…”
CPU: 85msApr 28 15:16:34 newtw systemd[1]: Starting The Apache Webserver…
Apr 28 15:16:34 newtw systemd[1]: Started The Apache Webserver.
Apr 28 15:16:34 newtw systemd[1]: apache2.service: Main process exited, code=exited, status=254/n/a
Apr 28 15:16:34 newtw start_apache2[11923]: httpd (no pid file) not running
Apr 28 15:16:34 newtw systemd[1]: apache2.service: Failed with result ‘exit-code’.
stan@newtw:~>
In /var/log/apache2/error_log I have this:
[Sun Apr 28 15:16:34.807063 2024] [ssl:warn] [pid 11908] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
PHP Fatal error: Unable to start pcre module in Unknown on line 0
Googling for AH01873 error I get old posts about manual configuration and going through various SSL related files but they were all about setting apache for the first time. Mine was working fine before, I never touched anything with “SSL” or “Session Cache” in their name, I don’t even know if I need SSL - I access this server only from local network for quick downloading files in a browser and such.
Does it mean that after this update I need to configure SSL and https?
Another thing I suspect i srelated - earlier this week another update broke my login on wayland, for all users on the system, then Saturday update fixed that but broke apache. Is it some kind of underlying identity problem somewhere?