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.
Bug 960993 - [sanlock] Monitor and report the lockspace hosts liveness
Summary: [sanlock] Monitor and report the lockspace hosts liveness
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 883504
TreeView+ depends on / blocked
 
Reported: 2013-05-08 13:30 UTC by Federico Simoncelli
Modified: 2013-11-21 11:48 UTC (History)
2 users (show)

Fixed In Version: sanlock-2.8-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 11:48:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1632 0 normal SHIPPED_LIVE sanlock bug fix and enhancement update 2013-11-21 01:32:25 UTC

Description Federico Simoncelli 2013-05-08 13:30:24 UTC 
Description of problem:
Sanlock should provide a way to monitor and report the lockspace hosts liveness.

Additional info:
An initial analysis has been made and it looks like the new C API will be sanlock_get_hosts which will return a list of active hosts with their status, e.g. alive, failing (killing the pids but not fenced by the watchdog yet), dead.

The python bindings will expose the same functionality with a function named get_hosts (sanlock module).
Comment 2 David Teigland 2013-07-01 22:05:58 UTC 
Here is a sequence of commands to test the capability without the need for a separate test program.  It uses a shared vg "test" with a shared lv "test".


host1,2: service wdmd start
host1,2: service sanlock start

host1:
lvcreate -n test -L1G test
sanlock client init -s test:0:/dev/test/test:0

host1: sanlock client add_lockspace -s test:1:/dev/test/test:0
host2: sanlock client add_lockspace -s test:2:/dev/test/test:0

host1: sanlock gets -h 1
s test:1:/dev/test/test:0
h 1 gen 1 timestamp 1137100 LIVE
h 2 gen 1 timestamp 1136975 LIVE

(Note: exact timestamps will of course vary.)

host2: sanlock gets -h 1
s test:1:/dev/test/test:0
h 1 gen 1 timestamp 1137100 LIVE
h 2 gen 1 timestamp 1136975 LIVE

host2: killall -9 sanlock

Continue monitoring host2 from host1 by running sanlock gets.
After 80 seconds, host2 should appear in the FAIL state.
After 140 seconds, host2 should appear in the DEAD state.

host1: sanlock gets -h 1
s test:1:/dev/test/test:0 
h 1 gen 1 timestamp 1137573 LIVE
h 2 gen 1 timestamp 1137373 FAIL

host1: sanlock gets -h 1
s test:1:/dev/test/test:0 
h 1 gen 1 timestamp 1137634 LIVE
h 2 gen 1 timestamp 1137373 DEAD
Comment 5 Leonid Natapov 2013-08-29 07:55:19 UTC 
sanlock-2.8-1.el6.x86_64, tested according to comment #2.
Comment 7 errata-xmlrpc 2013-11-21 11:48:51 UTC 
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-1632.html
Note You need to log in before you can comment on or make changes to this bug.