I¹m trying to rig puppetd (0.24.4) to run from cron on Solaris 10 with ³--onetime --splay ‹-splaylimit 900² using Ruby 1.8.6. puppetd runs just fine from an interactive shell, but segfaults in timeout.rb when run from cron: /opt/coolstack/lib/ruby/1.8/timeout.rb:52: [BUG] Segmentation fault ruby 1.8.6 (2007-09-23) [sparc-solaris2.10] What little I can find via Google that looks relevant appears to be in Japanese, which isn''t terribly helpful to me. Has anyone else come across this? Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Apr 29, 2008, at 12:58 AM, Matt McLeod wrote:> > I¹m trying to rig puppetd (0.24.4) to run from cron on Solaris 10 with > ³--onetime --splay ‹-splaylimit 900² using Ruby 1.8.6. puppetd runs > just > fine from an interactive shell, but segfaults in timeout.rb when run > from > cron: > > /opt/coolstack/lib/ruby/1.8/timeout.rb:52: [BUG] Segmentation fault > ruby 1.8.6 (2007-09-23) [sparc-solaris2.10] > > What little I can find via Google that looks relevant appears to be in > Japanese, which isn''t terribly helpful to me. Has anyone else come > across > this?In general, we''ve found that segfaults are specific to the build of ruby you''re using, which makes them nearly impossible to track down and thus impossible to fix. You might just try with a different version of ruby, even an older one. -- Those who speak most of progress measure it by quantity and not by quality. --George Santayana --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
> In general, we''ve found that segfaults are specific to the build of > ruby you''re using, which makes them nearly impossible to track down > and thus impossible to fix. > > You might just try with a different version of ruby, even an olderone. Is there a version considered "most stable"? Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Git HEAD :) Arjuna Christensen | Systems Engineer Maximum Internet Ltd DDI: + 64 9 913 9683 | Ph: +64 9 915 1825 | Fax:: +64 9 300 7227 arjuna.christensen@maxnet.co.nz| www.maxnet.co.nz -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of McLeod, Matt Sent: Wednesday, 30 April 2008 11:20 a.m. To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: Ruby sefault from cron> In general, we''ve found that segfaults are specific to the build of > ruby you''re using, which makes them nearly impossible to track down > and thus impossible to fix. > > You might just try with a different version of ruby, even an olderone. Is there a version considered "most stable"? Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Apr 29, 2008, at 6:19 PM, McLeod, Matt wrote:> >> In general, we''ve found that segfaults are specific to the build of >> ruby you''re using, which makes them nearly impossible to track down >> and thus impossible to fix. >> >> You might just try with a different version of ruby, even an older > one. > > Is there a version considered "most stable"?More recent versions of Ruby are usually better, but again, sometimes it''s just the specific compile, so I can''t say whether a given version will work. -- I have lost friends, some by death... others through sheer inability to cross the street. -- Virginia Woolf --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> On Apr 29, 2008, at 6:19 PM, McLeod, Matt wrote: > > Is there a version considered "most stable"? > > More recent versions of Ruby are usually better, but again, sometimes > it''s just the specific compile, so I can''t say whether a given version > will work.OK. For the record, the current "stable-snapshot" seems to be OK, as is 1.8.4. But not the couple of 1.8.6 versions I tried. Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---