apache-sp won't start when linode boots
I receive the following FAILED messages when my linode starts related to apache-sp, and when i execute i receive the message below - what do i need to do to get this resolved?
Thank you!
STARTUP INFO
[FAILED] Failed to start apache-sp.
See 'systemctl status apache-sp.service' for details.
[FAILED] Failed to start apache-sp.
See 'systemctl status apache-sp.service' for details.
[FAILED] Failed to start apache-sp.
See 'systemctl status apache-sp.service' for details.
[ OK ] Stopped apache-sp.
Starting apache-sp…
[FAILED] Failed to start apache-sp.
See 'systemctl status apache-sp.service' for details.
Ubuntu 16.04.7 LTS 127.0.0.1localhost ttyS0
root@127:/etc# systemctl status apache-sp.service
● apache-sp.service - apache-sp
Loaded: loaded (/lib/systemd/system/apache-sp.service; enabled; vendor preset
: enabled)
Active: failed (Result: start-limit-hit) since Fri 2020-09-18 01:42:09 UTC; 9
min ago
Process: 1568 ExecStartPre=/opt/sp/apache/bin/apachectl configtest (code=exite
d, status=1/FAILURE)
Sep 18 01:42:08 127.0.0.1localhost systemd[1]: Failed to start apache-sp.
Sep 18 01:42:08 127.0.0.1localhost systemd[1]: apache-sp.service: Unit entered f
ailed state.
Sep 18 01:42:08 127.0.0.1localhost systemd[1]: apache-sp.service: Failed with re
sult 'exit-code'.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: apache-sp.service: Service hold-o
ff time over, scheduling restart.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: Stopped apache-sp.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: apache-sp.service: Start request
repeated too quickly.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: Failed to start apache-sp.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: apache-sp.service: Unit entered f
ailed state.
Sep 18 01:42:09 127.0.0.1localhost systemd[1]: apache-sp.service: Failed with re
sult 'start-limit-hit'.
5 Replies
This is the key piece of info:
ExecStartPre=/opt/sp/apache/bin/apachectl configtest (code=exite
d, status=1/FAILURE)
apachectl configtest is a check on the syntax and semantics of your apache2 configuration. That check is failing.
Check your apache2 logs. The reason for the failure is most likely given there.
— sw
Thank you - problem was suexec didn't have the right permissions so I ran the command: root@localhost:/opt/sp/apache/bin# chmod 4754 suexec
@mshulman --
You should probably report this to the serverpilot team. This sounds like an installation packaging defect to me.
-- sw
Everything is the same as above for me just now, except mine gave this key piece of info:
475 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILUR
Being quite new to Apache, I do not yet know how to check my apache2logs. In fact, after viewing the output from running the systemctl status apache2.service command, I'm left with "lines 1-15/15 (END) and cannot seem to escape short of rebooting the server.