httpd stopped, cannot restart

F

fshagan

Verified User
Joined
Aug 2, 2011
Messages
38
Need some help to get my server back up. It was failing with a domain having a bad httpd.conf file, so I deleted that domain after trying to rebuild apache and failing. Rebooted the server. Now what I'm getting are these errors for every domain:


Sep 10 07:47:41 host1.hostkabob.com named[2018]: client @0x7fa20810e9d0 109.201.133.111#58199 (acumenconsultingcompany.com): query (cache) 'acumenconsultingcompany.com/SOA/IN' denied

Sep 10 07:47:41 host1.hostkabob.com named[2018]: client @0x7fa20004d570 185.206.180.104#41491 (makecbdpaincream.com): zone transfer 'makecbdpaincream.com/AXFR/IN' denied

Sep 10 07:47:41 host1.hostkabob.com named[2018]: client @0x7fa1f8023310 109.201.133.111#22984 (acumenconsultingcompany.com): bad zone transfer request: 'acumenconsultingcompany.com/IN': non-authoritative
 
And I have a message into Proalix support, but I believe it's nighttime in Russia.
 
Seems you rather have a nameserver issue.
AXFR/IN denied is a good thing by the way unless you're using non-DA external nameservers.

Check this (got it from intodns):
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns3.hostkabob.com
ns4.hostkabob.com

Looks like your nameservers do not agree on the SOA serial. Ths SOA records as reported by your nameservers:
168.235.104.53 -> 2021091002
185.136.96.100 -> 2021060300
185.136.98.100 -> 2021060300
185.136.97.100 -> 2021060300

Als no MX record present.
 
NS1 points to the DirectAdmin server at 168.235.104.53, and NS2 - NS4 point to servers at CloudNS.net. So maybe it's the configuration for the external name servers that's wonky all of a sudden.

DirectAdmin only lists two nameservers for the server in their default configuration, right? SOA record mismatches shouldn't cause an Apache error but maybe that does show the dns info is out of whack.
 
fshagan said:
SOA record mismatches shouldn't cause an Apache error
Click to expand...
Correct, but I'm only responding to what I see. From the log files you posted, one can't determine what is wrong with apache or the websites.
You posted the errors what you got and I posted why you do get those.

DNS problems can certainly cause websites to not be reachable. However seems ns1 is working fine.

I was looking at the domain you have the nameservers on and very shortly it was redirected to some domain with "pain" in the name but then jumped back to your man domain name. However still unreachable.

If you want to find out why your websites are down, you have to look at apache logs to start with.
 
OK, thank you very much! I appreciate pointing me in the direction to get it resolved!
 
You're welcome. If you find anything in the apache logs we can help you with, just let us now.

Just to be sure, try this as root via SSH:
Code: 
cd /usr/local/directadmin/custombuild
./build update
./build rewrite_confs

It can't do any harm but it can fix things.
 
Last edited:
You must log in or register to reply here.
Back
Top