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

[Martin Jackson (JIRA)]

Title: Message Title

Martin Jackson commented on an issue   Re: "current thread not owner" after Puppet Agent receives USR1 signal I see the same behavior on Fedora 20 with the system ruby interpreter and the puppetlabs puppet package. This is triggered through the "mco puppet runonce" MCollective plugin. Mar 9 18:10:13 ori puppet-agent[4858]: Caught USR1; calling reload Mar 9 18:10:13 ori puppet-agent[5047]: Could not autoload puppet/indirector/node/rest: current thread not owner Mar 9 18:10:13 ori puppet-agent[5047]: Unable to fetch my node definition, but the agent run will continue: Mar 9 18:10:13 ori puppet-agent[5047]: Could not autoload puppet/indirector/node/rest: current thread not owner Mar 9 18:10:13 ori puppet-agent[5047]: Could not autoload puppet/feature/external_facts: current thread not owner Mar 9 18:10:13 ori puppet-agent[5047]: Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner [root@ori ~]# ruby -v ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux] [root@ori ~]# rpm -qa | grep puppet mcollective-puppet-common-1.7.0-1.fc20.noarch mcollective-puppet-agent-1.7.0-1.fc20.noarch puppetlabs-release-20-10.noarch puppet-3.4.3-1.fc20.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.