segmentation fault on knife bootstrap
Bryan Berry
bootstrap on a node
RHEL 6.2, x86_64
sorry I don't have more info right now
s/repository.rb line 33)
hqlprfenixsql1 [Fri, 16 Dec 2011 16:58:36 +0100] INFO: execute[yum -q
makecache] sh(yum -q makecache)
hqlprfenixsql1 [Fri, 16 Dec 2011 16:59:32 +0100] INFO: execute[yum -q
makecache] ran successfully
hqlprfenixsql1 [Fri, 16 Dec 2011 16:59:32 +0100] INFO: Processing
bash[remove_vmware_tools] action run (vmware-tools::default line 12)
hqlprfenixsql1 [Fri, 16 Dec 2011 16:59:33 +0100] INFO: Processing
remote_file[/var/chef/cache/VMwareTools-8.3.7-341836.tar.gz] action
create (vmware-tools::default line 29)
hqlprfenixsql1 /usr/lib/ruby/1.8/timeout.rb:58: [BUG] Segmentation fault
hqlprfenixsql1 ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
hqlprfenixsql1
rubiojr
> I am getting a segmentation fault pretty consistently when I run knife
> bootstrap on a node
>
> RHEL 6.2, x86_64
>
> sorry I don't have more info right now
Thanks Bryan, gonna try to reproduce this.
If possible, could you please share all the cookbooks you are using
when bootstrapping and the bootstrap config file?
Output from rpm -qa, gem env output and cookbook versions will also
help.
I assume that you're using pure RHEL as CentOS/Scientific 6.2 aren't
out yet. Correct?
Bryan Berry
https://github.com/bryanwb/cookbooks
I use the following recipes
recipe[yumrepo::corporate]
recipe[chef-client::cron]
recipe[sudo]
recipe[VRTSralus]
recipe[nagios::xinetd]
recipe[vmware-tools]
recipe[java]
recipe[resolver]
recipe[ntp]
recipe[sendmail]
I am using RHEL 6.2 and not centos
i am on holidays and away from the office so will have to see about
getting you the other info
Bryan Berry
this happens on knife bootstrap and chef-client
however, I don't get the segmentation fault if I run chef-client -l debug
I am using RHEL 6.2 and not CentOS 6.2
I have attached the gem env and the rpms that are installed, i hope that helps
I am using the latest versions of the cookbooks in my repo
Bryan Berry
I don't get the segmentation fault when i use that Red Hat's version,
not quite sure why
here is the info on the package from red hat
[root@myhost1 ~]# rpm -qi ruby
Name : ruby Relocations: (not relocatable)
Version : 1.8.7.352 Vendor: Red Hat, Inc.
Release : 3.el6 Build Date: Fri 12 Aug
2011 03:41:37 PM CEST
Install Date: Thu 05 Jan 2012 02:10:48 PM CET Build Host:
x86-003.build.bos.redhat.com
Group : Development/Languages Source RPM:
ruby-1.8.7.352-3.el6.src.rpm
Size : 1895995 License: Ruby or GPLv2
Signature : RSA/8, Thu 22 Sep 2011 01:01:03 PM CEST, Key ID 199e2f91f
2012/1/5 Bryan Berry <bryan...@gmail.com>:
Bryan Berry
I have found an incredibly ugly hack to get around segmentation fault
problem on RHEL 6.2. I use the RHEL ruby rpms and the ruby-devel from
the rbel repo, which Red Hat doesn't provide
Here is my bootstrap script for RHEL 6.2
https://gist.github.com/1565379
I believe that Opscode is creating a new community application
crumbs.opscode.com, snippets for chefs. That site will be ideal for
storing and finding bootstrap scripts
rubiojr
was available in 6.2...
On 5 ene, 15:05, Bryan Berry <bryan.be...@gmail.com> wrote:
> Alright,
>
> I have found an incredibly ugly hack to get around segmentation fault
> problem on RHEL 6.2. I use the RHEL ruby rpms and the ruby-devel from
> the rbel repo, which Red Hat doesn't provide
http://mirror.centos.org/centos/6.2/os/x86_64/Packages/ruby-devel-1.8.7.352-3.el6.x86_64.rpm
I need to have a look at RHEL 1.8.7-p352 and see if they've added
patches to fix the segfaults or if it's just a build env/flags issue.
Anyway, having p352 in upstream renders RBEL ruby packages for RHEL6
useless. I'll probably replace RBEL ruby with RHEL packages soon and
backport the packages to RBEL5 too.
>
> Here is my bootstrap script for RHEL 6.2https://gist.github.com/1565379
> I believe that Opscode is creating a new community application
> crumbs.opscode.com, snippets for chefs. That site will be ideal for
> storing and finding bootstrap scripts
Rgds.
Bryan Berry
ruby-devel package? or would it be a waste of time?
so will you also stop maintaining the ruby-devel package as well?
rubiojr
> Do you think red hat would be responsive if I asked them to add the
> ruby-devel package? or would it be a waste of time?
their repos/DVDs is a good idea IMHO.
> so will you also stop maintaining the ruby-devel package as well?
I won't remove ruby/ruby-devel from RBEL6 no worries. Doing that would
break stuff for sure.
>
>
>
>
>
>
> On Thu, Jan 5, 2012 at 3:52 PM, rubiojr <el.canig...@gmail.com> wrote:
> > Hey Bryan, thanks a lot for all the input. Didn't realize 1.8.7-p352
> > was available in 6.2...
>
> > On 5 ene, 15:05, Bryan Berry <bryan.be...@gmail.com> wrote:
> >> Alright,
>
> >> I have found an incredibly ugly hack to get around segmentation fault
> >> problem on RHEL 6.2. I use the RHEL ruby rpms and the ruby-devel from
> >> the rbel repo, which Red Hat doesn't provide
>
> > Weird they don't have it, it's available in CentOS 6.2 in any case:
>
rubiojr
I've been stressing the current RBEL6 ruby packages using CentOS6/6.2
and could reproduce the segfault unfortunately.
The tests included bootstrapping the node and running the yum-stress-
cookbook I had prepared for the occasion. I've used that cookbook in
the past to successfully crash 1.8.7 few months ago, but I did not
have luck this time.
Nevertheless, I've been looking at the changes included in the RHEL6.2
ruby package and they've included some really nice bits, like
systemtap support. Have a look at:
http://lukas.zapletalovi.com/2012/01/probing-ruby-apps-with-systemtap-in.html
I've uploaded backported package to RBEL6 testing repo and will be
moving that to stable after playing a little bit with it.
Cheers.
Bryan Berry
how can i access the testing repo? I have several machines to install
today and would be happy to use the packages in the testing repo.
I filed a ticket w/ RHEL asking them to publish a ruby-devel rpm, but
we will have to see where that goes.
rubiojr
> > I've been stressing the current RBEL6 ruby packages using CentOS6/6.2> and could reproduce the segfault unfortunately.
>
> did u mean "could _not_" here?
>
> how can i access the testing repo? I have several machines to install
> today and would be happy to use the packages in the testing repo.
upgrade repo --enablerepo rbel6-testing" ruby should work. Here's the
repo config just in case:
[rbel6-testing]
name = RBEL 6 Testing Repo
baseurl = http://rbel.frameos.org/testing/el6/$basearch
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RBEL
gpgcheck = 1
enabled = 0
>
> I filed a ticket w/ RHEL asking them to publish a ruby-devel rpm, but
> we will have to see where that goes.
>
Rgds.
>
>
>
>
>
>
> On Mon, Jan 9, 2012 at 6:33 PM, rubiojr <el.canig...@gmail.com> wrote:
> > Howdy Folks!
>
> > I've been stressing the current RBEL6 ruby packages using CentOS6/6.2
> > and could reproduce the segfault unfortunately.
>
> > The tests included bootstrapping the node and running the yum-stress-
> > cookbook I had prepared for the occasion. I've used that cookbook in
> > the past to successfully crash 1.8.7 few months ago, but I did not
> > have luck this time.
>
> > Nevertheless, I've been looking at the changes included in the RHEL6.2
> > ruby package and they've included some really nice bits, like
> > systemtap support. Have a look at:
>
Bryan Berry
buy u dinner
rubiojr
On 10 ene, 18:55, Bryan Berry <bryan.be...@gmail.com> wrote:
> tks again for all your help rubiojr! drop by Roma some time ;) i will
> buy u dinner
>
>
>
>
>
>
>
> On Tue, Jan 10, 2012 at 6:53 PM, rubiojr <el.canig...@gmail.com> wrote:
> > On 10 ene, 13:34, Bryan Berry <bryan.be...@gmail.com> wrote:
> >> > I've been stressing the current RBEL6 ruby packages using CentOS6/6.2> and could reproduce the segfault unfortunately.
>
> >> did u mean "could _not_" here?
>
> > Yeah, sorry.
>
> >> how can i access the testing repo? I have several machines to install
> >> today and would be happy to use the packages in the testing repo.
>
> > If you installed the repo using the repo package (rbel.co/rbel6), "yum
> > upgrade repo --enablerepo rbel6-testing" ruby should work. Here's the
> > repo config just in case:
>
> > [rbel6-testing]
> > name = RBEL 6 Testing Repo