You might have noticed that State of Protest was down for quite some time. The reason was because it was waiting in the wings, static, for server techs to examine it so that they could tell me that, once again, it’s my fault that when the server reboots, I can’t even get remote access to it, and that most of the basic startup services don’t even come on like they’re supposed to, regardless of the fact that I haven’t changed a thing in that regard.
Besides the fact that I’m running only ONE website from a Virtual Dedicated Server, with a practically barebones Wordpress installation, as soon as I get a few hundred hits, BAM, it shuts down. Obviously, my only option is to buy more and more memory! Yay! Seriously, though, there’s no good reason why a VDS server that I’m paying $30+ a month for should shut down running a single application of WordPress.
Okay, any Linux gurus out there want to give me a hand?
First, I’m getting a “Unknown HZ value! () Assume 100. Internal error!” error, related supposedly to procps. Server techs suggest reprovisioning the server, which means wiping it clean and starting again from scratch. I’m inclined to think that’s bularky, since I haven’t made squat for changes to anything that would have any effect on procps or anything outside of just what I’ve uploaded to httpd. Plus, that’s just a lot more down time for my server, and makes me have to redo the entire thing from scratch (it’s my last resort). My research tells me that I might fix it by upgrading procps to latest version, but I can’t even figure out how to tell what version I currently have. (I’m no Linux hack).
I’m honestly very tired of dealing with my hosting provider’s server experts, who always end up telling me I need more memory and need to upgrade. I had server issues before, on a shared server, and upgraded to the VDS, which took care of most, if not all, of the issues, but then, bam, I get some attention and it goes all wacky. So, if anyone wants to assist, please let me know either via comments or email: procrustes AT stateofprotest DOT com (assuming it’s working). I’d be eternally grateful, and even give you mad props if you assist. (Sorry, ran out of cookies).
Hello,
The issue you are facing is due to kernel issue. Please try upgrading your kernel(try via yum, its much safer ) to the latest release. Also to know your current of kernel issue command “uname -a”. To know the current version of procp installed issue command “yum list procps”.
You rock. Thanks!