New CustomBuild on RHEL4

[l33tnet]

We just installed DA on a RHEL4 machine this afternoon. The installed went through fine, and everything was working until all of a sudden, the system just came to a slow crawl. I dug around in the logs after the data center rebooted the machine, and the only errors I found were:

Jul  1 20:31:02 apollo httpd: [Sun Jul 01 20:31:02 2007] [warn] module php5_module is already loaded, skipping
Jul  1 20:31:02 apollo httpd: Syntax error on line 16 of /etc/httpd/conf/ips.conf:
Jul  1 20:31:02 apollo httpd: User cannot occur within <VirtualHost> section
Jul  1 20:31:02 apollo httpd: httpd startup failed

Any thoughts on what might be causing this? the VHost at the line mentioned is below (IP/Domain edited):

<VirtualHost 00.00.00.00:80>
        ServerName shared.domain
        ScriptAliasMatch ^/~([^/]+)/+cgi-bin/+(.*) /home/$1/public_html/cgi-bin/$2
        AliasMatch ^/~([^/]+)(/.*)* /home/$1/public_html$2
        DocumentRoot /home/username/domains/sharedip

        User username
        Group username

        CustomLog /var/log/httpd/homedir.log homedir
</VirtualHost>

 

[l33tnet]

After doing some digging, and piecing some information together, along with an e-mail I got from DA Support ... I did the following, and now Apache loads with the server (only throwing the duplicate PHP error):

apache_ver=2.0 is set into /usr/local/directadmin/conf/directadmin.conf. Then do:

echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d

We were also noticing that the server was quickly becoming unstable, and we were unable to get to it via HTTP, or SSH (SSH allowed login, however no shell was provided). We're still looking into this issue, and are awaiting word from DA Support regarding the duplicate PHP entry.

 

[l33tnet]

After making these changes, overnight the server has become completely unresponsive. Checking error logs to see if this may be a KERNEL related issue.