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.
Cause:
The sanlock package is a new component that provides disk based leases, and uses the watchdog device to protect their recovery.
Consequence:
Previous versions of sos did not include support for collecting sanlock diagnostic data.
Fix:
A new module has been added to collect configuration and log files for this component.
Result:
Diagnostic information relating to the sanlock service is now captured in generated reports.
Created attachment 606226[details]
vdsm + spm logs
Description of problem:
on a host that is the SPM, no information is being written to spm-lock.log
Version-Release number of selected component (if applicable):
vdsm-4.9.6-29.0.el6_3.x86_64
How reproducible:
100%
Steps to Reproduce:
On a host that is SPM, nothing is being written to the log file
vdsm logs and spm-lock.log attached.
Comment 3Federico Simoncelli
2012-08-22 16:40:30 UTC
As far as I see in the logs the domains were V3 and therefore the logging took place in sanlock (/var/log/sanlock.log). What we may want to do is provide an sos plugin to fetch also the sanlock logs. Renaming the bug accordingly.
Thanks for the patch - looks good - I'll add this to the queue for RHEL6. You can also post sos patches to the sos-devel mailing list for review:
http://www.redhat.com/mailman/listinfo/sos-devel
They'll reach a wider audience of sos contributors there than bugzilla.
One thing to check is whether any of the files contain anything that we should elide for security reasons? I don't think so but I'm not very familiar with sanlock so it would be good to get that signed off by someone who knows the package well.
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/RHBA-2013-0474.html
Created attachment 606226 [details] vdsm + spm logs Description of problem: on a host that is the SPM, no information is being written to spm-lock.log Version-Release number of selected component (if applicable): vdsm-4.9.6-29.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: On a host that is SPM, nothing is being written to the log file vdsm logs and spm-lock.log attached.