Description of problem:
Aug 24 06:58:17 marathon-03 corosync: [MAIN ] Completed service synchronization, ready to provide service.
Aug 24 06:58:20 marathon-03 fenced: fenced 126.96.36.199 started
Aug 24 06:58:20 marathon-03 dlm_controld: dlm_controld 188.8.131.52 started
Aug 24 06:58:21 marathon-03 dlm_controld: /sys/kernel/config/dlm/cluster/comms/1: mkdir failed: 17
Aug 24 06:58:21 marathon-03 dlm_controld: /sys/kernel/config/dlm/cluster/comms/2: mkdir failed: 17
Aug 24 06:58:21 marathon-03 dlm_controld: /sys/kernel/config/dlm/cluster/comms/3: mkdir failed: 17
Aug 24 06:58:21 marathon-03 dlm_controld: /sys/kernel/config/dlm/cluster/comms/4: mkdir failed: 17
Aug 24 06:58:21 marathon-03 dlm_controld: /sys/kernel/config/dlm/cluster/comms/5: mkdir failed: 17
Aug 24 06:58:22 marathon-03 gfs_controld: gfs_controld 184.108.40.206 started
These errors do not appear if only one ring is used.
Required setup is same as for bug 722469 (https://fedorahosted.org/cluster/wiki/MultiHome).
Selinux is in permissive mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. setup cluster with redundant ring
2. service cman start
errors as above
$ ll /sys/kernel/config/dlm/cluster/comms
drwxr-xr-x. 2 root root 0 Aug 24 06:58 1
drwxr-xr-x. 2 root root 0 Aug 24 06:58 2
drwxr-xr-x. 2 root root 0 Aug 24 06:58 3
drwxr-xr-x. 2 root root 0 Aug 24 06:58 4
drwxr-xr-x. 2 root root 0 Aug 24 06:58 5
We just need to silence those messages (17/EEXIST is not a problem).
Will push out the change if/when this bz is approved.
pushed change to remove the error messages to cluster.git RHEL6
use the steps above to test (setup rrp and service cman start)
Marking as verified, the messages no longer appear in cman-220.127.116.11-16.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: corosync redundant ring configuration detected by dlm_controld.
Consequence: dlm_controld would log harmless EEXIST errors
"mkdir failed: 17"
Fix: remove the error message.
Result: no more error message.
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.