Editing Custom HTTPD configuration times out

LavantiS

Verified User
Joined
Apr 19, 2012
Messages
10
Dear all,

I am a frequent user of Custom HTTPD configuration, especially when needed to disable some modsecurity features while developent.

I recently updated my DirectAdmin from 4-5 minor releases back to the latest one and since then, everytime I click on a domain in order to modify it's custom Httpd configuration, I get a timeout (from Directadmin, not Apache)..

On server's logs I read;

25/02/2015:15:27:39 185.16.164.30 GET /CMD_CUSTOM_HTTPD HTTP/1.1

and on errors.log
2015:02:25-15:18:57: Timeout (timeout=60) from from 185.16.164.30 : last flagged: getHomeDir : userid1 : done
2015:02:25-15:28:39: Timeout (timeout=60) from from 185.16.164.30 : last flagged: getHomeDir : userid2 : done

I can still create and/or edit the

/usr/local/directadmin/data/users/userid1/domains/user1domain.com.cust_httpd

file, but I would prefer the user interface to work...


Any ideas?


Thank you in advance,
Minas
 
Hello,

To confirm, the timeout happens when you click the domain to view the page, and not when you save a change to the domain?

I believe that would probably be caused by DA's check for apache errors.
DA runs this for CentOS 6 and older:
Code:
/usr/sbin/service httpd configtest 2>&1
for the apache output at the bottom of the page.

If you're running CentOS 7 (systemd), Debian, or FreeBSD, or nginx, then the syntax is different, so let me know which it is.

Run the above code in ssh, as root, and we'll see what it shows us.

John
 
Hello and thank you for your reply..

Yes, the timeout happens when I click on the domain name. I don't get to the edit page at all..
I go to HTTPD custom configuration -> Click on domain name -> 1-2 minutes waiting -> error message:
Your connection has timed out
Details
Either your request was invalid or the program hasn't completed your request.
Please notify the server admin

I ran as root the "service httpd configtest" and I got the following:

service httpd configtest
Warning: DocumentRoot [/home/user1/domains/domain1.com/public_html/eg] does not exist
Warning: DocumentRoot [/home/user2/domains/domain2.com/public_html/jo] does not exist
Warning: DocumentRoot [/home/user2/domains/domain3.com/private_html] does not exist
[Fri Mar 13 17:40:31 2015] [warn] NameVirtualHost xx.xx.xxx.xx:80 has no VirtualHosts
[Fri Mar 13 17:40:31 2015] [warn] NameVirtualHost xx.xx.xxx.xx:443 has no VirtualHosts
Syntax OK


I am not sure it will be helpful..
The system runs on a CentOS release 5.7 (Final)
 
Back
Top