Sorry about the delay, On Fri, 1 Jan 2016 18:08:41 +0000 Victor Orlikowski <[email protected]> wrote:
> Folks, > > So - in our controller application here at Duke, we’ve added enabled the use > of eventlet.backdoor to help us debug greenlet issues. > > It’s been a real help - but it concerns me due to: > 1) Effectively being a security vulnerability > 2) Being disabled by fellow administrators *because* of being a security > vulnerability (and thereby being unavailable for debugging issues when they > happen). > > It seems that the OpenStack folks have had this same concern, and have > proposed the following solution: > > https://wiki.openstack.org/wiki/GuruMeditationReport > > Extending the above, I’d like to be able to (for example) get a “thread dump” > of the greenlets in a running instance of Ryu; that’s what I did for > debugging some of the issues I’ve been submitting patches for, using the > following bits of code as examples: > > http://docs.openstack.org/developer/ironic/_modules/ironic/openstack/common/eventlet_backdoor.html > > Would there be overall interest in my submitting a patch to provide a signal > handler for, say, SIGQUIT (a la Java) or SIGUSR1 to provide an error report > in a user-configurable location? It seems overdue, for live debugging and > error reporting by end users. Sounds reasonable to me. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
