[Nextcloud] Apache Not Booting
Howdy,
I'm new here and just recently completed the one-click install of Nextcloud. Everything was working well except my domain name I purchased. It had been over 72 hours since I changed the DNS address to Linode so I was beging to do some troubleshooting. I decided to try rebooting the linode…and it broke more!
After I noticed I could no longer reach nextcloud via IP, I saw that Apache failed to start on reboot. So I tried starting it manually.
root@user:/var/log# systemctl start apache2.service
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
root@user:/var/log#
Here's the log:
root@user:/var/log# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset:
Active: failed (Result: exit-code) since Tue 2020-12-01 12:00:00 UTC; 5min ag
Docs: https://httpd.apache.org/docs/2.4/
Process: 1474 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILUDec 01 12:00:00 user.com systemd[1]: Starting The Apache HTTP Server…
Dec 01 12:00:00 user.com apachectl[1474]: AH00548: NameVirtualHost has
Dec 01 12:00:00 user.com apachectl[1474]: AH00526: Syntax error on line
Dec 01 12:00:00 user.com apachectl[1474]: ServerAdmin takes one argumen
Dec 01 12:00:00 user.com apachectl[1474]: Action 'start' failed.
Dec 01 12:00:00 user.com apachectl[1474]: The Apache error log may have
Dec 01 12:00:00 user.com systemd[1]: apache2.service: Control process e
Dec 01 12:00:00 user.com systemd[1]: apache2.service: Failed with resul
Dec 01 12:00:00 user.com systemd[1]: Failed to start The Apache HTTP Se
As more of a hardware and LAN person I'm a bit out of my depth here, any help would be greatly appreciated.
2 Replies
You write:
Dec 01 12:00:00 user.com apachectl[1474]: AH00548: NameVirtualHost has
Dec 01 12:00:00 user.com apachectl[1474]: AH00526: Syntax error on line
Dec 01 12:00:00 user.com apachectl[1474]: ServerAdmin takes one argumen
These are syntax errors in your apache2(8) configuration. For Debian/Ubuntu, your apache2(8) configuration files are located in /etc/apache2 (YMMV for other distros):
- /etc/apache2/apache2.conf is the main configuration file run by apachectl(8);
- /etc/apache2/conf_enabled/* are symlinks to apache2(8) server configuration files located in /etc/apache2/conf_available (these symlinks are managed by the a2enconf(8)/a2disconf(8) commands);
- /etc/apache2/mods_enabled/* are symlinks to apache2(8) module configuration files located in /etc/apache2/mods_available (these symlinks are managed by the a2enmod(8)/a2dismod(8) commands); and
- /etc/apache2/sites_enabled/* are symlinks to apache2(8) site configuration files located in /etc/apache2/sites_available (these symlinks are managed by the a2ensite(8)/a2dissite(8) commands).
For a complete reference to apache2(8) configuration directives, see here:
https://www.guru99.com/apache.html
https://httpd.apache.org/docs/2.4/mod/directives.html
If your next question is Why didn't the one-click install take care of all this?, I'm afraid I'm not competent to answer that. As a general rule, I don't trust a one-click anything to ever do the right thing…
-- sw
Thanks for the direction. I'll dig in when I get the chance.