Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-09-22 Thread Andrew Beekhof
On Tue, Sep 21, 2010 at 4:10 PM, Angelo Höngens a.hong...@netmatch.nl wrote:
 On 25-8-2010 8:36, Andrew Beekhof wrote:
 I guess whoever packaged the rpm's can answer why the file is missing,
 but was that someone from the clusterlabs team or someone from the
 linux-ha team? :)

 Basically because I left out the libnet dependancy.
 The status of libnet as a viable project has been uncertain lately.


 Andrew,

 Because we have some ipv6 nodes I want to try out pacemaker on again,
 I'd really like to build an rpm of the resource agents package with ipv6
 support in. If you could tell a newbie like me how to do it, I'd be
 really grateful, and I think a lot of people will be happy as well. We
 run CentOS/RHEL5 everywhere.

 I've never built an RPM before, but it doesn't look that hard (until I
 saw the errors).

 I've installed all the dependencies (yum install autoconf automake gcc
 libnet-devel libtool libxml2-devel bzip2-devel glib2-devel libxslt-devel
 e2fsprogs-devel docbook-style-xsl rpm-build), and I want to make sure I
 can compile an RPM first before changing anything in the code.

 But even when doing that, I get errors:

 
 [ang...@test1 redhat]$ sudo rpm -i
 http://clusterlabs.org/rpm/epel-5/src/resource-agents-1.0.3-2.el5.src.rpm
 [ang...@test1 redhat]$ cd /usr/src/redhat/
 [ang...@test1 redhat]$ rpmbuild -bb SPECS/resource-agents.spec
 [..cut..]
 Provides: config(ldirectord) = 1.0.3-2 heartbeat-ldirectord
 Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1
 rpmlib(PayloadFilesHavePrefix) = 4.0-1
 Requires: /bin/sh /usr/bin/perl config(ldirectord) = 1.0.3-2 ipvsadm
 perl(Digest::MD5) perl(Getopt::Long) perl(IO::Select) perl(IO::Socket)
 perl(LWP::Debug) perl(LWP::UserAgent) perl(Mail::Send) perl(Net::Ping)
 perl(Net::SMTP) perl(POSIX) perl(Pod::Usage) perl(Socket) perl(Socket6)
 perl(Sys::Hostname) perl(Sys::Syslog) perl(strict) perl(vars)
 perl-MailTools perl-Net-SSLeay perl-libwww-perl
 Conflicts: heartbeat-ldirectord
 Obsoletes: heartbeat-ldirectord
 Checking for unpackaged file(s): /usr/lib/rpm/check-files
 /var/tmp/resource-agents-1.0.3-build

 RPM build errors:
    File not found: /var/tmp/resource-agents-1.0.3-build/usr/sbin/sfex_init
    File not found:
 /var/tmp/resource-agents-1.0.3-build/usr/lib64/heartbeat/sfex_daemon
 [ang...@test1 redhat]$
 

 Can you please help me in my quest to the desired end result? (which is
 the knowledge to build an ipv6-enabled version of the resource-agents so
 I can install it on my nodes, and I can rebuild it after each version
 upgrade of the source package).

You're close :-)
Try installing the -devel package for cluster-glue and trying again.



 It would be great if it would be part of the basic packages as well, but
 alas this does not seem to be the case right now.

 I can provide ssh root access to a clean vm (centos 5.5, x64) if needed.


 --


 With kind regards,


 Angelo Höngens
 systems administrator

 MCSE on Windows 2003
 MCSE on Windows 2000
 MS Small Business Specialist
 --
 NetMatch
 tourism internet software solutions

 Ringbaan Oost 2b
 5013 CA Tilburg
 +31 (0)13 5811088
 +31 (0)13 5821239

 a.hong...@netmatch.nl
 www.netmatch.nl
 --



 ___
 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


