Issue #8753 has been updated by R.I. Pienaar. Status changed from Accepted to Needs More Information
Dan Carley wrote: > mcollectived seems to handle USR1 and USR2 signals (for reloading > agents/logs) badly if it's attempting to reconnect to a STOMP server at the > same time. > > If it's unable to connect to STOMP at startup and receives a signal then the > process exits abruptly. The following can be observed if running with > `daemonize = 0`: actually on closer inspection the best I can do here is to make it ignore USR1 till after connection since agents cant be loaded or reloaded before then. would that work? > If it's able to connect to STOMP on startup, but subsequently loses > connection and receives a signal then the following is repeated in quick > succession: not much I can do about this, I can try do a simple bit of code to reproduce this and file a bug - this is something in the stomp gem ---------------------------------------- Bug #8753: USR1/USR2 signals during connection retry causes exit https://projects.puppetlabs.com/issues/8753 Author: Dan Carley Status: Needs More Information Priority: Normal Assignee: R.I. Pienaar Category: Core Target version: 1.3.x Keywords: Branch: Affected mCollective version: 1.2.0 mcollectived seems to handle USR1 and USR2 signals (for reloading agents/logs) badly if it's attempting to reconnect to a STOMP server at the same time. If it's unable to connect to STOMP at startup and receives a signal then the process exits abruptly. The following can be observed if running with `daemonize = 0`: <pre> [root@xxx ~]# ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg connect to stomp.labs.xxx.com failed: Connection refused - connect(2) will retry(#0) in 5 connect to stomp.labs.xxx.com failed: Connection refused - connect(2) will retry(#1) in 5 connect to stomp.labs.xxx.com failed: Connection refused - connect(2) will retry(#2) in 5 /usr/libexec/mcollective/mcollective/connector/stomp.rb:128:in `connect': Could not connect to Stomp Server: SIGUSR1 (RuntimeError) from /usr/lib/ruby/site_ruby/1.8/mcollective/runner.rb:16:in `initialize' from /usr/sbin/mcollectived:57:in `new' from /usr/sbin/mcollectived:57 </pre> If it's able to connect to STOMP on startup, but subsequently loses connection and receives a signal then the following is repeated in quick succession: <pre> transmit to stomp.labs.xxx.com failed: stopping only thread note: use sleep to stop forever transmit to stomp.labs.xxx.com failed: stopping only thread note: use sleep to stop forever transmit to stomp.labs.xxx.com failed: stopping only thread note: use sleep to stop forever </pre> -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
