Apache DocumentRoot does not exist?

ASap

Verified User
Joined
May 3, 2013
Messages
100
Location
the land of the long white cloud
Hi,

I'm wondering everytime I restart my Apache, I got these issues, any idea what's wrong with my Apache?
Code:
Stopping httpd:
Starting httpd: [Sat Jun 20 06:53:06.510646 2015] [so:warn] [pid 3974] AH01574: module php5_module is already loaded, skipping
AH00112: Warning: DocumentRoot [/home/google/domains/google.com/public_html/leech] does not exist
AH00112: Warning: DocumentRoot [/home/google/domains/google.com/private_html/leech] does not exist
AH00112: Warning: DocumentRoot [/home/yahoo/domains/yahoo.com/public_html/community] does not exist
AH00112: Warning: DocumentRoot [/home/yahoo/domains/yahoo.com/private_html/community] does not exist
AH00112: Warning: DocumentRoot [/home/yahoo/domains/yahoo.com/public_html/nat] does not exist
AH00112: Warning: DocumentRoot [/home/yahoo/domains/yahoo.com/private_html/nat] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/public_html/elsha] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/private_html/elsha] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/public_html/media] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/private_html/media] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/public_html/myradio] does not exist
AH00112: Warning: DocumentRoot [/home/altavista/domains/altavista.com/private_html/myradio] does not exist
AH00112: Warning: DocumentRoot [/home/bing/domains/bing.com/private_html] does not exist
AH00112: Warning: DocumentRoot [/home/deb/domains/debian.org/public_html/srikantirahayu] does not exist
AH00112: Warning: DocumentRoot [/home/deb/domains/debian.org/private_html/srikantirahayu] does not exist

root@server:/usr/local/directadmin/custombuild#
The system is going down for reboot NOW!server.net (tty1) (Sat Jun 20 06:59:17
 
Last edited:
Hello,

Those are just warnings you can safely ignore them. Or just create those directories and change ownership of them to their users. There is no a chance for us to guess on why those directories are gone.

By the way do you really host those domains (altavista.com, bing.com, google.com, etc) on your server?
 
I have apache down and I don't know why, this is the error, any help?


● httpd.service - The Apache HTTP Server
Loaded: loaded (/etc/systemd/system/httpd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2019-08-05 17:37:57 CEST; 18s ago
Process: 2789234 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 2592419 ExecReload=/usr/sbin/httpd $OPTIONS -k graceful (code=exited, status=0/SUCCESS)
Process: 2788493 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 2788493 (code=exited, status=1/FAILURE)

Aug 05 17:37:56 ns81.honesting.com httpd[2788493]: AH00112: Warning: DocumentRoot [/home/admin/domains/sharedip] does not exist
Aug 05 17:37:56 ns81.honesting.com httpd[2788493]: AH00112: Warning: DocumentRoot [/home/admin/domains/sharedip] does not exist
Aug 05 17:37:56 ns81.honesting.com httpd[2788493]: AH00112: Warning: DocumentRoot [/home/admin/domains/sharedip] does not exist
Aug 05 17:37:56 ns81.honesting.com httpd[2788493]: AH00112: Warning: DocumentRoot [/home/admin/domains/sharedip] does not exist
Aug 05 17:37:57 ns81.honesting.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Aug 05 17:37:57 ns81.honesting.com kill[2789234]: kill: cannot find process ""
Aug 05 17:37:57 ns81.honesting.com systemd[1]: httpd.service: control process exited, code=exited status=1
Aug 05 17:37:57 ns81.honesting.com systemd[1]: Failed to start The Apache HTTP Server.
Aug 05 17:37:57 ns81.honesting.com systemd[1]: Unit httpd.service entered failed state.
Aug 05 17:37:57 ns81.honesting.com systemd[1]: httpd.service failed.
 
The posted lines do not give any clue on what might be wrong there.

Check syntax:

Code:
apachectl -t

check logs:

Code:
tail -n30 /var/log/httpd/error_log
 
On the first post in this thread: that happens when users create subdomains from the DirectAdmin control panel and then delete the directories from FTP. You can safely ignore the warnings. Or ask the users to delete the subdomains when they are no longer using them.
 
Back
Top