___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-09-22 Thread Angelo Höngens
On 22-9-2010 9:58, Andrew Beekhof wrote:
 Can you please help me in my quest to the desired end result? (which is
 the knowledge to build an ipv6-enabled version of the resource-agents so
 I can install it on my nodes, and I can rebuild it after each version
 upgrade of the source package).
 
 You're close :-)
 Try installing the -devel package for cluster-glue and trying again.

Thanks, that works like a charm, I didn't even have to change anything!

For people googling, here's my version of the resource-agents with the
IPv6addr module:
http://files.hongens.nl/RPM/resource-agents-1.0.3-2.x86_64.rpm



-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
--
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg
+31 (0)13 5811088
+31 (0)13 5821239

a.hong...@netmatch.nl
www.netmatch.nl
--



___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-09-21 Thread Angelo Höngens
On 25-8-2010 8:36, Andrew Beekhof wrote:
 I guess whoever packaged the rpm's can answer why the file is missing,
 but was that someone from the clusterlabs team or someone from the
 linux-ha team? :)
 
 Basically because I left out the libnet dependancy.
 The status of libnet as a viable project has been uncertain lately.


Andrew,

Because we have some ipv6 nodes I want to try out pacemaker on again,
I'd really like to build an rpm of the resource agents package with ipv6
support in. If you could tell a newbie like me how to do it, I'd be
really grateful, and I think a lot of people will be happy as well. We
run CentOS/RHEL5 everywhere.

I've never built an RPM before, but it doesn't look that hard (until I
saw the errors).

I've installed all the dependencies (yum install autoconf automake gcc
libnet-devel libtool libxml2-devel bzip2-devel glib2-devel libxslt-devel
e2fsprogs-devel docbook-style-xsl rpm-build), and I want to make sure I
can compile an RPM first before changing anything in the code.

But even when doing that, I get errors:


[ang...@test1 redhat]$ sudo rpm -i
http://clusterlabs.org/rpm/epel-5/src/resource-agents-1.0.3-2.el5.src.rpm
[ang...@test1 redhat]$ cd /usr/src/redhat/
[ang...@test1 redhat]$ rpmbuild -bb SPECS/resource-agents.spec
[..cut..]
Provides: config(ldirectord) = 1.0.3-2 heartbeat-ldirectord
Requires(rpmlib): rpmlib(CompressedFileNames) = 3.0.4-1
rpmlib(PayloadFilesHavePrefix) = 4.0-1
Requires: /bin/sh /usr/bin/perl config(ldirectord) = 1.0.3-2 ipvsadm
perl(Digest::MD5) perl(Getopt::Long) perl(IO::Select) perl(IO::Socket)
perl(LWP::Debug) perl(LWP::UserAgent) perl(Mail::Send) perl(Net::Ping)
perl(Net::SMTP) perl(POSIX) perl(Pod::Usage) perl(Socket) perl(Socket6)
perl(Sys::Hostname) perl(Sys::Syslog) perl(strict) perl(vars)
perl-MailTools perl-Net-SSLeay perl-libwww-perl
Conflicts: heartbeat-ldirectord
Obsoletes: heartbeat-ldirectord
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/var/tmp/resource-agents-1.0.3-build

RPM build errors:
File not found: /var/tmp/resource-agents-1.0.3-build/usr/sbin/sfex_init
File not found:
/var/tmp/resource-agents-1.0.3-build/usr/lib64/heartbeat/sfex_daemon
[ang...@test1 redhat]$


Can you please help me in my quest to the desired end result? (which is
the knowledge to build an ipv6-enabled version of the resource-agents so
I can install it on my nodes, and I can rebuild it after each version
upgrade of the source package).

It would be great if it would be part of the basic packages as well, but
alas this does not seem to be the case right now.

I can provide ssh root access to a clean vm (centos 5.5, x64) if needed.


-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
--
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg
+31 (0)13 5811088
+31 (0)13 5821239

a.hong...@netmatch.nl
www.netmatch.nl
--



