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.

Description of problem:

The permissions on pid and log files were not correct.

test: verify that file permissions match these:
service wdmd start
service sanlock start
ls -l /var/run/wdmd/
-rw-r--r--. 1 root root    5 Aug 16 16:52 wdmd.pid
srw-rw----. 1 root sanlock 0 Aug 16 16:52 wdmd.sock
ls -l /var/run/sanlock/
-rw-r--r--. 1 sanlock sanlock 5 Aug 16 16:52 sanlock.pid
srw-rw----. 1 sanlock sanlock 0 Aug 16 16:52 sanlock.sock
ls -l /var/log/sanlock.log
-rw-r--r--. 1 root root 2141429 Aug 16 16:52 /var/log/sanlock.log

commits
wdmd: use lockfile mode 644
sanlock: use lockfile mode 644
sanlock: remove umask 0

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

[root@purple-vds2 vdsm]# ls -l /var/run/sanlock/
total 4
-rw-r--r-- 1 sanlock sanlock 5 Nov 26 14:11 sanlock.pid
srw-rw---- 1 sanlock sanlock 0 Nov 26 14:11 sanlock.sock
[root@purple-vds2 vdsm]# ls -l /var/run/wdmd/
total 4
-rw-r--r-- 1 root root    5 Nov 26 14:11 wdmd.pid
srw-rw---- 1 root sanlock 0 Nov 26 14:11 wdmd.sock
[root@purple-vds2 vdsm]# ls -l /var/log/sanlock.log
-rw-r--r-- 1 sanlock sanlock 9973348 Nov 26 14:11 /var/log/sanlock.log
[root@purple-vds2 vdsm]# 


Fixed.

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-2012-1507.html