[Mageia-sysadm] Puppet lockup, potential solution
Remy CLOUARD
shikamaru at mageia.org
Sat Jul 30 10:29:53 CEST 2011
On Mon, Jul 18, 2011 at 02:59:37PM +0200, Michael Scherer wrote:
> Hi,
>
> After trying the hardcore approach ( debugging, etc ), I decided to do a
> more complete search on the web, and found that :
> http://www.mail-archive.com/puppet-users@googlegroups.com/msg09156.html
>
> Basically, that's exactly the problem we see, and I have been able to
> reproduce on alamut, using the openssl speed trick.
>
> According to
> https://launchpad.net/debian/squeeze/+source/ruby1.8/+changelog
> the bug is fixed in 1.8.7.299
>
> Problem, we run :
> [root at alamut ~]# rpm -q ruby
> ruby-1.8.7.p249-4.1mdv2010.2
>
> So we have a few choice :
> - backport the patch
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580464 )
>
> - backport the whole ruby package
>
> - wait until we upgrade servers ( and kill all puppet process once per
> day )
>
> Any opinions ?
> --
> Michael Scherer
>
I’d say we backport the whole ruby package, since it will both fix
security issues (the reason for p334 is just that) and bugfixes.
I can do it if you agree on this.
Regards,
--
Rémy CLOUARD
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
More information about the Mageia-sysadm
mailing list