customapache is broken and it won't tell me why

[gabriel]

We use the apache component to run a few small sites that I don't normally bother with so I have no idea how long apache has been dead, but it's definitely not working:

# /usr/local/etc/rc.d/httpd start
Starting httpd: [ OK ]
[Wed Nov 23 03:11:22 2005] [warn] module perl_module is already loaded, skipping
# ps ax | grep ht
19099 p1 RL+ 0:00.00 grep ht

So in my attempts to make it work I've tried to run the build script with "all" and just PHP as the arguments with no change except that I now have a number of copies of httpd.conf in my /etc/httpd/conf/ directory.

The error log just keeps repeating the same warning:

Wed Nov 23 03:14:01 2005] [warn] module perl_module is already loaded, skipping
[Wed Nov 23 03:14:01 2005] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run?

and I'm fresh out of ideas. The only thing I can think of that might have bothered this machine was my upgrade of gd because portaudit complained that the package had a security issue. I'd upgrade Perl too (yet another security issue) if i wasn't so afraid that that would break DNS and mail as well.

I'm hoping to find a solution that will allow me to keep the configurations for the few users we have setup using this thing as I don't know what kind of work went into creating the users in the first place and don't care to find out the hard way. Suggestions? Questions? Would it be bad to install a standard apache on this machine and just use that?

I'm using FreeBSD 5.3 if that means anything.

 

[Yikes2000]

Did you do this?

cd /usr/local/directadmin/customapache
./build clean
./build update
./build apache_mod_ssl

Did you notice any error? It may help if you replace the last command with "script build.log ./build apache_mod_ssl". It saves the compiling output to build.log for your review.

 

[gabriel]

Yep. Tried that last night, though just in case I ran exactly what you asked just now. The compilation finished without errors save for the following:

===> [config: Installing Apache configuration files]
./src/helpers/install.sh -c -m 644 ./conf/httpd.conf-dist[*] /etc/httpd/conf/httpd.conf.default
[PRESERVING EXISTING CONFIG FILE: /etc/httpd/conf/httpd.conf]
./src/helpers/install.sh -c -m 644 ./conf/access.conf-dist[*] /etc/httpd/conf/access.conf.default
[PRESERVING EXISTING CONFIG FILE: /etc/httpd/conf/access.conf]
./src/helpers/install.sh -c -m 644 ./conf/srm.conf-dist[*] /etc/httpd/conf/srm.conf.default
[PRESERVING EXISTING CONFIG FILE: /etc/httpd/conf/srm.conf]
./src/helpers/install.sh -c -m 644 ./conf/mime.types /etc/httpd/conf/mime.types.default
[PRESERVING EXISTING CONFIG FILE: /etc/httpd/conf/mime.types]
./src/helpers/install.sh -c -m 644 ./conf/magic /etc/httpd/conf/magic.default
[PRESERVING EXISTING CONFIG FILE: /etc/httpd/conf/magic]
chmod 755 /etc/httpd/conf/ssl.crt
chmod 755 /etc/httpd/conf/ssl.crl
chmod 755 /etc/httpd/conf/ssl.csr
chmod 700 /etc/httpd/conf/ssl.key
chmod 755 /etc/httpd/conf/ssl.prm
[PRESERVING EXISTING CERTIFICATE FILES: /etc/httpd/conf/ssl.crt/*]
Updating hash symlinks in /etc/httpd/conf/ssl.crt/:
ca-bundle.crt ... Skipped
server.crt ... 82ab5372.0
snakeoil-ca-dsa.crt ... 0cf14d7d.0
snakeoil-ca-rsa.crt ... e52d41d0.0
snakeoil-dsa.crt ... 5d8360e1.0
snakeoil-rsa.crt ... 82ab5372.1
[PRESERVING EXISTING CSR FILES: /etc/httpd/conf/ssl.csr/*]
[PRESERVING EXISTING CRL FILES: /etc/httpd/conf/ssl.crl/*]
[PRESERVING EXISTING KEY FILES: /etc/httpd/conf/ssl.key/*]
[PRESERVING EXISTING PRM FILES: /etc/httpd/conf/ssl.prm/*]
<=== [config]

which really isn't much of an error anyway. This didn't do the trick either though so I've decided to just disable SSL in each of the VirtualHosts. This made it work, even though it isn't a fix per se

 

[Yikes2000]

Maybe re-install OpenSSL from port?

 

[LyricTung]

The first error you list:

[Wed Nov 23 03:11:22 2005] [warn] module perl_module is already loaded, skipping

is just a warning as indicated and does not effect httpd's ability to stay running. Check your httpd logs and see if there is more detail. Also, there has been some discussion threads on gd upgrades installing Apache 2 leading httpd to not run.

DA has instructions for downgrading Apache if this turns out to be the problem for you:

http://help.directadmin.com/item.php?id=54