Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Josh Cooper Status: Readyfor CI Test Assignee: KyloGinsberg QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Eric Thompson commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal verified on rhel7 at SHA: 1efdef31 after the USR1 agent reload: [root@gapx07egnoj17sp ~]# more /var/lib/puppet/reports/nqlel81tfk13bum.delivery.puppetlabs.net/201503092118.yaml --- !ruby/object:Puppet::Transaction::Report [snipped ...] - !ruby/object:Puppet::Util::Log level: !ruby/sym info tags: - info message: Applying configuration version '1425935911' source: Puppet time: 2015-03-09 14:18:31.427043 -07:00
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title John Duarte commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal QA Risk assessment = Medium Probability: Medium, lightly used feature, but will impact all who use it. Severity: Medium, work-arounds are available. Test layer prediction to come (unit, integration, acceptance). Currently, risk assessment of medium targets manual validation. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Steve Barlow Scope Change Reason: Community Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Michael Smith updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Michael Smith Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Re-opened to target at the next 3.x release. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal This can be verified without using mco. 1) Start a puppet master (webrick or puppet-server, whatever is easiest for you). It can be a little easier if you turn on --verbose, because it will be obvious when the agent checks in. 2) Start an agent daemonized pointing at the puppet master (you'll see that it checks in with the master, this is SOP not part of this fix). 3) Send the agent a USR1 signal. Find the agent pid, and issue 'kill -USR1 pid'. In about 5 seconds (exact timing isn't a requirement), you should see the agent checking in with the master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title John Duarte commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Verified with puppet-agent-0.3.2.90.gc5e3bb3-1 on RHEL 7. Install Puppet server Add `puppet` alias to master in /etc/hosts Install and start puppetserver on master node curl -O http://builds.puppetlabs.lan/puppet-agent/c5e3bb3384ba87507711dd2a2d70102e185388e5/artifacts/el/7/products/x86_64/puppet-agent-0.3.2.90.gc5e3bb-1.el7.x86_64.rpm curl -O http://nightlies.puppetlabs.com/puppetserver/2.0.0.SNAPSHOT.2015.02.25T1428/repos/el/7/products/x86_64/puppetserver-2.0.0.SNAPSHOT.2015.02.25T1428-1.el7.noarch.rpm rpm -ivh puppet-agent-0.3.2.90.gc5e3bb3-1.el7.x86_64.rpm yum -y install java-1.7.0-openjdk yum -y install net-tools rpm -ivh puppetserver-2.0.0.SNAPSHOT.2015.02.25T1428-1.el7.noarch.rpm systemctl enable puppetserver systemctl restart puppetserver
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg assigned an issue to QA Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Artifacts that passed CI at: http://builds.puppetlabs.lan/puppet-agent/c1ba5efb802bf23a032c47bfc2bf7e4b07516f66/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title John Duarte updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: John Duarte QA Contact: KurtWall JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: John Duarte Assignee: QA JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title John Duarte updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Sprint: Client2015-03- 18 04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Merged to master in https://github.com/puppetlabs/puppet/commit/6e6282f1784d315ade33a7077d62a9968abb1403. This will be released in puppet 4.0.0. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Eric Thompson commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal thanks for the analysis, everyone. this is great! just to clarify: part of our FR process will track the need for an acceptance test at medium priority in testrail. This will ensure we create an acceptance test... sometime Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Fix Version/s: PUP4.x Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Steve Barlow Sprint: Client2015-03-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Sprint: Client2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Sprint: Client2015-03-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kurt Wall updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kurt Wall QA Contact: NarmadhaPerumal KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Eric Thompson or Kurt Wall just a heads up that this ticket seems like a candidate for an acceptance test (spec tests can't really test the user contract here) to ensure we don't regress. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Kylo Ginsberg Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Lee Packham would you want to submit that as a pull request at https://github.com/puppetlabs/puppet? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Lee Packham commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal I'm running this version of lib/puppet/daemon.rb (which I cobbled together based on the issue and how it's best to get out of the context of the trap). https://gist.github.com/leepa/bf5ab312fbdb94750f49 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Henrik Lindberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Robin Bowes commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal This is just a me too comment. CentOS 7 ruby 2.0.0 (as supplied by CentOS) puppet 3.7.3 (from PL yum repo) mcollective 2.7.0 (from PL yum repo) mco puppet runonce causes puppet to fail with this output in /var/log/messages: Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26617]: Caught USR1; calling reload Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/indirector/node/rest: current thread not owner Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Unable to fetch my node definition, but the agent run will continue: Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/indirector/node/rest: current thread not owner Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Could not autoload puppet/feature/external_facts: current thread not owner Jan 22 23:45:55 ip-172-20-14-143 puppet-agent[26427]: Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Francois Conil commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Confirming another Jessie + puppet 3.7.3 case. Running puppet agent --test instead kill USR1 works as expected. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Jon Topper commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal I'm also seeing this on ruby 2.0.0p481 with puppet 3.4.2, and also ruby 2.1.5p273 and puppet 3.7.3 It seems to me like this might be related to the changes described in PUP-202 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Jon Topper commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Reading further, this ruby error seems to relate to bad synchronisation of resources across multiple threads. https://github.com/puppetlabs/puppet/commit/4da350b merged a number of changes to remove thread-related synchronsiation code under an assumption that Puppet isn't run in a multi-threaded environment - was that assumption incorrect? The output of 'ps -eLf' on my system suggests that the puppet agent does actually run across two threads, and strace shows calls to clone(2) going on. I can't see anything thready in the current Puppet codebase though. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Jon Topper commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal Ruling out my assumptions about https://github.com/puppetlabs/puppet/commit/4da350b since 3.3.2 (which doesn't have that commit in it) exhibits the same problem. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Jon Topper updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Jon Topper Comment: Rulingoutmyassumptionsabouthttps://github.com/puppetlabs/puppet/commit/4da350bsince3.3.2(whichdoesn'thavethatcommitinit)exhibitsthesameproblem. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Jon Topper commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal On this earlier hunch, I tried Puppet 3.3.2 (the last tagged version before the commit I mentioned earlier went in), running on Ruby 2.0. It gives different errors. Could not run: can't be called from trap context when sent a USR1. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Thomas Buts updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Thomas Buts Affects Version/s: PUP3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Chris Kuehl updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Chris Kuehl Environment: Ubuntu12.04.2LTSRuby2.0.0(patchlevel353)ORRuby2.1.0(patchlevel0)CentOS7Ruby2.0.0(patchlevel353) ORDebianjessie(2014-11-14)Ruby2.1.4p265puppet3.7.2-1 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Chris Kuehl commented on PUP-1635 Re: current thread not owner after Puppet Agent receives USR1 signal This also occurs on Debian jessie as of 2014-11-14 (ruby 2.1.4p265, puppet 3.7.2-1); I've also filed a Debian bug for it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769621 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title
max commented on an issue
Re: current thread not owner after Puppet Agent receives USR1 signal
+1
mcollective-puppet-common-1.9.1-1.el6.noarch mcollective-puppet-client-1.9.1-1.el6.noarch puppetlabs-release-6-11.noarch mcollective-puppet-agent-1.9.1-1.el6.noarch puppet-3.7.1-1.el6.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
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title
max commented on an issue
Re: current thread not owner after Puppet Agent receives USR1 signal
err Puppet Could not autoload puppet/indirector/node/rest: current thread not owner warning Puppet Unable to fetch my node definition, but the agent run will continue: warning Puppet Could not autoload puppet/indirector/node/rest: current thread not owner err Puppet Could not autoload puppet/feature/external_facts: current thread not owner err Puppet Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner
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
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
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
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Logan Attwood updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Logan Attwood Environment: Ubuntu12.04.2LTSRuby2.0.0(patchlevel353)ORRuby2.1.0(patchlevel0) CentOS7Ruby2.0.0(patchlevel353) Add Comment 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Andy Parker updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Andy Parker Component/s: CatalogApplication Add Comment 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Joshua Partlow Affects Version/s: 3.5.1 Add Comment 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.
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
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...
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Ryan Conway created an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Issue Type: Bug Affects Versions: 3.4.2 Assignee: Unassigned Created: 10/Feb/14 12:38 PM Environment: Ubuntu 12.04.2 LTS Ruby 2.0.0 (patchlevel 353) OR Ruby 2.1.0 (patchlevel 0) Labels: ruby2.0.0 ruby2.1.0 Priority: Normal Reporter: Ryan Conway 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 fail due to the following errors: Failed to apply catalog: Could not autoload puppet/feature/external_facts: current thread not owner Could not autoload puppet/feature/external_facts: current thread not owner Could not autoload puppet/indirector/node/rest:
