Updated Directadmin and now Apache is screwed up.

labrocca

labrocca

Verified User
Joined
Mar 12, 2006
Messages
138
Well..ever since I did a directadmin update on my freebsd 6.2 box the apache has decided to lock up.

Searching and searching I have come up with very few solid solutions. I have turned off the apache keepalive and that has seemingly stopped the problem. However this imho isn't a solution.

Can someone please tell me what the directadmin update actually does so I might fully understand what was changed and how it may have effected the server?

My server version is listed as 1.31.2

Specs:
Apache/1.3.37 (Unix) PHP/5.2.3 mod_ssl/2.8.28 OpenSSL/0.9.7e-p1 FrontPage/5.0.2.2510

I also run eaccelerator and zend optimizer. The server has been running for nearly a year perfectly up till I hit that "update directadmin" link in the control panel. I ain't going to do that again.

One of the errors I recieved that clued me in was on dmesg:

"collecting pv entries -- suggest increasing > PMAP_SHPGPERPROC"


Help is greatly appreciated.

Thank you.
 
Last edited:
Well I did the updates to apache 1.3.9 and php 5.2.5 as well as mysql 5.0.45a. Everything seems to take well.

Now I get this error in apache hundreds of times:

/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/uptime: not found
/chmod: not found
/chmod: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/chmod: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
/uptime: not found
Click to expand...

Anyone want to guess what's wrong there? Google searching hasn't brought up anything useful. Also the server was fine for a few hours then it locked up again. So this really hasn't fixed completely the problem. Apache didn't lock up completely as it did before.

Should I contact DA support for this? Would they actually log into my server to fix this? The problem completely stems from an update of their directadmin panel.

Bah!
 
Apache error logs and it's driving me NUTS...

It's like I am going from one error to the next.

I did a grep on just about the entire server and so far no luck...so I just don't know what to do. I can't have the server lock up everytime I am away from the computer.

These errors seem to appear at a rate of 5 a minute give or take..it's VERY frequent. I am shutting off parts one at a time trying to see which might produce the error. This is very time consuming and frustrating. I could be spending time with my wife on her day off but instead I am trapped typing all day.

SUCKS...

DA help me please!
 
Almost like they are missing aliases or something.

/chmod: not found

this is all that is in the logs?

You can try rebuilding the httpd configs

cd /usr/local/directadmin/custombuild
./build rewrite_confs
/sbin/service httpd restart
 
That's the bulk of the error logs...the rest is fairly normal 404 stuff.

And Apache still appears to lock up after some time.

This server was PERFECT for months..this just stinks.

I still wish someone would explain how the updating of the directadmin has created such havok.
 
chatwizrd said:
Almost like they are missing aliases or something.

/chmod: not found

this is all that is in the logs?

You can try rebuilding the httpd configs

cd /usr/local/directadmin/custombuild
./build rewrite_confs
/sbin/service httpd restart
Click to expand...

Just tried this...didn't work.

I also tried to update php by removing the openssl but that didn't help. I have removed zend optimizer and eaccelerator with no effect. I also have the keep alive set to off now. Oh..and I also tried to end the dataskq with this command:

echo 'action=tally&value=none' >> /usr/local/directadmin/data/task.queue


Not sure if that's correct but it doesn't seem to have changed anything.
 
Last edited:
If you would like I can look at it but would need ssh access to do so.

You can send me a priv message here on the boards or contact me on instant messenger.
 
Last edited:
Alright..seems the problem is from a script on one of my sites...earlier I altered all the sites to be safe_mode on and I guess that's what started it. I will enable them one by one to see which is the problem (35 sites :rolleyes: )

Doubtful this is the end of my problems because the lockups were still occuring. Apache just seem to decide it wasn't worth it to serve pages even though the processes are running and the load is very low.

Getting late here...not much more of this I can take. Will keep you updated in case tomorrow I need assistance.
 
Well if you know what version your control panel was at before you can always look at the changelog at http://directadmin.com/versions.php to see what was changed.

As far as locking up what are you using to determine this is happening? Is the website just not loading in your browser or how do you determine it has locked up.
 
Hello,

We have a few guides to debug things like that..
If it's a filedescript limit issue, then try solution number #2 first from this guide, then try others failing that:
http://help.directadmin.com/item.php?id=9

Past that, you mention you're using apache 1.3, try apache 2.2 if the problem can't be found:
http://files.directadmin.com/services/custombuild/1.1/

As for DA updates, they don't really touch apache. DA updates mainly only update things for DA itself. The closes thing that would affect apache from the DA update would be changes to the user httpd.conf files, which you can try playing with, but the syntax didn't change a whole lot, just more "if" statements, for other cases.

John
 
I think with the ./build rewrite_confs and finding my errors in apache have fixed the problems.

Been 12 hours without problems now. If I can go a full 48 hours then I am fairly confident it's all good once again.

Some good help here in the forums. I try to fix things with forum help before contacting support as I like to understand how to fix things myself. I appreciate everyones assistance.

Thank you.
 
Well problem is still persistent so I am now trying your solution here:

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

I guess tomorrow I will try to go Apache 2.2.

I am still getting this error from system:

"collecting pv entries -- suggest increasing PMAP_SHPGPERPROC"

So that makes me think that Apache 2.2 might fix it.

Looks like tomorrow is another day of compiling. :(
 
You must log in or register to reply here.
Back
Top