help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Segmentation Fault in cfagent on RH EL-3.0 updates 3,5


From: Mark Burgess
Subject: Re: Segmentation Fault in cfagent on RH EL-3.0 updates 3,5
Date: Thu, 30 Jun 2005 09:24:28 +0200

Gary - what version of libc are you running?
This looks as thought the bug occurs inside the readdir() code.
I saw some patches to libc recently on SuSE linux. Perhaps there is
an upgrade you can make and try again?

I'm not sure that this can be a cfengine bug per se.

M

On Wed, 2005-06-29 at 08:54 -0700, Gary Meyer wrote:
> The very first thing I did, was to download the latest stable source 
> code, and rebuild it right on the box that had been newly installed 
> with EL3 Update 5.  I was hoping that either someone else had fixed the 
> problem(s) or that rebuilding the tool would solve it.  Unfortunately 
> for me, the guys who built the older version of CFEngine at my company 
> are long gone, so I don't really know if they had to use some weird 
> flags in building CFEngine.  It seemed to me that I could probably do 
> with a simple "./configure", but that doesn't seemed to have helped.  
> There are several hundred packages that have been changed by RedHat 
> between 3.0 with no updates and update 5, and I thought that rebuilding 
> CFEngine would fix that.  Unfortunately it didn't.
> Gary.
> =============================
> Gary Meyer
> Configuration Management Engineer
> Process Engineering
> Caspian Networks
> gmeyer@caspiannetworks.com
> 
> On Jun 28, 2005, at 11:18 PM, Mark Burgess wrote:
> 
> >
> > This sounds a little strange. The trouble with free segfaults is that
> > they are impossible to track down. It might even be the version of libc
> > that you have. Perhaps you could collect a few of these and see if 
> > there
> > is a pattern. Often this kind of thing can occur due to build errors,
> > e.g. mixed up library versions.  Have you considered rebuilding 
> > cfagent?
> >
> > Mark
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]