On 06/06/2013, at 3:41 PM, Larry Brigman <larry.brig...@gmail.com> wrote:
> I pulled the git tree but it failed to build in a number of ways when trying > to build on centos 5.9. > > make rpm-dep: > .... > Checking for new repos for mirrors > Enabling epel-source repository > Enabling rpmfusion-free-updates-testing-source repository > No such package(s): pacemaker-fedora.spec.src > make: *** [rpm-dep] Error 1 > > Since I have built 1.1.5 on this machine I went for a manual config. > Instead I just manually did ./autogen.sh && ./configure > It shows 1.1.9 at the end of configure. > > make rc: > make rc > sort: invalid option -- V > Try `sort --help' for more information. Urgh. Looks like RHEL5 is older than "sort -V". See if this gets you any further: make TAG=Pacemaker-1.1.10-rc3 rpm > make TAG= rpm > make[1]: Entering directory `/usr/src/devel/pacemaker/pacemaker' > rm -f pacemaker-dirty.tar.* pacemaker-tip.tar.* pacemaker-HEAD.tar.* > if [ ! -f ClusterLabs-pacemaker-.tar.gz ]; then > \ > rm -f pacemaker.tar.*; > \ > if [ = dirty ]; then \ > git commit -m "DO-NOT-PUSH" -a; > \ > git archive --prefix=ClusterLabs-pacemaker-/ HEAD | gzip > > ClusterLabs-pacemaker-.tar.gz; \ > git reset --mixed HEAD^; > \ > else > \ > git archive --prefix=ClusterLabs-pacemaker-/ | gzip > > ClusterLabs-pacemaker-.tar.gz; \ > fi; > \ > echo `date`: Rebuilt ClusterLabs-pacemaker-.tar.gz; > \ > else > \ > echo `date`: Using existing tarball: > ClusterLabs-pacemaker-.tar.gz;\ > fi > Wed Jun 5 22:30:54 PDT 2013: Using existing tarball: > ClusterLabs-pacemaker-.tar.gz > sort: invalid option -- V > Try `sort --help' for more information. > rm -f *.src.rpm > cp pacemaker-fedora.spec pacemaker.spec > if [ -e build.counter ]; then \ > echo 1 > build.counter; \ > fi > sed -i.sed 's/Source0:.*/Source0:\ ClusterLabs-pacemaker-.tar.gz/' > pacemaker.spec > sed -i.sed 's/global\ specversion.*/global\ specversion\ 1/' pacemaker.spec > sed -i.sed 's/global\ upstream_version.*/global\ upstream_version\ /' > pacemaker.spec > sed -i.sed 's/global\ upstream_prefix.*/global\ upstream_prefix\ > ClusterLabs-pacemaker/' pacemaker.spec > case in \ > Pacemaker*) sed -i.sed 's/Version:.*/Version:\ /' > pacemaker.spec;; \ > *) sed -i.sed 's/Version:.*/Version:\ /' > pacemaker.spec;; \ > esac > /bin/sh: -c: line 1: syntax error near unexpected token `Pacemaker*' > /bin/sh: -c: line 1: ` Pacemaker*) sed -i.sed 's/Version:.*/Version:\ /' > pacemaker.spec;; \' > make[1]: *** [srpm-fedora] Error 2 > make[1]: Leaving directory `/usr/src/devel/pacemaker/pacemaker' > make: *** [rc] Error 2 > > > > > > On Wed, Jun 5, 2013 at 4:20 AM, Kirill Proskurin <k.prosku...@corp.mail.ru> > wrote: > On 6/5/13 14:59 , Andreas Mock wrote: > Hi Andrew, > > waiting for the RHEL 6.x build of pacemaker 1.1.10 I want to ask > whether there can be done something for finding the memory leaks. > If so, than explain the steps needed in detail. Currently there > are two real clusters available to do testing. > > (Questions: Do you need logs? Debug-Log? Some excerpt? Shall we look > for certain patterns?) > > > Same thing, but for RHEL 5. > If I can get RHEL5 compatible rpm I can test it on my cluster(6 clusters > running) > > > > > -----Ursprüngliche Nachricht----- > Von: Andrew Beekhof [mailto:and...@beekhof.net] > Gesendet: Mittwoch, 5. Juni 2013 04:26 > An: The Pacemaker cluster resource manager > Betreff: Re: [Pacemaker] Release candidate: 1.1.10-rc3 > > > On 23/05/2013, at 12:33 PM, Andrew Beekhof <and...@beekhof.net> wrote: > > Please keep the bug reports coming in. There is a good chances that > this will be the final release candidate and 1.1.10 will be tagged on > May 30th. > > I am delaying rc4 until we can get definitive closure on the crmd memory > leak(s). > Valgrind has given it a clean bill of health, however the process still > appears to be growing over time and at strange intervals, so its not yet > clear what is responsible. > > Beyond fixes for memory leaks, rc4 will include a workaround for > inconsistent tls handshake behavior between gnutls versions and some > improvements to the way crm_resource can be used to move resources around. > I hope to provide more detail soon. > > -- Andrew > > > -- > Best regards, > Proskurin Kirill > > > _______________________________________________ > 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://bugs.clusterlabs.org > > _______________________________________________ > 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://bugs.clusterlabs.org _______________________________________________ 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://bugs.clusterlabs.org
