I've reported this bug to Ubuntu.  The solution is to rebuild ruby1.8
without pthreads, unless ruby fixes the bug upstream which causes the
hang.

https://bugs.launchpad.net/ubuntu/+source/ruby1.8/+bug/520715

Joel

On Feb 10, 2:42 pm, Nigel Kersten <nig...@google.com> wrote:
> On Wed, Feb 10, 2010 at 11:48 AM, Nigel Kersten <nig...@google.com> wrote:
> > On Tue, Feb 9, 2010 at 5:06 AM, kai.steverding
> > <kai.steverd...@googlemail.com> wrote:
> >> I installed ruby on the above server and tried with a simple exec-
> >> test :
>
> >> class testmodule {
> >>                exec {"TEST-EXEC" :
> >>                        cwd => "/tmp/",
> >>                        command =>"/usr/bin/touch /tmp/7777 >/tmp/123 2>&1",
> >>                        timeout => 5,
> >>                        logoutput=> on_failure
> >>                }
> >> }
>
> >> This simple thing gets the following output from "puppet --debug --
> >> test"
>
> >> debug: Loaded state in 0.00 seconds
> >> info: Applying configuration version '1265719507'
> >> debug: //testmodule/Exec[TEST-EXEC]: Changing returns
> >> debug: //testmodule/Exec[TEST-EXEC]: 1 change(s)
> >> debug: //testmodule/Exec[TEST-EXEC]: Executing '/usr/bin/touch /tmp/
> >> 7777'
> >> debug: Executing '/usr/bin/touch /tmp/7777'
> >> err: //testmodule/Exec[TEST-EXEC]/returns: change from notrun to 0
> >> failed: Command exceeded timeout at /etc/puppet/modules/testmodule/
> >> manifests/init.pp:6
> >> debug: Finishing transaction 69914685668640 with 1 changes
> >> debug: Storing state
> >> debug: Stored state in 0.01 seconds
> >> debug: Format pson not supported for Puppet::Transaction::Report; has
> >> not implemented method 'from_pson'
> >> debug: Format s not supported for Puppet::Transaction::Report; has not
> >> implemented method 'from_s'
>
> >> What can I do ? Did i make a mistake, or is exec broken ?
>
> > Kai, something is definitely broken in Lucid.
>
> > We're seeing all sorts of process exec issues.
>
> > Have you nailed this down at all?
>
> So Kai, we've been doing some experimenting here today, and have
> reproduced these hangs in all the Debian Ruby1.8 packages back to
> 1.8.7.174-2.
>
> 1.8.7.174-1 we've been unable to reproduce it on though.
>
> From the changelog I'm wondering if the first entry under 174-2 is
> responsible. Note this was later removed after upstream integrated it.
>
> ruby1.8 (1.8.7.174-2) unstable; urgency=medium
>
>    [ akira yamada ]
>    * Added debian/patches/090811_thread_and_select.dpatch: threads may hangup
>      when IO.select called from two or more threads.
>    * Added debian/patches/090812_finalizer_at_exit.dpatch: finalizers should 
> be
>      run at exit (Closes: #534241)
>    * Added debian/patches/090812_class_clone_segv.dpatch: avoid segv when an
>      object cloned.  (Closes: #533329)
>    * Added debian/patches/090812_eval_long_exp_segv.dpatch: fix segv when eval
>      a long expression.  (Closes: #510561)
>    * Added debian/patches/090812_openssl_x509_warning.dpatch: suppress warning
>      from OpenSSL::X509::ExtensionFactory.  (Closes: #489443)
>
>    [ Lucas Nussbaum ]
>    * Removed Fumitoshi UKAI <u...@debian.or.jp> from Uploaders. Thanks a
>      lot for the past help! Closes: #541037
>
>    [ Daigo Moriwaki ]
>    * debian/fixshebang.sh: skip non-text files, which works around hanging of
>      sed on scanning gif images.
>    * Bumped up Standards-Version to 3.8.2.
>
> --
> nigel

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to