This is not an indication of hardware problems. yoursite.com loads fine. If there is a problem you would like us to address, please describe it in more detail.
Thank you for choosing Rackshack!!! "
i got errors when restarting httpd
"service httpd restart
Shutting down http: /etc/init.d/httpd: kill: (5570) - No such pid
/etc/init.d/httpd: kill: (5569) - No such pid
/etc/init.d/httpd: kill: (5568) - No such pid
/etc/init.d/httpd: kill: (5567) - No such pid
/etc/init.d/httpd: kill: (5566) - No such pid
/etc/init.d/httpd: kill: (5565) - No such pid
/etc/init.d/httpd: kill: (5564) - No such pid
/etc/init.d/httpd: kill: (5563) - No such pid
/etc/init.d/httpd: kill: (5562) - No such pid
/etc/init.d/httpd: kill: (5561) - No such pid
Well howard RackShack has UN-managed servers, they take care of hardware problems only. If there is a Apache httpd error that is a software issue. They do not support software it is up to you and you alone.
check your server for oversized logfiles.... that's one of the first things I learned when I got my RS server. when they get over 2GB (which can happen in no time with a large site, which from your bandwidth usage it seems yours is) the server quickly bogs down very badly. My box has plesk so my paths probably are different a bit than your Ensim ones.... but check the size of the logs in (again, these are my locations):
I've also had instances where dns_cache.db has got too large for the space limitation of a particular site (could not figure out why).... Plesk uses Webalizer for stats, and that is located in the httpdocs/webstat folders for vhosts in Plesk - I think Ensim uses Analog for stats and I'm not sure if that can have a similar problem - worth checking into though.
Anyhow, check all those places for oversized files. If you find huge files, consider clearing them, and finding a way to ensure they never reach that huge size again (log rotation, earlier deletion, etc). There's a few ways to clear them.... often I find just typing:
does the trick. Sometimes though you need to:
And once you've done that, you should check to make sure your logging services are all still working... I've found that after a log hits 2+ GB often logging for the whole server can be switched off. In that case, restart the "system logging daemon":
killall -HUP syslogd
When you have a log exceed 2GB, another problem happens that makes matters worse.... your /usr/local/psa/apache/logs/error_log begins growing rapidly as well with entries concerning the other oversized log. So always check that file too.
Anyhow - I'm no expert.... just trying to relay what I've learned in the last 6 months or so since I had to cancel my managed server with Rackspace and move to Rackshack so I could afford to stay in the game
Oh and.... I would advise you NOT to take that advice in the above post by Paul (no offense).... in that, you really do need to "do stuff" to your server, or it definately "will" break - when RS gives it to you, it is usually hugely insecure, with somewhat outdated software versions, telnet instead of SSH, no firewall rules, etc. You need to address all that immediately or risk being hacked in no time. Besides that, I've found Plesk/Ensim can be a bit stupid at times, and require you to get into SSH and fix/restart things.
Anyhow, I dunno if the logfiles thing is the problem in your case... maybe maybe not. Hopefully it will help someone though hehe