Users' http.conf reset to nothing after reinstall

Invader Zim

Verified User
Joined
Sep 4, 2004
Messages
188
We installed the DA update to 1.36 last night, after which we added mod_expires to apache and soap support to php. All was well.

A couple of hours later I needed to make a change to our website but when I went there I got our default placeholder.

I restarted apache from the command line and I got this:
Code:
[Sun Jul 11 09:48:22 2010] [warn] NameVirtualHost a.b.c.d:80 has no VirtualHosts
[Sun Jul 11 09:48:22 2010] [warn] NameVirtualHost a.b.c.d:443 has no VirtualHosts
[Sun Jul 11 09:48:22 2010] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter
[Sun Jul 11 09:48:22 2010] [warn] (2)No such file or directory: Failed to enable the 'dataready' Accept Filter

The ip address is for an account with it's own ip address, all the other users have another ip address which is the same for all of them.

When I looked in a couple of httpd.conf files all I saw was:
Code:
# Auto generated apache config file by DirectAdmin version 1.36.0
# Modifying this file is not recommended as any changes you make will be
# overwritten when the user makes any changes to his/her website

# Frontpage requires these parameters in every httpd.conf file or else
# it won't work.
ServerRoot /etc/httpd
 
Well, this is embarrassing....

Turns out the virtual_host*.conf files in /usr/local/directadmin/data/templates/custom were owned by root and only had user read/write privs.

I've executed this operation many times but this hasn't happened before, not on this one, nor on another one...

*sigh* If only I had discovered this 5 hours ago, I could've gotten some sleep.
 
All DirectAdmin does with the files in the custom directory is it tries to read them. So it's likely that you edited the files (or created them) with the wrong permissions and ownership yourself.

Jeff
 
Whenever we reinstall apache or php we follow a script. In this script we copy the template config files for apache to the custom directory and make a few changes. When you copy a file over an existing file it usually takes on the privs of the existing file. Only this time it didn't, which caused our problems.

I just failed to look there (/usr/local/directadmin/data/templates/custom) on account of sleep deprivation.
 
Back
Top