Hello world,
according to [1] using the pacemaker plugin with corosync is
deprecated and will cease to be supported at some point in the future
(on RHEL!). Instead, the use of CMAN and running pacemaker as a
standalone service is recommended.
Now, unfortunately, the former (corosync with pcmk
* Dejan Muhamedagic deja...@fastmail.fm:
Please make a hb_report for this incident and open a bugzilla.
2439
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
FdI #176: NT-Consulter - italienische Ledertreter, Achselschweiß Erklärt
Probleme dadurch, daß man
Hi,
* Dejan Muhamedagic deja...@fastmail.fm:
On Wed, Jun 09, 2010 at 07:16:28AM +0200, Stefan Foerster wrote:
Unfortunately, I had some time constraints, so I completely forgot to
capture that hb_report. However, I still got all of the logs - if you
could tell me what files you need, I
Follow-up to my own posting:
* Stefan Foerster cite+pacema...@incertum.net:
I have a number of primitives and a master/slave resource which need
to be started in a given order. At first I was thinking about using a
group, but as things go with groups, seemingly independent resources
might
* Stefan Förster cite+pacema...@incertum.net:
* Dejan Muhamedagic deja...@fastmail.fm:
On Fri, Nov 27, 2009 at 01:05:41PM +0100, Stefan Förster wrote:
With Debian, apart from some minor glitches (path to controld.pcmk,
old udev, old kernel) everything went well, but as soon as I commit
Hello world,
out of curiosity, I tried to set up OCFS2 and a
Pacemaker/Corosync/OpenAIS cluster stack ohn Debian/lenny.
I copy/pasted the cluster configuration from Michael Schwartzkopff's
HOWTO (which works flawlessly on Fedora Core 11).
With Debian, apart from some minor glitches (path to
* Dejan Muhamedagic deja...@fastmail.fm:
On Fri, Nov 27, 2009 at 01:05:41PM +0100, Stefan Förster wrote:
With Debian, apart from some minor glitches (path to controld.pcmk,
old udev, old kernel) everything went well, but as soon as I commit
the configuration containing the O2CB resources, both
Hello world,
settings cluster-recheck-interval of five minutes, we often see
messages of the this kind in our logfiles:
crmd: [3856]: WARN: do_state_transition: Progressed to state
S_POLICY_ENGINE after C_TIMER_POPPED
Why is this logged as a warning?
Ciao
Stefan
--
Stefan Förster http
* Stefan Förster cite+pacema...@incertum.net:
crmd: [3856]: WARN: do_state_transition: Progressed to state
S_POLICY_ENGINE after C_TIMER_POPPED
Why is this logged as a warning?
Clarifying: Logged as a warning, and not as a merely informational
message
* Andrew Beekhof and...@beekhof.net:
2009/11/23 Stefan Förster cite+pacema...@incertum.net:
* Stefan Förster cite+pacema...@incertum.net:
crmd: [3856]: WARN: do_state_transition: Progressed to state
S_POLICY_ENGINE after C_TIMER_POPPED
Why is this logged as a warning?
Clarifying
10 matches
Mail list logo
