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.
DescriptionJaroslav Kortus
2015-03-26 13:57:04 UTC
Description of problem:
if service cman start fails, it leaves behind file in the /tmp directory.
[root@virt-147 ~]# service cman start
Starting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... Unable to update relaxng schema: /tmp/tmp.OvriT1TRhw/cluster.rng:5085: parser error : attributes construct error
uld be unique to a node and have to be written in /etc/multipath.conf. For the "
^
/tmp/tmp.OvriT1TRhw/cluster.rng:5085: parser error : Couldn't find end of Start Tag attribute line 5085
uld be unique to a node and have to be written in /etc/multipath.conf. For the "
^
generated schema does not pass xmllint validation
corosync died: Could not read cluster configuration Check cluster logs for details
[FAILED]
Stopping cluster:
Leaving fence domain... [ OK ]
Stopping gfs_controld... [ OK ]
Stopping dlm_controld... [ OK ]
Stopping fenced... [ OK ]
Stopping cman... [ OK ]
Unloading kernel modules... [ OK ]
Unmounting configfs... [ OK ]
[root@virt-147 ~]# ll /tmp/tmp*
-rw-------. 1 root root 1509 Mar 26 14:52 /tmp/tmp.bJhBV0gmlr
The error messages are related to bug https://bugzilla.redhat.com/show_bug.cgi?id=1206185, it's possible these two are connected.
Version-Release number of selected component (if applicable):
cman-3.0.12.1-73.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. add invalid content to cluster.conf (for example:
<cman><multicast addr="999.192.100.43"/></cman>
)
2. service cman start
3. see file being left in /tmp containing cluster configuration
Actual results:
extra file left in /tmp
Expected results:
no temporary files present when the scripts stop
Additional info:
Comment 6Jan Pokorný [poki]
2015-04-10 10:49:31 UTC
Haven't read all the comments, but suggest NOTABUG: for keeping /tmp
clean, one should use tmpwatch utility (seems to be installed and enabled
by default). There's a lot more leave-behind producers using /tmp
and never looking back in case of failure (or even in general).
Furthermore, permissions for the "leaked" file seems to be OK.
Comment 7Jan Pokorný [poki]
2015-04-10 11:24:32 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.
https://rhn.redhat.com/errata/RHBA-2016-0729.html
Description of problem: if service cman start fails, it leaves behind file in the /tmp directory. [root@virt-147 ~]# service cman start Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... Unable to update relaxng schema: /tmp/tmp.OvriT1TRhw/cluster.rng:5085: parser error : attributes construct error uld be unique to a node and have to be written in /etc/multipath.conf. For the " ^ /tmp/tmp.OvriT1TRhw/cluster.rng:5085: parser error : Couldn't find end of Start Tag attribute line 5085 uld be unique to a node and have to be written in /etc/multipath.conf. For the " ^ generated schema does not pass xmllint validation corosync died: Could not read cluster configuration Check cluster logs for details [FAILED] Stopping cluster: Leaving fence domain... [ OK ] Stopping gfs_controld... [ OK ] Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] [root@virt-147 ~]# ll /tmp/tmp* -rw-------. 1 root root 1509 Mar 26 14:52 /tmp/tmp.bJhBV0gmlr The error messages are related to bug https://bugzilla.redhat.com/show_bug.cgi?id=1206185, it's possible these two are connected. Version-Release number of selected component (if applicable): cman-3.0.12.1-73.el6.x86_64 How reproducible: always Steps to Reproduce: 1. add invalid content to cluster.conf (for example: <cman><multicast addr="999.192.100.43"/></cman> ) 2. service cman start 3. see file being left in /tmp containing cluster configuration Actual results: extra file left in /tmp Expected results: no temporary files present when the scripts stop Additional info: