This worked. Let me know if there is a better way. From crm.h:
#ifdef ALAN_JONES_WANTS_HIS_LOG_MESSAGES
#define do_crm_log_unlikely(level, fmt, args...) do { \
if(__likely(crm_log_level < (level))) { \
continue;
Hi,
I would like to set debugging levels higher than zero with
pacemaker/corosync.
[r...@fc12-a heartbeat]# ./crmd version
CRM Version: 1.0.5 (ee19d8e83c2a5d45988f1cee36d334a631d84fc7)
[r...@fc12-a heartbeat]# corosync -v
Corosync Cluster Engine, version '1.1.2' SVN revision '2539'
Copyright (c) 2
On Thu, Apr 01, 2010 at 08:27:02AM -0600, Alan Robertson wrote:
> Lars Ellenberg wrote:
> >On Thu, Apr 01, 2010 at 12:12:47AM -0600, Alan Robertson wrote:
> >>OK
> >>
> >>Since there was no ssh-as-root between the cluster nodes, I didn't
> >>send all the logs along from every node in the cluste
Florian Haas wrote:
On 2010-04-01 16:27, Alan Robertson wrote:
None of them verified. All the nodes in the cluster failed the test at
the same time - and now I have no official CIBs on disk - on any cluster
nodes... I sent Andrew all the CIBs, and all the core files, and
basically everything
On 2010-04-01 16:27, Alan Robertson wrote:
> None of them verified. All the nodes in the cluster failed the test at
> the same time - and now I have no official CIBs on disk - on any cluster
> nodes... I sent Andrew all the CIBs, and all the core files, and
> basically everything under /var/lib/
Lars Ellenberg wrote:
On Thu, Apr 01, 2010 at 12:12:47AM -0600, Alan Robertson wrote:
OK
Since there was no ssh-as-root between the cluster nodes, I didn't
send all the logs along from every node in the cluster - and it
didn't occur to me to look at all of them.
However, the problem has go
On Thu, Apr 01, 2010 at 12:12:47AM -0600, Alan Robertson wrote:
> OK
>
> Since there was no ssh-as-root between the cluster nodes, I didn't
> send all the logs along from every node in the cluster - and it
> didn't occur to me to look at all of them.
>
> However, the problem has gotten curios
Hi Gerry,
> Stop all resources running on the node going to be shut down.
> That's what you want in the end, isn't it?
That should also work: set the second node to standby and do the reboot on
the primary - when primary is up again you'll set the secondary back
online.
Best,
Martin
"Gerry K
