| Summary: | [vdsm] processPool processes does not always exit when vdsm dies | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jakub Libosvar <jlibosva> | ||||
| Component: | vdsm | Assignee: | Erez Shinan <erez> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Jakub Libosvar <jlibosva> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1 | CC: | abaron, bazulay, iheim, ilvovsky, ykaul | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | vdsm-4.9-66.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 07:14:47 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: |
|
||||||
Verified vdsm-4.9-67.el6.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2011-1782.html |
Created attachment 493481 [details] vdsm.log Description of problem: When running rhel6 host in 2.3 cluster in DC 2.2, vdsm is running a few processes on the host. If the parent of those processes is killed, child processes become orphans and keep runnning. Note that DC 2.2 is important in this case, in DC 2.3 there is not that amount of processes. Version-Release number of selected component (if applicable): ic114 vdsm-4.9-60.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Have rhel6.x host in DC2.2 2. Kill vdsm 3. Check running vdsm processes Actual results: Watchdog revives vdsmd and new duplicit processes are created Expected results: Oprhan processes dies with it's parent or are cleaned at new vdsm start Additional info: gdb of one of orphan processes pystack /usr/share/vdsm/storage/processPool.py (124): _helperMainLoop /usr/share/vdsm/storage/processPool.py (124): _helperMainLoop /usr/lib64/python2.6/multiprocessing/process.py (83): run /usr/lib64/python2.6/multiprocessing/process.py (215): _bootstrap /usr/lib64/python2.6/multiprocessing/forking.py (89): __init__ /usr/lib64/python2.6/multiprocessing/forking.py (89): __init__ /usr/lib64/python2.6/multiprocessing/process.py (90): start /usr/share/vdsm/storage/processPool.py (97): __init__ /usr/share/vdsm/storage/processPool.py (97): __init__ /usr/share/vdsm/storage/processPool.py (38): runExternally /usr/share/vdsm/storage/processPool.py (38): runExternally /usr/share/vdsm/storage/processPool.py (33): wrapper /usr/share/vdsm/storage/processPool.py (33): wrapper /usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles /usr/share/vdsm/storage/nfsSD.py (134): collectMetaFiles /usr/share/vdsm/storage/misc.py (1112): wrapper /usr/share/vdsm/storage/misc.py (1112): wrapper /usr/lib64/python2.6/threading.py (481): run /usr/lib64/python2.6/threading.py (513): __bootstrap_inner /usr/lib64/python2.6/threading.py (490): __bootstrap /usr/lib64/python2.6/threading.py (490): __bootstrap