Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 479087[details]
vdsm log
Description of problem:
In case libvirt crashes- vdsm watchdog will stop trying to restart after 30 seconds:
Feb 16 11:40:20 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:24 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:29 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:34 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:39 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:43 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:48 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave
Feb 16 11:40:53 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly for more than 30 seconds, exiting master
Which in case libvirt will be restarted vdsm needs to be restarted manually as well.
Version-Release number of selected component (if applicable):
vdsm-4.9-48.el6.x86_64
libvirt-0.8.7-5.el6.x86_64
device-mapper-multipath-0.4.9-32.el6.x86_64
qemu-kvm-0.12.1.2-2.144.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1.run vm
2.kill libvirt
3.
Actual results:
Expected results:
vdsm watchdog should keep trying to restart vdsm (maybe on longer wait intervals)
Additional info:
Comment 2RHEL Program Management
2011-02-16 12:18:06 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Ayal suggests to have vdsmd/respawn to sleep for 10 minutes instead of stopping to respawn.
We should make sure that `service vdsmd status` reflects this state of sleep between trials.
Verified - vdsm-4.9-59.el6 - vdsm/respawn command sleeps for the amount of time that is described above, under normal scenario (accidentaly killing libvirt - started it up after few minutes) the vdsmd service doesn't have to be started manually.
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 479087 [details] vdsm log Description of problem: In case libvirt crashes- vdsm watchdog will stop trying to restart after 30 seconds: Feb 16 11:40:20 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:24 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:29 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:34 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:39 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:43 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:48 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly, respawning slave Feb 16 11:40:53 gold-vdsc respawn: slave '/usr/share/vdsm//vdsm' died too quickly for more than 30 seconds, exiting master Which in case libvirt will be restarted vdsm needs to be restarted manually as well. Version-Release number of selected component (if applicable): vdsm-4.9-48.el6.x86_64 libvirt-0.8.7-5.el6.x86_64 device-mapper-multipath-0.4.9-32.el6.x86_64 qemu-kvm-0.12.1.2-2.144.el6.x86_64 How reproducible: always Steps to Reproduce: 1.run vm 2.kill libvirt 3. Actual results: Expected results: vdsm watchdog should keep trying to restart vdsm (maybe on longer wait intervals) Additional info: