First time every using aaPanel and really liking it!
Setup a new VPS to try and added a few domains. All seems to work perfectly and do not see any errors in aaPanel area. Using Ubuntu 20.10 (GNU/Linux 3.10.0-1127.8.2.vz7.151.14 x86_64)
Apache showing fine in aaPanel:
While trying a few things in terminal (SSH), I discovered that Apache2 would not (re)start? Very confused. Shows fine in aaPanel but not in terminal. Hoping someone can enlighten me by looking at few logs below.
Many thanks.
`root@server4:~# journalctl -xe
Dec 12 16:49:35 server4.xxxxxxxx.net apachectl[23561]: The Apache error log may have more i>
Dec 12 16:49:35 server4.xxxxxxxx.net systemd[1]: apache2.service: Control process exited, c>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 12 16:49:35 server4.xxxxxxxx.net systemd[1]: apache2.service: Failed with result 'exit->
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Dec 12 16:49:35 server4.xxxxxxxx.net systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 737 and the job result is failed.
===============================================================
root@server4:~# journalctl | tail
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23603]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23603]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23603]: no listening sockets available, shutting down
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23603]: AH00015: Unable to open logs
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23600]: Action 'start' failed.
Dec 12 16:58:50 server4.xxxxxxxx.net apachectl[23600]: The Apache error log may have more information.
Dec 12 16:58:50 server4.xxxxxxxx.net systemd[1]: apache2.service: Control process exited, code=exited, status=1/ FAILURE
Dec 12 16:58:50 server4.xxxxxxxx.net systemd[1]: apache2.service: Failed with result 'exit-code'.
Dec 12 16:58:50 server4.xxxxxxxx.net systemd[1]: Failed to start The Apache HTTP Server.
Dec 12 16:58:50 server4.xxxxxxxx.net sudo[23594]: pam_unix(sudo:session): session closed for user root
===============================================================
root@server4:~# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor prese>
Active: failed (Result: exit-code) since Sat 2020-12-12 17:29:32 CST; 19h >
Docs: https://httpd.apache.org/docs/2.4/
Process: 294 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAI>
Dec 12 17:29:31 server4.xxxxxxxx.net systemd[1]: Starting The Apache HTTP Server.>
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[322]: (98)Address already in use: >
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[322]: (98)Address already in use: >
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[322]: no listening sockets availab>
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[322]: AH00015: Unable to open logs
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[294]: Action 'start' failed.
Dec 12 17:29:32 server4.xxxxxxxx.net apachectl[294]: The Apache error log may hav>
Dec 12 17:29:32 server4.xxxxxxxx.net systemd[1]: apache2.service: Control process>
Dec 12 17:29:32 server4.xxxxxxxx.net systemd[1]: apache2.service: Failed with res>
Dec 12 17:29:32 server4.xxxxxxxx.net systemd[1]: Failed to start The Apache HTTP >`
