Restarting Apache on Bluehost
Posted in North Star Labs, System Administration on 06/08/2007 02:52 pm by jmccuneI have a dedicated IP address on a shared hosting server from bluehost.com. This setup is working well for me; my goal is to run a subversion server with public http and https access, authenticated users for commit access, Trac project management, and a blog. The only issue I’ve really run into is bluehost binds to port 80 and 443 with their virtualhost apache server, so even though I have a dedicated IP, these ports are already bound. As a result, I simply run the subversion server on an alternate port.
Sometimes, however, my custom build of Apache would die off and the subversion server would be down. I wrote a small bash script and configured my bluehost account to execute this script fairly frequently to make sure apache is always running. A bit dirty, but it works. If you running a similar setup, you may be interested in the apache restart script.
The script is: check_httpd.sh.
09/27/2007 at 12:41 am
I have been trying to get this thing off ground and gawd it wont allow me at all. Now that i know that we need to have a dedicated IP to run this thing…DAmN
09/27/2007 at 8:26 am
Yeah, the dedicated IP address is definitely required if you want to run any sort of server. I’ve found that bluehost is pretty good about letting you run a fair number of processes at the same time, but a friend of mine just ran into an issue where his main page would come up completely blank. It turned out to be that his Mail client was creating a lot of connections to the IMAP server, and he was running into the process limit.
I think the process limit is around 20 or so, and my Apache2 spawns 6 processes by default. I’ve never had to reduce that number, but the process limit is just something to keep in mind.
-Jeff
02/25/2008 at 5:34 pm
Jeff:
I kinda need that shell script coz i lost it. And not its not accesible.
Could you send me a copy?
Thanks