<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SkeyMedia &#187; server</title>
	<atom:link href="http://skeymedia.com/tag/server/feed/" rel="self" type="application/rss+xml" />
	<link>http://skeymedia.com</link>
	<description>Blogging about Web Development and Website Management &#38; Monetization</description>
	<lastBuildDate>Sun, 20 Sep 2009 23:18:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Getting the Big &#8220;Oops&#8221; from a Server</title>
		<link>http://skeymedia.com/getting-the-big-oops-from-a-server/</link>
		<comments>http://skeymedia.com/getting-the-big-oops-from-a-server/#comments</comments>
		<pubDate>Thu, 15 Nov 2007 05:15:35 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Server Administration]]></category>
		<category><![CDATA[putty]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[xcache]]></category>

		<guid isPermaLink="false">http://skeymedia.com/getting-the-big-oops-from-a-server/</guid>
		<description><![CDATA[I had some minor problems with xCache recently that ended up causing segfaults in my apache install. I had left my SSH putty session open last night and didn&#8217;t check my laptop before I trecked into the office this morning (yes, some of us bloggers still have 9-5&#8242;s). When I got to work, I noticed [...]]]></description>
			<content:encoded><![CDATA[<p>I had some minor <a href="http://skeymedia.com/xcache-is-more-trouble-than-it-s-worth/">problems with xCache</a> recently that ended up causing segfaults in my apache install.  I had left my SSH putty session open last night and didn&#8217;t check my laptop before I trecked into the office this morning (yes, some of us bloggers still have 9-5&#8242;s).  When I got to work, I noticed my server was down.  I had to hard reboot it through the IPMI switch at my data center.  I removed xCache from my php.ini and things have been solid since.</p>
<p>I came home from work and looked at my putty session and got a good laugh.  &#8220;Oops&#8221; it tells me.  haha.  I had a good chuckle about it.</p>
<p><a href='http://skeymedia.com/wp-content/uploads/2007/11/opps.GIF' title='Oops'><img src='http://skeymedia.com/wp-content/uploads/2007/11/opps.thumbnail.GIF' width='250' height='174' title='Opps' alt='Oops' /></a></p>
<blockquote><p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: Oops: 0002 [#1]</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: SMP</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: CPU:    1</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: EIP is at kernel_thread_helper+0&#215;7/0&#215;10</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: eax: 00000000   ebx: c0434cd9   ecx: ffffffff   edx: ffffffff</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: esi: 00000000   edi: 00000000   ebp: 00000000   esp: e8121fe8</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: ds: 007b   es: 007b   ss: 0068</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: Process pdflush (pid: 8071, ti=e8121000 task=f67d3000 task.ti=e8121         000)</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:13 2007 &#8230;<br />
sv03 kernel: Stack: c2858f60 00000000 00000000 00000000 00000000 00000000</p>
<p>Message from syslogd@sv03 at Wed Nov 14 04:56:14 2007 &#8230;<br />
sv03 kernel: Call Trace:
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://skeymedia.com/getting-the-big-oops-from-a-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>xCache is More Trouble than it&#8217;s Worth</title>
		<link>http://skeymedia.com/xcache-is-more-trouble-than-it-s-worth/</link>
		<comments>http://skeymedia.com/xcache-is-more-trouble-than-it-s-worth/#comments</comments>
		<pubDate>Wed, 14 Nov 2007 21:29:44 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Server Administration]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[segfault]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[xcache]]></category>

		<guid isPermaLink="false">http://skeymedia.com/xcache-is-more-trouble-than-it-s-worth/</guid>
		<description><![CDATA[Two servers and a just about every option variation later, I&#8217;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 [...]]]></description>
			<content:encoded><![CDATA[<p>Two servers and a just about every option variation later, I&#8217;ve officially given up on xCache.</p>
<p>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.</p>
<p>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&#8217;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&#8217;m out some cash because of it, and missed out on some traffic due to a digg&#8217;ed post that is currently about to break from upcoming into popular.</p>
<p>I&#8217;ve disabled xcache for now, and things seem to be stable again.  </p>
<p>Running it, it saved me about .2 average load, and memory usage was about the same at 25% most the time.</p>
<p>I can&#8217;t say the site ran faster with it on either.</p>
<p>Maybe i&#8217;ll try it again in a later version, but in my opinion, version 1.2.1 is not all it&#8217;s cracked up to be.</p>
]]></content:encoded>
			<wfw:commentRss>http://skeymedia.com/xcache-is-more-trouble-than-it-s-worth/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
