[Pacemaker] corosync does not start

[Andrew Beekhof]

On 11/06/2013, at 1:32 AM, andreas graeper <agraeper at googlemail.com> wrote:

> hi, 
> i found that uid.gid is hacluster.haclient but /var/log/cluster was owned by root.root.
> corosync refused to start, cause of missing write permission to log file ! 
> 
> another question:
> i read in logs, that pacemaker plugin is not supported any longer ?!

Only if you're using RHEL6

> 
> i still use 
> service {
>   name:pacemaker
>   ver:0
>  }
> and it seems to work. 
> in what situation i  have to use ver:1 

"ver:1" is still the plugin

> and if i would use cman, what was its role in the middle of corosync, pacemaker ?

http://clusterlabs.org/quickstart.html

"
For example, on RHEL6 the supported stack is based on CMAN which has APIs Pacemaker can
use to obtain the membership and quroum information it needs.
"

> does cman replaces corosync ?

No. CMAN is just a different plugin for corosync.

> what is cman as corosync-plugin ?  
> 
> thanks in advance
> andreas
> 
> 2013/6/10 emmanuel segura <emi2fast at gmail.com>
> Hello Andreas
> 
> What do you have in /etc/security/limits.conf ?
> 
> Thanks
> 
> 
> 2013/6/10 andreas graeper <agraeper at googlemail.com>
> hi,
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not set SCHED_RR at priority 99: Operation not permitted (1)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Could not lock memory of service to avoid page faults: Cannot allocate memory (12)
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine ('1.4.1'): started and ready to provide service.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync built-in features: nss dbus rdma snmp
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Successfully read main configuration file '/etc/corosync/corosync.conf'.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Executive couldn't create lock file.
> Jun 10 15:09:06 n1 corosync[2785]:   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1794.
> 
> sestatus : disabled
> corosync-blackbox : 
>  Failed to initialize the objdb API. Error 6
>  Failed to initialize the objdb API. Error 6
>  failed to open /var/lib/corosync/fdata: No such file or directory
> 
> please help
> andreas
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 
> 
> 
> 
> -- 
> esta es mi vida e me la vivo hasta que dios quiera
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org