| Summary: | Broker / mcollective commands sometimes hang | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OKD | Reporter: | Thomas Wiest <twiest> | ||||
| Component: | Containers | Assignee: | Dan McPherson <dmcphers> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 2.x | CC: | blentz, dmcphers, jhou, junpark, mmcgrath, rmillner | ||||
| Target Milestone: | --- | Keywords: | Security, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-14 00:59:33 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Thomas Wiest
2012-02-08 01:22:58 UTC
I don't know how to recreate this in dev. But where ever this happens we need to: require 'thread-dump' in the source (note you need the latest broker to do this) when it hangs kill -3 the process. That should let us know where it is hanging. *** Bug 783175 has been marked as a duplicate of this bug. *** Created attachment 564016 [details]
Stack trace / thread-dump from a hung mc-ping process
I was able to re-create the mc-ping hang with an mc-ping that had thread-dump enabled.
Attached is the output from mc-ping and the thread-dump.
Just to update the bug, we've tracked this down to a bug in Ruby 1.8 and it's "green threads". This is basically making timeout.rb unreliable. See an explanation here: http://ph7spot.com/musings/system-timer We're looking at fixing this issue in 2 ways: 1) Upgrade to Ruby 1.9 on the brokers (and devenv and what not). 2) See if you could get the SystemTimer working with Ruby 1.8 (from the link above). Wasn't this fixed a long time ago? Broker has been updated to ruby-1.9 a long time ago. So this bug should have already been fix for a long time. Didn't reproduce on devenv, so moving this bug to verified. |