[Pacemaker] corosync does not start
andreas graeper
agraeper at googlemail.com
Mon Jun 10 13:15:06 UTC 2013
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130610/8d739972/attachment-0003.html>
More information about the Pacemaker
mailing list