[ClusterLabs] DLM not working on my GFS2/pacemaker cluster

[Jan Pokorný]

On 18/01/16 21:47 -0500, daniel at benoy.name wrote:
> Here's the exact same command run twice. First, on a very similarly
> configured cluster (which is currently running):
>   # cat /sys/kernel/config/dlm/cluster/comms/169446438/addrcat
>   cat: /sys/kernel/config/dlm/cluster/comms/169446438/addr: Permission
> denied
> (That's what I expect to see. It's a write-only file.)
> 
> And now on this messed up cluster:
>   # cat /sys/kernel/config/dlm/cluster/comms/168528918/addr
>   cat: /sys/kernel/config/dlm/cluster/comms/168528918/addr: Operation not
> permitted
> 
> Why 'operation not permitted'? dmesg isn't telling me anything at all, and I
> don't see any way to get the kernel to spit out some kind of explanation for
> why it's blocking me. Can anyone help? At least point me in a direction
> where I can get the system to give me some indication why it's behaving this
> way?

Was this on SELinux-enabled system, SELinux would be the suspect #1.
Can AppArmor (or any other enforcing mechanism) have a similar effect?

-- 
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160119/19885f34/attachment-0003.sig>