If I disable both (logd and mgmtd) the Problem is still existing.
Has nobody an idea?
Is Pacemaker or Corosync the problem?
Or is it a Debian problem?
Regards
Bastian
Am 18.08.2010 10:32, schrieb Bastian Schern:
Am 17.08.2010 11:28, schrieb Brett Delle Grazie:
Hi,
Are you using backports or the madkis repository?
> For lenny you should be using backports.
>
Both!
pacemaker-mgmt and pacemaker-mgmt-client is only available via madkis
repository.
I had a similar problem, remove the 'use_logd' and 'use_mgmtd' lines
from your
service entry for pacemaker. Try just removing the use_logd first.
It did not help.
I think the current version(s) of pacemaker no longer use logd or the
service
definition in corosync no longer supports it.
btw, my service definition for pacemaker is in a separate file in
/etc/corosync/services.d/
I removed the service section from the corosync.conf and created the
following:
# cat /etc/corosync/service.d/pcmk
service {
# Load the Pacemaker Cluster Resource Manager
name: pacemaker
ver: 0
}
But this is not fixing the problem. :-(
Do you have any other suggestions?
Thanks
Bastian
_______________________________________________
Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
