Hi,everybody.
I tried to compile Heartbeat on RHEL 4.5.
But after installed Cluster glue, it seems everything is ok, but when I try
to compile heartbeat 3.0 stable src, it gives me a error about 'cannot find
lplumb'.
How can I pass it?
Thanks.
--
~~~
宠辱不惊,看庭前花开花落，去留无意,望天上云卷云舒。
__
Hi, all
I downloaded Pacemaker GUI today and am having problem to compile it on Redhat
Enterprise server v5.5 (X86_64). The message is:
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include
-I../../include -I../../include -I../../libltdl -I../../libltdl
-I../../linux-ha -
2010/5/7 Aleksey Zholdak :
> So, the problem is solved.
Excellent!
> P.S. Firewall also prevents the launch of resources. Someone can explain me
> how to run the resources with firewall?
>
IIRC, Whatever port number you listed in openais.conf, you need to
open that port and that port + 1 in the
; > The cluster was running fairly stable for the past couple of weeks.
> >
> > But then Yesterday without any user interaction and while idle the
> > active node (gwa) failed and was subsequently stonithed by the
> > passive one (gwb) due to a strange error (at least to me
Hi,
Dejan Muhamedagic wrote:
I've never seen this happen in the cluster. The argument list of
resource agents should consist of just the operation name. This
could be memory corruption. Can you please provide the hb_report
and open a bug report. Perhaps we can find some clues in the logs.
Tha
Hi, Andrew
After I wiped out the OS and reinstalled RHEL, it passed compilation. I guess
the KickStart installation caused the problem. This time I did ISO OS
installation and there was no problem. Wield.
Ryan
-Original Message-
From: Andrew Beekhof [mailto:and...@beekhof.net]
Sent: T
Hi,
On Fri, May 07, 2010 at 03:01:21PM +0200, JECH Ladislav wrote:
> Hello,
>
> I want to ask what about Pacemaker 1.2 compatibility with python version
> 3.*? Did anyone already test it?
I haven't. The only critical component using python is the crm
shell. You can try /usr/share/pacemaker/tests
cluster was running fairly stable for the past couple of weeks.
>
> But then Yesterday without any user interaction and while idle the
> active node (gwa) failed and was subsequently stonithed by the
> passive one (gwb) due to a strange error (at least to me) on allmost
> all resour
Hello,
I want to ask what about Pacemaker 1.2 compatibility with python version
3.*? Did anyone already test it?
Best regards,
Ladislav Jech
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemake
Hi,
On Fri, May 07, 2010 at 11:54:27AM +0200, JECH Ladislav wrote:
> Hi,
>
> I finally make Pacemaker up and running on CentOS 5.4. Currently using
> Heartbeat, but I want to switch to OpenAIS(Corosync). There were some
> problems related to Python and XML, strace crm still try to open some
> fil
while idle the
active node (gwa) failed and was subsequently stonithed by the passive
one (gwb) due to a strange error (at least to me) on allmost all
resource agents:
gwa:~# grep -i error /var/log/syslog-20100507
May 6 14:13:23 gwa lrmd: [27931]: ERROR: (raexecocf.c:execra:178) execl failed
Hi,
I finally make Pacemaker up and running on CentOS 5.4. Currently using
Heartbeat, but I want to switch to OpenAIS(Corosync). There were some
problems related to Python and XML, strace crm still try to open some
files which don't exist, I also did some symbolic links because of bad
paths. I wil
So, the problem is solved.
The solution is very interesting, because nowhere described.
If I follow the advice as to the article
http://www.linux-ha.org/wiki/SBD_Fencing and using multipath, I increase
timeouts when creating a partition for sbd...
sles2:~ # sbd -d /dev/mapper/SBD dump
Header
13 matches
Mail list logo
