Bug 830848 - sanlock: initscript should create /var/lock/subsys/sanlock
sanlock: initscript should create /var/lock/subsys/sanlock
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sanlock (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: David Teigland
: Reopened, ZStream
Depends On:
Blocks: 841991 906027
  Show dependency treegraph
Reported: 2012-06-11 10:13 EDT by Daniel Berrange
Modified: 2016-04-26 09:34 EDT (History)
6 users (show)

See Also:
Fixed In Version: sanlock-2.5-1.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 03:52:44 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Berrange 2012-06-11 10:13:08 EDT
Description of problem:
The 'killall' initscript that is run when a machine shuts down, iterates over all files in /var/lock/subsys/, taking filenames as a service name. It invokes the stop action on each initscript which a subsys file.

Unfortunately, the sanlock initscript never creates/deletes any /var/lock/subsys/sanlock file, so it is not handled by the killall init script.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. /etc/init.d/sanlock start
2. ls /var/lock/subsys/sanlock
Actual results:
subsys file not present

Expected results:
subsys file should be present

Additional info:
Comment 2 David Teigland 2012-06-11 11:06:42 EDT
Hi Dan, this seems to work for me, could you check for any wdmd or sanlock errors in /var/log/messages?  This could also be related to all the uid issues we've been going through (sanlock is now back to being root, so that should lessen the problems.)

# modprobe softdog
# service wdmd start
# service sanlock start

# ps ax | grep -E 'sanlock|wdmd'
17771 ?        SLs    0:00 wdmd -G sanlock
17787 ?        SLsl   0:00 sanlock daemon -U sanlock -G sanlock

# ls -l /var/run/sanlock/
total 4
-rw-rw-rw-. 1 root    root    6 Jun 11 10:17 sanlock.pid
srw-rw----. 1 sanlock sanlock 0 Jun 11 10:17 sanlock.sock

# killall sanlock

# ps ax | grep -E 'sanlock|wdmd'
17771 ?        SLs    0:00 wdmd -G sanlock
Comment 3 Daniel Berrange 2012-06-11 11:21:05 EDT
You are mixing up the 'killall' command in /usr/bin which kills processes based on their argv[0] name, with the /etc/init.d/killall script which stops init services based on the existance of /var/lock/subsys/XXXXXX (where XXXX must be the initscript name ie 'sanlock').
Comment 4 David Teigland 2012-06-11 12:01:06 EDT
Thanks, I've pushed out a fix for both sanlock and wdmd:
Comment 5 David Teigland 2012-07-09 17:36:46 EDT

*** This bug has been marked as a duplicate of bug 838654 ***
Comment 6 David Teigland 2012-07-13 11:27:12 EDT
Comment 9 Leonid Natapov 2012-12-17 10:17:41 EST

[root@cinteg26 ~]# service sanlock start
Starting sanlock:                                          [  OK  ]
[root@cinteg26 ~]# ls -al /var/run/sanlock/
total 12
drwxrwxr-x.  2 sanlock sanlock 4096 Dec 17 17:17 .
drwxr-xr-x. 24 root    root    4096 Dec 17 13:23 ..
-rw-r--r--.  1 sanlock sanlock    6 Dec 17 17:17 sanlock.pid
srw-rw----.  1 sanlock sanlock    0 Dec 17 17:17 sanlock.sock
[root@cinteg26 ~]#
Comment 11 errata-xmlrpc 2013-02-21 03:52:44 EST
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.


Note You need to log in before you can comment on or make changes to this bug.