On 11/06/2013, at 1:32 AM, andreas graeper 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 no
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 ?!
i still use
service {
name:pacemaker
ve
Hello Andreas
What do you have in /etc/security/limits.conf ?
Thanks
2013/6/10 andreas graeper
> 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
>
hi,
service corosync start as root
2013/6/10 emmanuel segura
> Hello Andreas
>
> Ho do you start the cluster ?
>
> Thanks
>
>
> 2013/6/10 andreas graeper
>
>> hi,
>> Jun 10 15:09:06 n1 corosync[2785]: [MAIN ] Could not set SCHED_RR at
>> priority 99: Operation not permitted (1)
>> Jun
Hello Andreas
Ho do you start the cluster ?
Thanks
2013/6/10 andreas graeper
> 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 p
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 ] Corosyn
