Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal

[Logan Attwood (JIRA)]

Title: Message Title

Logan Attwood commented on an issue   Re: "current thread not owner" after Puppet Agent receives USR1 signal Also chiming in on this. [centos@galen-stage ~]$ ruby -v ruby 2.0.0p353 (2013-11-22) [x86_64-linux] [centos@galen-stage ~]$ rpm -qa | grep puppet puppetlabs-release-7-11.noarch puppet-3.7.1-1.el7.noarch mcollective-puppet-agent-1.9.1-1.el7.noarch mcollective-puppet-common-1.9.1-1.el7.noarch Add Comment   Puppet / PUP-1635 "current thread not owner" after Puppet Agent receives USR1 signal We're running the Puppet Agent daemonised, with {{splay}} enabled. We use the {{USR1}} signal to trigger an immediate reload and catalog run, bypassing the splay setting. This works fine in our other Ruby environment (1.9.3, various patch levels), but when testing under Ruby 2.0.0 and 2.1.0, we noticed that the signal would cause the catalog run to fai... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.