hostit1

Well-Known Member
Jul 24, 2003
88
0
156
A strange thing is happening on a server that we have. We have 360 users on a quad server. Sometimes the httpd.conf file will be corrupted. Today, I went into whm and it said I only had 20 accounts.

This has happened twice on this server. Last time, it said I had 120 accounts.

Luckily, I make a backup of the configuration files daily and I was able to restore.

There are no apparent rootkits installed. To be on the safe side, I am going to move all accounts from this server to another server, but we must find out what is causing this httpd.conf corruption!!!!!!

Sincerely,


Mark Langston
Host It Now Networks
 

haze

Well-Known Member
Dec 21, 2001
1,540
3
318
You could run badblocks to check for a corrupt filesystem. I haven't had this happen in a while, but in my case, its happened on drives going bad. This may also be caused by 2 people ( perhaps resellers ) creating an account at the same time, which would cause problems. I believe a proposed fix exists in the bugzilla system, perhaps you can have a look and vote for the bug if ya find it ;)
 

hostit1

Well-Known Member
Jul 24, 2003
88
0
156
Thanks for the advice. I did check badblocks, and everything seems to be fine! We don't have any resellers on this server and the server is at compacity, so we have not been adding users. This is really weird stuff. At first I believed that maybe I had an employee that was goofing with the production box, but I reviewed his bash history and he did not su into root.

Really weird stuff.
 

easyhoster1

Well-Known Member
Sep 25, 2003
656
0
166
This happened to us when we edited the packages. We found that http.config would drop half the accounts when we did this. Now we only upgrade or downgrade one account at a time.
 

hostit1

Well-Known Member
Jul 24, 2003
88
0
156
We were NOT upgrading any accounts at time of corruption

We were NOT upgrading any accounts at time of corruption.
 

mr.wonderful

BANNED
Feb 1, 2004
344
1
166
This has happened to us on at least two occasions. Forunately, we had a saved httpd.conf file on both occassions. We were missing about 150 domains and it was nearly impossible to work out which domains those were but after we restored the backup httpd.conf everthing was smooth sailing from there. Suggestion, always backup httpd.conf before rebuilding Apache. To this day we dont know what caused it.
 

Silverado

Well-Known Member
Mar 19, 2003
153
0
166
Backyard - Poolside
We justg rolled back the apache conf within our WHM on one server missing almost 200 accounts and within a few seconds and it was all there, back again to normal. :)
I would have prefered to had a backup of the httpd.conf but we didn't. :)
 

iko

Well-Known Member
PartnerNOC
Jan 29, 2004
56
0
156
Although we have a backup of httpd.conf we need to use it a lot of times and this doesn't solve the problem. The problem is somewhere in cpanel, I believe. Httpd.conf regularly becomes corrupted. It is not a particular problem. It is a widespread problem that will affect you soon if you are not affected. Many users are complaining about this and I am surprised that cPanel stuff have NOT done anything to fix it.