Issue #22008 has been updated by Charlie Sharpsteen. Status changed from Unreviewed to Accepted Target version set to 3.x Keywords set to signal trap
Thanks for reporting this. It looks like the signal handlers will have to be re-written so that they can be safely called within Trap contexts. ---------------------------------------- Bug #22008: Puppet does not work with ruby2 properly. https://projects.puppetlabs.com/issues/22008#change-95819 * Author: David K * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: 3.x * Affected Puppet version: 3.2.3 * Keywords: signal trap * Branch: ---------------------------------------- ruby2 has messed up signal handling. kill -HUP -USR1, etc on the puppet agent process causes it to bail out completey with errors like: puppet-agent[11759]: Could not run: can’t be called from trap context <https://github.com/mperham/sidekiq/commit/fb2c286506107dc0d5d3f297c19df8170b32ef54#L1R3> <https://bugs.ruby-lang.org/issues/7917> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
