Service httpd restart FAILED what is wrong ?

Which generally means it will stop all programs from managing apache; including when a server boot, shuts down, or restarts. It will probably stop DirectAdmin from restarting apache even when you want it to.

Jeff
 
That's not really a solution, they need to be able to restart the server normally.

Is there any way to contact the DirectAdmin support directly? Because our hosting provider has pretty much said "It's not our problem".
 
You get support from your DirectAdmin supplier. Lifetime licenses from DirectAdmin include limited support for the first X months (I don't remember how many). If you buy DirectAdmin with period licenses, you get full support from DirectAdmin staff.

If you pay your provider for DirectAdmin, then support is supposed to be up to them. Perhaps if they say it's not their problem you can ask them to remove their DirectAdmin license, and give you a discount, and then buy a license yourself from DirectAdmin. You should expect to pay more, though, because data centers pay less for DirectAdmin licenses since they're supposed to do their own support, and support is really the most expensive part of any control panel.

You can certainly ask DirectAdmin if they'll help you; they may. You can reach them here.

Jeff
 
Thanks for that info, I'm starting to get the feeling our hosting provider is trying to get us to pay for a SLA... Anyway, they're switching us to a new VPS now, hopefully that will solve our problem as well.

On another forum this solution was offered, and it sounds like it could be a good solution for the problem: http://help.directadmin.com/item.php?id=181

Haven't tried it, because they're moving our stuff now, but hopefully that will be of help to others with the same problem. :)
 
Same problem here

Got the same problem on 2 servers of mine (start about 2 weeks ago) every few days i need to use kill -9 in order to kill the apache and then restart it. i think it's might be a problem with the last version of directadmin (some kind of bug or someting), i'm using directadmin for about 4-5 years and never had this kind of problem before.

Anyone can confirm that it will be solved in the next version of directadmin (some kind of bug fix or someting) ?

Thanks.
 
killall -9 exim
service httpd restart
service exim restart

That should solve the issue, if not, just reboot from the command line, or via the DA interface
 
@hostpc.com: that works, but that's not a permanent fix for the problem (almost daily crashing apache).

@gisha: I doubt it. If you have the exact same problem with ports in use like in this older help doc.. look at the date there, 2004. I'm amazed this is still an issue today, you'd think they would update those scripts to restart apache properly especially because the tally happens daily.

Gisha, maybe you can try out this other solution, looks like it could help in restarting apache properly.
 
Aero said:
@hostpc.com: that works, but that's not a permanent fix for the problem (almost daily crashing apache).
Click to expand...
If you check a lot of threads in these forums you'll see that apache and exim clash on port 80. So it actually is a permanent fix. Install it into your httpd control script as part of the restart section. Stopping exim momentarily each time you restart apache is NOT a problem.

Jeff
 
Hello,

I belive roundcube 0.1 may be playing a role in the issue. Please ensure you do not have roundcube 0.1 running.
Here are some tips to secure your system:
http://help.directadmin.com/item.php?id=247

The "/usr/sbin/apache/log" program, or the "www" program that were bound to port 80 are *highly* suspicious, especially when they don't exist. (they're not ours)

When checking /tmp for suspicious files, use "ls -la /tmp" to ensure you're seeing the username of the files as well.. you'll be looking for files chowned to apache or webapps. Usually, you should only be seeing sess_* files owned by them. Anything else would be worth taking note of.

If something else is bound to port 80 that isn't /usr/sbin/httpd, then the issue isnt the restart script or apache but rather that something else managed to bind to it. They may be using the same issue intentionally that exim accidently runs into when apache gets restarted an exim is bound to 80.
http://help.directadmin.com/item.php?id=247
But I'm still suspecting roundecube 0.1.

Another thing, is ensure you don't have any cronjobs by apache or webapps:
crontab -u webapps -l
crontab -u apache -l

should not show any cronjobs.

John
 
You should check:
Code: 
netstat -lnp | grep :80

Then:
Code: 
lsof -p PID
 
Aero said:
Hi, I've been having the same problem, on two servers actually. With one we just removed directadmin completely, but with the other one that's not an option.

Every night when Directadmin does the "Tally", it restarts apache. But it doesn't stop apache correctly somehow and port 80 (and sometimes port 443 too) are still in use by a not-working apache process. Apache won't restart because ports in use is a critical error and it just closes again:
Code: 
httpd not running, trying to start
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down

Quick manual fix:
  1. Search for ports in use:
    # lsof -i :80
    COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
    httpd 6617 apache 4u IPv6 527364 TCP *:www (LISTEN)
  2. Kill the process using the PID:
    # kill -9 6617

After that you can restart apache normally. But I'm really hoping directadmin can provide us with a permanent solution.

Here's wat seems to be a solution: http://help.directadmin.com/item.php?id=31. But it's an old help file, those files/paths are not available on my server. Plus I'm using Debian as well, and the commands there are for redhat/freebsd. :( Is this custombuild thing doing the same as described on that help-page?
Click to expand...

Hey Aero I'm having the exact same problem with this. Have you been able to find an actual fix? My problem is only one one server, and is _exactly_ the same as you describe.
 
switch said:
Hey Aero I'm having the exact same problem with this. Have you been able to find an actual fix? My problem is only one one server, and is _exactly_ the same as you describe.
Click to expand...
No, we are now sponsored (by the same webhoster), and they would take care of all tech issues. But they also thought it would be better if we wouldn't use directadmin at all because of this problem. I guess they don't know how to fix it either, lol.

But, it does seem to be the apache-exim clash. On another webhosters-forum it was suggested to try this: http://help.directadmin.com/item.php?id=181
Basically the same as some of the offered solutions above, make sure apache does graceful restarts. I couldn't try out any of the solutions, so I don't know which works.

But imho it should be also fixed by DirectAdmin, changing the tally-script that checks for this problem with restarting apache. As this is something that runs daily, you'd expect a script that does not potentially crash your website.
 
You must log in or register to reply here.
Back
Top