[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apache not running at boot

On 07/18/2018 10:12 AM, Jonathan Dowland wrote:
On Wed, Jul 18, 2018 at 09:36:14AM -0400, Greg Wooledge wrote:
Sounds like the service may be disabled for some reason.  What is the
output of:

systemctl status apache2

If you see "; disabled;" on the "Loaded" line, then this should fix it,
one hopes:

systemctl enable apache2

After doing that, you should see "; enabled;" on the Loaded line.

The above should address having apache2 start on system boot (or restart
if killed for some reason); to start it on a running system you will
also want to issue

   systemctl start apache2

However, from what I recall, none of this should be necessary by
default, so there is likely a configuration problem. If all of the above

hello when i run systemctl this is what i get

● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 EDT; 1min 2s ago
  Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to addres
Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, shutting down
Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have more information.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process exited, code=exited status=1
Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered failed state.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 'exit-code'.

does not result in a running apache2, check "journalctl -u
apache2.service" for clues, and failing that, /var/log/apache2/*



hello when i run systemctl this is what i get

● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 EDT; 1min 2s ago
  Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to addres
Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, shutting down
Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have more information.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process exited, code=exited status=1
Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered failed state.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 'exit-code'.
Reply to: