[Pacemaker] ccm crash: /var/run/heartbeat/ccm/ccm Permission denied

Andrew Beekhof beekhof at gmail.com
Mon Jul 28 10:29:38 UTC 2008


On Jul 28, 2008, at 12:24 PM, Rainer Traut wrote:

> Hi,
>
> sys: Centos 5 x86_64, 2 nodes
>
> # rpm -qa|grep heartbeat
> pacemaker-heartbeat-0.6.5-8.2
> heartbeat-ldirectord-2.1.3-23.1
> heartbeat-resources-2.1.3-23.1
> heartbeat-common-2.1.3-23.1
> heartbeat-2.1.3-23.1
>
> One cluster member constanly reboots with these logs:
>
> Jul 28 12:11:47 n02asp7 ccm: [8768]: ERROR: socket_wait_conn_new:  
> unlink failure(/var/run/heartbeat/ccm/ccm): Permission denied
> Jul 28 12:11:47 n02asp7 ccm: [8768]: ERROR: socket_wait_conn_new:  
> trying to create in /var/run/heartbeat/ccm/ccm bind:: Permission  
> denied
> Jul 28 12:11:47 n02asp7 ccm: [8768]: ERROR: Can't create wait  
> channel: Resource temporarily unavailable
> Jul 28 12:11:47 n02asp7 heartbeat: [8756]: WARN: Managed /usr/lib64/ 
> heartbeat/ccm process 8768 exited with return code 1.
> Jul 28 12:11:47 n02asp7 stonithd: [8771]: info: Signing in with  
> heartbeat.
> Jul 28 12:11:47 n02asp7 heartbeat: [8756]: EMERG: Rebooting system.  
> Reason: /usr/lib64/heartbeat/ccm
>
> and:
> # ls -la /var/run/heartbeat/ccm/ccm
> srwxrwxrwx 1 hacluster haclient 0 12. Jul 14:04 /var/run/heartbeat/ 
> ccm/ccm

what about the directories it in?
what user is ccm running as?

>
>
> This cluster has been running w/o problems for some months now...
> I do not dare to touch the other cluster member atm.
>
> Rainer
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker





More information about the Pacemaker mailing list