apache not working

Sumaleth

Verified User
Joined
Jul 27, 2003
Messages
198
Our apache service has stopped working. When I try to stop or start the service I get errors like:

--
Starting httpd: [FAILED]
--

This has happened since we updated DA a couple of hours ago. Any ideas on what I could do to fix this?

Rowan.
 
Hi there,
I"m searching on this forum on this issue as all my domains are unaccessible and all my clients get angry right now.

I check with datacenter, but they said datacenter is fine. So I try to check with some friends who are usinf directadmin and they said they have the same problem.

It happen when I update to the latest version.

So is this really directadmin problem? If it's, I hope directadmin staff can solve the issue urgently as all my clients are angry right now.

I received lots of complaints since I update it to the latest version as my server is down.
 
Anyone can assit me what to do to solve this issue? My datacenter is quite far from my office. Do I need to rebbot the server physically? As I can SSH it at all right now as the server is down.

Please help. I need an urgent assitance on solving the issue.
 
Anyone can assit me what to do to solve this issue? My datacenter is quite far from my office. Do I need to rebootthe server physically? As I can't SSH my server at all right now as the server is down.

Please help. I need an urgent assitance on solving the issue.
 
If your problem is the same problem that we had, it was because something compiled apache 2.x whereas we needed to retain 1.x.

We recompiled 1.x to fix it (via SSH), but I don't know anything more than that.

I'll mention this thread to Phil and he might be able to be more specific.

Rowan.
 
searching,

If you can't ssh in, and you could before, then it's probably not the same problem that Rowan has mentioned.

If you can't ssh in, have the data center try to reboot the server.

If that doesn't work, then yes, you'll need to visit the server to figure out what's wrong.

Jeff
 
Hi,
Thanks for the assistance. The problem is already solved. My administartor try to reboot it physically many times this morning at 8am 24th March (on GMT+8) but failed.

Therefore he has to disconnect it and diagnost it offline.

I'm really surprised with this issue of updating to the latest version and made my server down!

I like directadmin but now I'm thinking twice due to this issue. Directadmin supposely to test it before releasing the latest version as this downtime really cost me a lot!

Regards
 
Hi,
My apache never updated. It's still the old apache ie 1.3.31. What I mean updated to the latest version was the directadmin 1.235. Since I update it, my server suddently down few hours later.

Regards
 
searching said:
Hi,
My apache never updated. It's still the old apache ie 1.3.31. What I mean updated to the latest version was the directadmin 1.235. Since I update it, my server suddently down few hours later.

Regards

You might want to ask your host what the issue was instead of guess assuming it was DA. They fixed it afterall. :)

Last time a host fixed a server for me, they broke Exim. Lots of fun.

-drmike
 
my DA is installed in my own server. It's colocated at a datacenter. I'm not using any other host. And I never altered any configuration until I encountered this issue ie after I update my DA license to version 1.235 and suddently my server is totally down.

When it was down, then only I've altered the configuration to fix the issue.

Anyway, it's solved now but after our administartor debug it.

Regards
 
drmike said:
You might want to ask your host what the issue was instead of guess assuming it was DA. They fixed it afterall. :)

My server was fixed by MY datacenter technical support and not by DA staff or DA technical support. Which means it's fixed on my own and not by DA.

Hope next time, DA test it frst before releasing the latest version for user to update.

Regards
 
Back
Top