That solved it! Apache has successfully started.Thanks Yehuda and Frank!On 30 May 2022, at 8:51, Yehuda Katz <yehuda@xxxxxxxxxx> wrote:Then something is probably wrong with the contents of one of your SSL certificates. Make sure they are formatted correctly.Check if any virtualhost has a separate error log.- YThe tail end of /var/log/apache2/error_log gives:[Fri May 27 00:02:10.914649 2022] [ssl:warn] [pid 1562] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache][Fri May 27 00:02:10.939405 2022] [:emerg] [pid 1562] AH00020: Configuration Failed, exitingAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedAH00016: Configuration FailedThere's nothing for May 30. I have updated ssl certificates recently.JMNOn 30 May 2022, at 7:01, Yehuda Katz <yehuda@xxxxxxxxxx> wrote:systemd doesn't know to look in the HTTPD log file. What does that log say?Likely located in /var/log/apache2/- YI recently rebooted the server and started apache only to get a failure. Here's the diagnosis; I'm not sure what to make of it.systemctl status apache2.service● apache2.service - The Apache WebserverLoaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled)Active: failed (Result: exit-code) since Mon 2022-05-30 06:53:28 PDT; 23s agoProcess: 23499 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=exited, status=1/>Main PID: 23499 (code=exited, status=1/FAILURE)Status: "Reading configuration..."May 30 06:53:28 server systemd[1]: Starting The Apache Webserver...May 30 06:53:28 server systemd[1]: apache2.service: Main process exited, code=exited, status=1/FAILUREMay 30 06:53:28 server systemd[1]: apache2.service: Failed with result 'exit-code'.May 30 06:53:28 server systemd[1]: Failed to start The Apache Webserver.
|