Server Administration

xCache is More Trouble than it’s Worth

Two servers and a just about every option variation later, I’ve officially given up on xCache.

The first round of problems involved caching config files and forms that needed to be updated all the time. I made exclude rules for those, and eventually it just got too long and became way too tedious to restart apache every time i changed a config file.

Second round of problems involved Apache segfaults. Happened to me twice in 12 hours and cost me a good amount of money as it happened at 5am the second time, and I didn’t log in to check my server until noon (because I was sleeping). 7 hours of downtime across multiple sites that my server hosts, and I’m out some cash because of it, and missed out on some traffic due to a digg’ed post that is currently about to break from upcoming into popular.

I’ve disabled xcache for now, and things seem to be stable again.

Running it, it saved me about .2 average load, and memory usage was about the same at 25% most the time.

I can’t say the site ran faster with it on either.

Maybe i’ll try it again in a later version, but in my opinion, version 1.2.1 is not all it’s cracked up to be.

Server Administration

How to View Apache error logs

If you’re new to running your own server, sometimes just finding things is the hardest thing to do. I spent a good 15 min trying to find mine, so here’s some info to help you.

Your system may vary. All my postings are from CentOS 5, running php 5.2.x, mysql 5.0.2x, and apache 2.2.x

You may need root-level access to see some of these as well.

I use pico. Some people like VI, some like VIM, some like NANO. I use pico. It’s just a text viewer.

View apache error_log

pico /usr/local/apache/logs/error_log

Send the text file to your website to make it viewable

cp /usr/local/apache/logs/error_log /home/SITEPATH/public_html

You can then view it in Firefox will open it up with out a download prompt.