<?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>Kernel-Panik.com &#187; CentOS</title>
	<atom:link href="http://www.kernel-panik.com/wordpress/category/linux/centos/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kernel-panik.com/wordpress</link>
	<description>science, technology, linux, howto&#039;s</description>
	<lastBuildDate>Tue, 27 Oct 2009 08:49:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>rpmforge sarg 2.2.3.1-1 x64 package bug on CentOS 5.3</title>
		<link>http://www.kernel-panik.com/wordpress/2009/07/15/rpmforge-sarg-bug-centos/</link>
		<comments>http://www.kernel-panik.com/wordpress/2009/07/15/rpmforge-sarg-bug-centos/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 07:43:56 +0000</pubDate>
		<dc:creator>Jorge_S</dc:creator>
				<category><![CDATA[CentOS]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[rpmforge]]></category>
		<category><![CDATA[sarg]]></category>
		<category><![CDATA[segfault]]></category>

		<guid isPermaLink="false">http://www.kernel-panik.com/wordpress/?p=34</guid>
		<description><![CDATA[While running /etc/cron.daily/sarg against a medium size squid access.log file, this error showed on the screen of a CentOS 5.3 x64 box:
&#8220;sarg[5646]: segfault at 000000008d784200 rip 0000003280078d80 rsp 00007fff8d784d78 error 4&#8243;
After googling for a while I found this thread explaining similar problems. Apparently the current sarg rpmforge package for RHEL 5 x64 has some kind [...]]]></description>
			<content:encoded><![CDATA[<p>While running /etc/cron.daily/sarg against a medium size squid access.log file, this error showed on the screen of a CentOS 5.3 x64 box:</p>
<p style="padding-left: 30px;">&#8220;sarg[5646]: segfault at 000000008d784200 rip 0000003280078d80 rsp 00007fff8d784d78 error 4&#8243;</p>
<p>After googling for a while I found <a title="centos.org forums" href="http://www.centos.org/modules/newbb/viewtopic.php?topic_id=16303" target="_blank">this thread</a> explaining similar problems. Apparently the current sarg rpmforge package for RHEL 5 x64 has some kind of bug when dealing with long url&#8217;s. I also noticed that at the <a title="rpmforge sarg package listing" href="http://packages.sw.be/sarg/" target="_blank">rpmforge repository for sarg</a> there is a newer version, <a href="http://packages.sw.be/sarg/sarg-2.2.5-1.fc9.rf.i386.rpm">sarg-2.2.5-1</a>, but the aren&#8217;t packages for  RHEL 5 x86 x64 arquitecture, only for FC and RHEL PPC.</p>
<p>The fix is pretty simple, just uninstall the x64 version and install the i386 version. /etc/cron.daily/sarg will ran without problems after changing to the x86 version.</p>
<p>At the time  this post was written, latest rpmforge sarg packages for CentOS 5 x64 &amp; i386 were:</p>
<p style="padding-left: 30px;"><a href="http://packages.sw.be/sarg/sarg-2.2.3.1-1.el5.rf.x86_64.rpm">sarg-2.2.3.1-1.el5.rf.x86_64.rpm</a> &lt;&#8211; I was using this when I got the error</p>
<p style="padding-left: 30px;"><a href="http://packages.sw.be/sarg/sarg-2.2.3.1-1.el5.rf.i386.rpm">sarg-2.2.3.1-1.el5.rf.i386.rpm</a> &lt;&#8211; changing to this one fixed the problem</p>
<p>I did this for changing the package version:</p>
<ul>
<li>rpm -ev rpm -ev sarg-2.2.3.1-1.el5.rf</li>
<li>wget http://packages.sw.be/sarg/sarg-2.2.3.1-1.el5.rf.i386.rpm</li>
<li>yum localinstall sarg-2.2.3.1-1.el5.rf.i386.rpm</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.kernel-panik.com/wordpress/2009/07/15/rpmforge-sarg-bug-centos/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
