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:
fenced creates its log file with permissions of 666.  It should create it with permissions of 644 or better, like the rest of the cluster-related logs.

The problem is at line 1042 in fence/fenced/main.c.

Version-Release number of selected component (if applicable):
cman-3.0.12.1-32.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. configure cluster
2. start cluster
3. ls -l /var/log/cluster/fenced.log
  
Actual results:
666

Expected results:
644

Additional info:

The problem is that the daemon is doing umask(0), causing the fopen() within liblogthread to use 666.  I'll remove umask(0), but that won't fix the 666 permission on existing files.  Any suggestions about whether I should also add a chmod("/var/log/cluster/fenced.log", 666) to fix the existing files?

typo, we'd change it to 644.

Created attachment 602152 [details]
patch

    Remove umask(0) which caused liblogthread's fopen to
    create fenced.log with mode 666.
    
    Check if existing fenced.log has mode 666 and if so,
    chmod to 644.

pushed to RHEL6 branch
http://git.fedorahosted.org/cgit/cluster.git/commit/?h=RHEL6&id=638deec0ccbf45862eee97294f09ba9d6b3f56d0

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-0287.html