[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: mount resource segfault

[Mark Rechler < >]

Hi James,

Yes, I tested the frameos package for the segfault and had the same issue (sorry if I was unclear when I said the package was fine, I meant it was built correctly/met dependencies for chef). I did not get a chance to test the aegisco package. Also, it turned out the segfault point was random (just seemed to be hitting the mount resource more often than not). I'm wondering if it's an issue with this particular patchset of ruby 1.8.7.

Mark 

On Thu, May 5, 2011 at 12:18 PM, James < "> > wrote:

Mark,

Did you test the 1.8.7 package in frameos or rpm.aegisco.com against the segfaulting mount provider?

James

On Thu, May 5, 2011 at 9:12 AM, Mark Rechler < " target="_blank"> > wrote:

The ruby 1.8.7 install was built by tweaking the centos spec file. For 1.9, this was the specfile used:
https://github.com/imeyer/ruby-1.9.2-rpm/blob/master/ruby19.spec
This spec file provides everything in 1 rpm, vs splitting them all. I had tried using FrameOS's rpms from the rbel repo (http://rbel.frameos.org/), but they were somewhat broken (I should say just their 1.9 seemed to be missing some dependencies, the 1.8.7 packages are fine).

On Thu, May 5, 2011 at 12:04 PM, Bryan McLellan < " target="_blank"> > wrote:

On Thu, May 5, 2011 at 8:48 AM, Mark Rechler < " target="_blank"> > wrote:
> Just thought I would update the thread. Upgrading to ruby 1.9.2 resolved the
> segfault issues. Still not sure why they were occurring in 1.8.7 though.

Was the Ruby 1.8.7p334 installation you were using from the original
CentOS 5.6 RPM installation?

How did you install Ruby 1.9.2? If from RPMs, where did you get them from?

Bryan