thankfully it hooks into way too much Sent from my iPhone
> On May 31, 2022, at 6:53 PM, Yehuda Katz <yeh...@ymkatz.net> wrote: > > > systemd doesn't know to look in the HTTPD log file. What does that log say? > Likely located in /var/log/apache2/ > > - Y > >> On Mon, May 30, 2022 at 9:58 AM jnil...@jala.com <jnil...@jala.com> wrote: >> I 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 Webserver >> Loaded: 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 ago >> Process: 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/FAILURE >> May 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.