___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-26 Thread Andrew Beekhof
On Wed, Aug 25, 2010 at 1:14 PM, Angelo Höngens a.hong...@netmatch.nl wrote:
 On 25-8-2010 8:36, Andrew Beekhof wrote:
 Basically because I left out the libnet dependancy.
 The status of libnet as a viable project has been uncertain lately.

 Perhaps there could be a warning in the FAQ about this? The fact that
 the binary package misses a very important (to some) module is quite a
 nuisance, and it took me a day to figure it out. :-(

 After finding it out, it took me another 4 hours to compile the packages
 from source, mostly because of my lack of understanding of compiling
 stuff and all the problems involved. Not exactly the pleasant experience
 I was hoping for, but at last I have the IPv6addr module.

The issue will be moot as soon as the next agents package is released
(which has a rewritten version that doesnt depend on libnet).



 Note to self and other newbies googling:

 These are the required packages that I installed on a clean CentOS5.5
 box in order to compile everything:

 autoconf
 automake
 gcc
 libnet-devel
 libtool
 libxml2-devel
 bzip2-devel
 glib2-devel
 libxslt-devel
 e2fsprogs-devel (not checked for by the configure script!)

 libnet-devel is available in the epel repo, to add it, run:

 sudo rpm -Uvh
 http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm

 The cluster glue package might not compile because of a warning in
 lib/stonith/main.c. Strangely enough i saw this only on one machine,
 after I reinstalled it, this was no longer present. Add
 --enable-fatal-warnings=no to the configure statement to go along anyway
 if this occurs.

 And yes, the compiling of the documentation will take very very long if
 you don't have a http proxy in place, because the process will make
 hundreds, if not thousands of http requests to
 http://docbook.sourceforge.net. In my case, building the resource agents
 package took 1.5 hours.

 --


 With kind regards,


 Angelo Höngens
 systems administrator

 MCSE on Windows 2003
 MCSE on Windows 2000
 MS Small Business Specialist
 --
 NetMatch
 tourism internet software solutions

 Ringbaan Oost 2b
 5013 CA Tilburg
 +31 (0)13 5811088
 +31 (0)13 5821239

 a.hong...@netmatch.nl
 www.netmatch.nl
 --



 ___
 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


___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-25 Thread Andrew Beekhof
On Wed, Aug 25, 2010 at 7:50 AM, Angelo Höngens a.hong...@netmatch.nl wrote:
 On 24-8-2010 17:55, Dejan Muhamedagic wrote:

 BTW, any reason not to go with the prebuilt rpms from
 clusterlabs.org?

 I am, through their repository.

 But when I download the prebuilt file from the clusterlabs website
 (http://www.clusterlabs.org/rpm/epel-5/x86_64/resource-agents-1.0.3-2.6.el5.x86_64.rpm),
 the /usr/lib/ocf/resource.d/heartbeat/IPv6addr is missing as well:

 [r...@lb2 ~]# rpm -qpl resource-agents-1.0.3-2.6.el5.x86_64.rpm  | grep
 -i ip
 /usr/lib/ocf/resource.d/heartbeat/IPaddr
 /usr/lib/ocf/resource.d/heartbeat/IPaddr2
 /usr/lib/ocf/resource.d/heartbeat/IPsrcaddr
 /usr/lib/ocf/resource.d/heartbeat/VIPArip
 /usr/share/man/man7/ocf_heartbeat_IPaddr.7.gz
 /usr/share/man/man7/ocf_heartbeat_IPaddr2.7.gz
 /usr/share/man/man7/ocf_heartbeat_IPsrcaddr.7.gz
 /usr/share/man/man7/ocf_heartbeat_VIPArip.7.gz
 /usr/share/resource-agents/ocft/configs/IPaddr2
 /usr/share/resource-agents/ocft/configs/IPsrcaddr

 I guess whoever packaged the rpm's can answer why the file is missing,
 but was that someone from the clusterlabs team or someone from the
 linux-ha team? :)

Basically because I left out the libnet dependancy.
The status of libnet as a viable project has been uncertain lately.

___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-25 Thread Angelo Höngens
On 25-8-2010 8:36, Andrew Beekhof wrote:
 Basically because I left out the libnet dependancy.
 The status of libnet as a viable project has been uncertain lately.

Perhaps there could be a warning in the FAQ about this? The fact that
the binary package misses a very important (to some) module is quite a
nuisance, and it took me a day to figure it out. :-(

After finding it out, it took me another 4 hours to compile the packages
from source, mostly because of my lack of understanding of compiling
stuff and all the problems involved. Not exactly the pleasant experience
I was hoping for, but at last I have the IPv6addr module.


Note to self and other newbies googling:

These are the required packages that I installed on a clean CentOS5.5
box in order to compile everything:

autoconf
automake
gcc
libnet-devel
libtool
libxml2-devel
bzip2-devel
glib2-devel
libxslt-devel
e2fsprogs-devel (not checked for by the configure script!)

libnet-devel is available in the epel repo, to add it, run:

sudo rpm -Uvh
http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm

The cluster glue package might not compile because of a warning in
lib/stonith/main.c. Strangely enough i saw this only on one machine,
after I reinstalled it, this was no longer present. Add
--enable-fatal-warnings=no to the configure statement to go along anyway
if this occurs.

And yes, the compiling of the documentation will take very very long if
you don't have a http proxy in place, because the process will make
hundreds, if not thousands of http requests to
http://docbook.sourceforge.net. In my case, building the resource agents
package took 1.5 hours.

-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
--
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg
+31 (0)13 5811088
+31 (0)13 5821239

a.hong...@netmatch.nl
www.netmatch.nl
--



___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-24 Thread Angelo Höngens
A reply to myself..

It looks like the underlying script gives an error:

[r...@lb1 heartbeat]# /etc/ha.d/resource.d/IPv6addr 2001::1 status
IPv6addr[17013]: ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not an 
executable file
ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not an executable file

And I now see the underlying executeable 
/usr/lib/ocf/resource.d/heartbeat/IPv6addr does not exist! It seems to be 
missing from the RPM so it seems. 
 
I downloaded the heartbeat agents source (agents-1.0.3.tar.bz2), and if I run 
'make' it does not seem to compile the IPv6addr program. There's a IPv6addr.c 
though, but no idea how that works.. 

Any idea on how to proceed?

Am I posting to the correct list, or should I post to some heartbeat mailing 
list?

-- 

 
With kind regards,
 
 
Angelo Höngens
 
Systems Administrator
 
--
NetMatch
tourism internet software solutions
 
Ringbaan Oost 2b
5013 CA Tilburg
T: +31 (0)13 5811088
F: +31 (0)13 5821239
 
mailto:a.hong...@netmatch.nl
http://www.netmatch.nl
--


 -Original Message-
 From: Angelo Höngens
 Sent: dinsdag 24 augustus 2010 14:55
 To: 'pacemaker@oss.clusterlabs.org'
 Subject: error: ocf:heartbeat:IPv6addr: could not parse meta-data
 
 Hey guys and girls,
 
 I'm new to pacemaker/heartbeat/corosync/openais. I've been using
 FreeBSD+Carp for high availability of simple web/proxy servers for a
 few years now, but we want to standardize all our *nix machines to
 CentOS now. In my quest for an easy-to-use and robust HA suite, I am
 now evaluating pacemaker. From what I've seen so far, pacemaker looks
 very nice.
 
 I set up a test lab with two ESX vm's with CentOS 5.5, and followed the
 instructions here:
 http://www.clusterlabs.org/wiki/Install#Installing_on_EPEL_Compatible_D
 istributions:_RHEL.2C_CentOS.2C_etc
 Because of using yum as a package manager, I can easily query and
 upgrade packages.
 
 I can get everything I want to work fine for ipv4 addresses. However, I
 have a problem with ipv6 addresses (we use ipv6 extensively, and it is
 a hard requirement). It looks like the IPv6addr resource agent is
 broken.
 
 I can get information on other resource agents fine:
 
 [r...@lb1 ~]# crm configure ra info IPaddr2
 Manages virtual IPv4 addresses (Linux specific version)
 (ocf:heartbeat:IPaddr2)
 
 This Linux-specific resource manages IP alias IP addresses.
 It can add an IP alias, or remove one.
 ..
 
 However, if I try the same for the IPv6addr ra:
 
 [r...@lb1 ~]# crm configure ra info IPv6addr
 lrmadmin[29030]: 2010/08/24_14:51:14 ERROR:
 lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a reply
 message of rmetadata with function get_ret_from_msg.
 ERROR: ocf:heartbeat:IPv6addr: could not parse meta-data:
 
 
 Is this a known issue? Does anyone else use this ra?
 
 --
 
 
 With kind regards,
 
 
 Angelo Höngens
 
 Systems Administrator
 
 --
 NetMatch
 tourism internet software solutions
 
 Ringbaan Oost 2b
 5013 CA Tilburg
 T: +31 (0)13 5811088
 F: +31 (0)13 5821239
 
 mailto:a.hong...@netmatch.nl
 http://www.netmatch.nl
 --
 


___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-24 Thread Dejan Muhamedagic
Hi,

On Tue, Aug 24, 2010 at 02:55:09PM +, Angelo Höngens wrote:
 A reply to myself..
 
 It looks like the underlying script gives an error:
 
 [r...@lb1 heartbeat]# /etc/ha.d/resource.d/IPv6addr 2001::1 status
 IPv6addr[17013]: ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not an 
 executable file
 ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not an executable file
 
 And I now see the underlying executeable 
 /usr/lib/ocf/resource.d/heartbeat/IPv6addr does not exist! It seems to be 
 missing from the RPM so it seems. 
  
 I downloaded the heartbeat agents source (agents-1.0.3.tar.bz2), and if I run 
 'make' it does not seem to compile the IPv6addr program. There's a IPv6addr.c 
 though, but no idea how that works.. 
 
 Any idea on how to proceed?

The most probable issue is that you're missing libnet. Now, that
dependency has recently been removed, so if you're brave enough
you can try the tip of the repository (i.e. unreleased software).
Or install libnet.

 Am I posting to the correct list, or should I post to some
 heartbeat mailing list?

The right list is linux-ha, but we got used to listening to
multiple lists.

Thanks,

Dejan

 
 -- 
 
  
 With kind regards,
  
  
 Angelo Höngens
  
 Systems Administrator
  
 --
 NetMatch
 tourism internet software solutions
  
 Ringbaan Oost 2b
 5013 CA Tilburg
 T: +31 (0)13 5811088
 F: +31 (0)13 5821239
  
 mailto:a.hong...@netmatch.nl
 http://www.netmatch.nl
 --
 
 
  -Original Message-
  From: Angelo Höngens
  Sent: dinsdag 24 augustus 2010 14:55
  To: 'pacemaker@oss.clusterlabs.org'
  Subject: error: ocf:heartbeat:IPv6addr: could not parse meta-data
  
  Hey guys and girls,
  
  I'm new to pacemaker/heartbeat/corosync/openais. I've been using
  FreeBSD+Carp for high availability of simple web/proxy servers for a
  few years now, but we want to standardize all our *nix machines to
  CentOS now. In my quest for an easy-to-use and robust HA suite, I am
  now evaluating pacemaker. From what I've seen so far, pacemaker looks
  very nice.
  
  I set up a test lab with two ESX vm's with CentOS 5.5, and followed the
  instructions here:
  http://www.clusterlabs.org/wiki/Install#Installing_on_EPEL_Compatible_D
  istributions:_RHEL.2C_CentOS.2C_etc
  Because of using yum as a package manager, I can easily query and
  upgrade packages.
  
  I can get everything I want to work fine for ipv4 addresses. However, I
  have a problem with ipv6 addresses (we use ipv6 extensively, and it is
  a hard requirement). It looks like the IPv6addr resource agent is
  broken.
  
  I can get information on other resource agents fine:
  
  [r...@lb1 ~]# crm configure ra info IPaddr2
  Manages virtual IPv4 addresses (Linux specific version)
  (ocf:heartbeat:IPaddr2)
  
  This Linux-specific resource manages IP alias IP addresses.
  It can add an IP alias, or remove one.
  ..
  
  However, if I try the same for the IPv6addr ra:
  
  [r...@lb1 ~]# crm configure ra info IPv6addr
  lrmadmin[29030]: 2010/08/24_14:51:14 ERROR:
  lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a reply
  message of rmetadata with function get_ret_from_msg.
  ERROR: ocf:heartbeat:IPv6addr: could not parse meta-data:
  
  
  Is this a known issue? Does anyone else use this ra?
  
  --
  
  
  With kind regards,
  
  
  Angelo Höngens
  
  Systems Administrator
  
  --
  NetMatch
  tourism internet software solutions
  
  Ringbaan Oost 2b
  5013 CA Tilburg
  T: +31 (0)13 5811088
  F: +31 (0)13 5821239
  
  mailto:a.hong...@netmatch.nl
  http://www.netmatch.nl
  --
  
 
 
 ___
 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

___
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


Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-24 Thread Dejan Muhamedagic
On Tue, Aug 24, 2010 at 05:52:28PM +0200, Dejan Muhamedagic wrote:
HI,

 Hi,
 
 On Tue, Aug 24, 2010 at 02:55:09PM +, Angelo Höngens wrote:
  A reply to myself..
  
  It looks like the underlying script gives an error:
  
  [r...@lb1 heartbeat]# /etc/ha.d/resource.d/IPv6addr 2001::1 status
  IPv6addr[17013]: ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not 
  an executable file
  ERROR: /usr/lib/ocf/resource.d//heartbeat/IPv6addr is not an executable file
  
  And I now see the underlying executeable 
  /usr/lib/ocf/resource.d/heartbeat/IPv6addr does not exist! It seems to be 
  missing from the RPM so it seems. 
   
  I downloaded the heartbeat agents source (agents-1.0.3.tar.bz2), and if I 
  run 'make' it does not seem to compile the IPv6addr program. There's a 
  IPv6addr.c though, but no idea how that works.. 
  
  Any idea on how to proceed?
 
 The most probable issue is that you're missing libnet. Now, that
 dependency has recently been removed, so if you're brave enough
 you can try the tip of the repository (i.e. unreleased software).
 Or install libnet.

BTW, any reason not to go with the prebuilt rpms from
clusterlabs.org?

Thanks,

Dejan

  Am I posting to the correct list, or should I post to some
  heartbeat mailing list?
 
 The right list is linux-ha, but we got used to listening to
 multiple lists.
 
 Thanks,
 
 Dejan
 
  
  -- 
  
   
  With kind regards,
   
   
  Angelo Höngens
   
  Systems Administrator
   
  --
  NetMatch
  tourism internet software solutions
   
  Ringbaan Oost 2b
  5013 CA Tilburg
  T: +31 (0)13 5811088
  F: +31 (0)13 5821239
   
  mailto:a.hong...@netmatch.nl
  http://www.netmatch.nl
  --
  
  
   -Original Message-
   From: Angelo Höngens
   Sent: dinsdag 24 augustus 2010 14:55
   To: 'pacemaker@oss.clusterlabs.org'
   Subject: error: ocf:heartbeat:IPv6addr: could not parse meta-data
   
   Hey guys and girls,
   
   I'm new to pacemaker/heartbeat/corosync/openais. I've been using
   FreeBSD+Carp for high availability of simple web/proxy servers for a
   few years now, but we want to standardize all our *nix machines to
   CentOS now. In my quest for an easy-to-use and robust HA suite, I am
   now evaluating pacemaker. From what I've seen so far, pacemaker looks
   very nice.
   
   I set up a test lab with two ESX vm's with CentOS 5.5, and followed the
   instructions here:
   http://www.clusterlabs.org/wiki/Install#Installing_on_EPEL_Compatible_D
   istributions:_RHEL.2C_CentOS.2C_etc
   Because of using yum as a package manager, I can easily query and
   upgrade packages.
   
   I can get everything I want to work fine for ipv4 addresses. However, I
   have a problem with ipv6 addresses (we use ipv6 extensively, and it is
   a hard requirement). It looks like the IPv6addr resource agent is
   broken.
   
   I can get information on other resource agents fine:
   
   [r...@lb1 ~]# crm configure ra info IPaddr2
   Manages virtual IPv4 addresses (Linux specific version)
   (ocf:heartbeat:IPaddr2)
   
   This Linux-specific resource manages IP alias IP addresses.
   It can add an IP alias, or remove one.
   ..
   
   However, if I try the same for the IPv6addr ra:
   
   [r...@lb1 ~]# crm configure ra info IPv6addr
   lrmadmin[29030]: 2010/08/24_14:51:14 ERROR:
   lrm_get_rsc_type_metadata(578): got a return code HA_FAIL from a reply
   message of rmetadata with function get_ret_from_msg.
   ERROR: ocf:heartbeat:IPv6addr: could not parse meta-data:
   
   
   Is this a known issue? Does anyone else use this ra?
   
   --
   
   
   With kind regards,
   
   
   Angelo Höngens
   
   Systems Administrator
   
   --
   NetMatch
   tourism internet software solutions
   
   Ringbaan Oost 2b
   5013 CA Tilburg
   T: +31 (0)13 5811088
   F: +31 (0)13 5821239
   
   mailto:a.hong...@netmatch.nl
   http://www.netmatch.nl
   --
   
  
  
  ___
  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
 
 ___
 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

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: 

Re: [Pacemaker] error: ocf:heartbeat:IPv6addr: could not parse meta-data

2010-08-24 Thread Angelo Höngens
On 24-8-2010 17:55, Dejan Muhamedagic wrote:
 
 BTW, any reason not to go with the prebuilt rpms from 
 clusterlabs.org?

I am, through their repository.

But when I download the prebuilt file from the clusterlabs website
(http://www.clusterlabs.org/rpm/epel-5/x86_64/resource-agents-1.0.3-2.6.el5.x86_64.rpm),
the /usr/lib/ocf/resource.d/heartbeat/IPv6addr is missing as well:

[r...@lb2 ~]# rpm -qpl resource-agents-1.0.3-2.6.el5.x86_64.rpm  | grep
-i ip
/usr/lib/ocf/resource.d/heartbeat/IPaddr
/usr/lib/ocf/resource.d/heartbeat/IPaddr2
/usr/lib/ocf/resource.d/heartbeat/IPsrcaddr
/usr/lib/ocf/resource.d/heartbeat/VIPArip
/usr/share/man/man7/ocf_heartbeat_IPaddr.7.gz
/usr/share/man/man7/ocf_heartbeat_IPaddr2.7.gz
/usr/share/man/man7/ocf_heartbeat_IPsrcaddr.7.gz
/usr/share/man/man7/ocf_heartbeat_VIPArip.7.gz
/usr/share/resource-agents/ocft/configs/IPaddr2
/usr/share/resource-agents/ocft/configs/IPsrcaddr

I guess whoever packaged the rpm's can answer why the file is missing,
but was that someone from the clusterlabs team or someone from the
linux-ha team? :)


-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
--
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg
+31 (0)13 5811088
+31 (0)13 5821239

a.hong...@netmatch.nl
www.netmatch.nl
--



___
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