On Wed, Nov 19, 2008 at 04:06, Alex Strachan <[EMAIL PROTECTED]> wrote: > Similar issue, did eventually manage to upgrade. > > RHEL4 64bit, 2 node cluster > > Current software... > heartbeat-2.99.2-3.1 > heartbeat-common-2.99.2-3.1 > heartbeat-resources-2.99.2-3.1 > libheartbeat2-2.99.2-3.1 > libopenais2-0.80.3-10.1 > libpacemaker3-1.0.0-4.1 > openais-0.80.3-10.1 > pacemaker-1.0.0-4.1 > pacemaker-pygui-1.4-11.1 > > Tried upgrading (software from > http://download.opensuse.org/repositories/server:/ha-clustering/RHEL_4/x86_6 > 4/?C=M;O=A) > > [EMAIL PROTECTED] 20081114]# rpm -Uvh libheartbeat2-2.99.2-4.1.x86_64.rpm > libopenais2-0.80.3-11.1.x86_64.rpm > warning: libheartbeat2-2.99.2-4.1.x86_64.rpm: V3 DSA signature: NOKEY, key > ID 1d362aeb > error: Failed dependencies: > liblrm.so.0()(64bit) is needed by (installed) > heartbeat-common-2.99.2-3.1.x86_64 > liblrm.so.0()(64bit) is needed by (installed) > pacemaker-1.0.0-4.1.x86_64 > liblrm.so.0()(64bit) is needed by (installed) > pacemaker-pygui-1.4-11.1.x86_64
This looks like a slightly different issue since the SO number changed. I've just made some spec file changes to be sure I notice these SO increases in the future (which would require the libheartbeat number to go up too). > The rpm upgrade completed by installing in this order > > # rpm -Uvh heartbeat-2.99.2-4.1.x86_64.rpm > heartbeat-common-2.99.2-4.1.x86_64.rpm > heartbeat-resources-2.99.2-4.1.x86_64.rpm > libheartbeat2-2.99.2-4.1.x86_64.rpm pacemaker-1.0.1-1.1.x86_64.rpm > pacemaker-pygui-1.4-11.5.x86_64.rpm > > # rpm -Uvh libopenais2-0.80.3-11.1.x86_64.rpm > libpacemaker3-1.0.1-1.1.x86_64.rpm openais-0.80.3-11.1.x86_64.rpm > > To activate I did > Stop heartbeat (on inactive host) > Upgrade RPM > Start heartbeat > Stop Heartbeat (on active) > Upgrade RPM > Start heartbeat > > So far, so good. > > -- > Alex > > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:linux-ha- >> [EMAIL PROTECTED] On Behalf Of Andrew Beekhof >> Sent: Wednesday, 19 November 2008 6:05 AM >> To: General Linux-HA mailing list >> Subject: Re: [Linux-HA] Missing dependency on new RPM's >> >> On Tue, Nov 18, 2008 at 20:44, Andrew Beekhof <[EMAIL PROTECTED]> wrote: >> > On Tue, Nov 18, 2008 at 16:48, bart <[EMAIL PROTECTED]> wrote: >> >> >> >>> Hmmm - thats really weird. >> >>> >> >>> The liblrm.so.2 dependancy is an automatic one based the liblrm >> >>> shared >> >>> library that Pacemaker was built against. >> >>> Perhaps you were unlucky and mirrored the repo at a point when it was >> >>> rebuilding... refreshing your local mirror might help. >> >>> >> >>> As an advantage, you'll get the 1.0.1 update from earlier today :-) >> >>> >> >> >> >> Thanks! I just synced, and the problem appears to be still here: >> >> >> >> [EMAIL PROTECTED] scripts]# yum update >> >> Loading "fastestmirror" plugin >> >> Loading mirror speeds from cached hostfile >> >> * CentOS-5.1-epel-x86_64: 192.168.0.4 >> >> * CentOS-5.1-extras-x86_64: 192.168.0.4 >> >> * CentOS-5-x86_64: 192.168.0.4 >> >> * CentOS-5-updates-x86_64: 192.168.0.4 >> >> * CentOS-5.1-extra-x86_64: 192.168.0.4 >> >> * CentOS-5-novell-x86_64: 192.168.0.4 >> >> * CentOS-5.1-testing-x86_64: 192.168.0.4 >> >> * CentOS-5.1-dagwieers-x86_64: 192.168.0.4 >> >> Setting up Update Process >> >> Resolving Dependencies >> >> --> Running transaction check >> >> ---> Package pacemaker.x86_64 0:1.0.1-1.1 set to be updated >> >> ---> Package heartbeat.x86_64 0:2.99.2-4.1 set to be updated >> >> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common >> >> ---> Package libheartbeat2.x86_64 0:2.99.2-4.1 set to be updated >> >> ---> Package heartbeat-resources.i386 0:2.99.2-4.1 set to be updated >> >> ---> Package libxml2-python.x86_64 0:2.6.26-2.1.2.7 set to be updated >> >> ---> Package heartbeat.i386 0:2.99.2-4.1 set to be updated >> >> ---> Package pacemaker.i386 0:1.0.1-1.1 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: pacemaker >> >> --> Finished Dependency Resolution >> >> --> Running transaction check >> >> ---> Package pacemaker.x86_64 0:1.0.1-1.1 set to be updated >> >> ---> Package heartbeat.x86_64 0:2.99.2-4.1 set to be updated >> >> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common >> >> ---> Package libheartbeat2.x86_64 0:2.99.2-4.1 set to be updated >> >> ---> Package heartbeat-resources.i386 0:2.99.2-4.1 set to be updated >> >> ---> Package libxml2-python.x86_64 0:2.6.26-2.1.2.7 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: pacemaker >> >> ---> Package libxml2.x86_64 0:2.6.26-2.1.2.7 set to be updated >> >> --> Running transaction check >> >> ---> Package heartbeat-common.i386 0:2.99.2-4.1 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: heartbeat-common >> >> ---> Package pacemaker.i386 0:1.0.1-1.1 set to be updated >> >> --> Processing Dependency: liblrm.so.2 for package: pacemaker >> >> --> Finished Dependency Resolution >> >> Error: Missing Dependency: liblrm.so.2 is needed by package heartbeat- >> common >> >> Error: Missing Dependency: liblrm.so.2 is needed by package pacemaker >> >> >> >> I do not see a package librm on the SuSe mirror, and it's doesn't >> appear to be available anywhere else... Isn't that the problem?? >> > >> > No. liblrm.* is be in libheartbeat2 >> > >> > [EMAIL PROTECTED] pacemaker $ wget >> > http://download.opensuse.org/repositories/server:/ha- >> clustering/CentOS_5/i386/libheartbeat2-2.99.2-4.1.i386.rpm >> > 20:39:17 (13.59 MB/s) - `libheartbeat2-2.99.2-4.1.i386.rpm' saved >> > [193175/193175] >> > >> > [EMAIL PROTECTED] pacemaker $ rpm -qlp libheartbeat2-2.99.2-4.1.i386.rpm >> > warning: libheartbeat2-2.99.2-4.1.i386.rpm: Header V3 DSA signature: >> > NOKEY, key ID 1d362aeb >> > /usr/lib/libapphb.so.2 >> > /usr/lib/libapphb.so.2.0.0 >> > /usr/lib/liblrm.so.2 <------- here >> > /usr/lib/liblrm.so.2.0.0 >> > /usr/lib/libpils.so.2 >> > /usr/lib/libpils.so.2.0.0 >> > /usr/lib/libplumb.so.2 >> > /usr/lib/libplumb.so.2.0.0 >> > /usr/lib/libplumbgpl.so.2 >> > /usr/lib/libplumbgpl.so.2.0.0 >> > /usr/lib/libstonith.so.1 >> > /usr/lib/libstonith.so.1.0.0 >> > [EMAIL PROTECTED] pacemaker $ >> > >> > [EMAIL PROTECTED] pacemaker $ rpm -q --provides -p >> > libheartbeat2-2.99.2-4.1.i386.rpm >> > warning: libheartbeat2-2.99.2-4.1.i386.rpm: Header V3 DSA signature: >> > NOKEY, key ID 1d362aeb >> > libapphb.so.2 >> > liblrm.so.2 <---- here again >> > libpils.so.2 >> > libplumb.so.2 >> > libplumbgpl.so.2 >> > libstonith.so.1 >> > libheartbeat2 = 2.99.2-4.1 >> > >> > Comparing that to the x86_64 packages... >> > >> > [EMAIL PROTECTED] pacemaker $ rpm -q -l -p libheartbeat2-2.99.2- >> 4.1.x86_64.rpm >> > warning: libheartbeat2-2.99.2-4.1.x86_64.rpm: Header V3 DSA signature: >> > NOKEY, key ID 1d362aeb >> > /usr/lib64/libapphb.so.2 >> > /usr/lib64/libapphb.so.2.0.0 >> > /usr/lib64/liblrm.so.2 >> > /usr/lib64/liblrm.so.2.0.0 >> > /usr/lib64/libpils.so.2 <--- as expected >> > /usr/lib64/libpils.so.2.0.0 >> > /usr/lib64/libplumb.so.2 >> > /usr/lib64/libplumb.so.2.0.0 >> > /usr/lib64/libplumbgpl.so.2 >> > /usr/lib64/libplumbgpl.so.2.0.0 >> > /usr/lib64/libstonith.so.1 >> > /usr/lib64/libstonith.so.1.0.0 >> > [EMAIL PROTECTED] pacemaker $ >> > >> > [EMAIL PROTECTED] pacemaker $ rpm -q --provides -p >> > libheartbeat2-2.99.2-4.1.x86_64.rpm >> > warning: libheartbeat2-2.99.2-4.1.x86_64.rpm: Header V3 DSA signature: >> > NOKEY, key ID 1d362aeb >> > libapphb.so.2()(64bit) >> > liblrm.so.2()(64bit) <--- could these extra brackets be the issue? >> > libpils.so.2()(64bit) >> > libplumb.so.2()(64bit) >> > libplumbgpl.so.2()(64bit) >> > libstonith.so.1()(64bit) >> > libheartbeat2 = 2.99.2-4.1 >> > >> >> Scratch that, I just looked at the pacemaker requires >> >> [EMAIL PROTECTED] pacemaker $ rpm -q --requires -p >> pacemaker-1.0.1-1.1.x86_64.rpm.1 >> warning: pacemaker-1.0.1-1.1.x86_64.rpm.1: Header V3 DSA signature: >> NOKEY, key ID 1d362aeb >> /bin/sh >> /usr/bin/env >> /usr/bin/python >> libSaMsg.so.2()(64bit) >> libapphb.so.2()(64bit) >> libbz2.so.1()(64bit) >> libc.so.6()(64bit) >> libc.so.6(GLIBC_2.2.5)(64bit) >> libc.so.6(GLIBC_2.3)(64bit) >> libccmclient.so.1()(64bit) >> libcib.so.1()(64bit) >> libcrmcluster.so.1()(64bit) >> libcrmcommon.so.2()(64bit) >> libcrypto.so.6()(64bit) >> libdl.so.2()(64bit) >> libglib-2.0.so.0()(64bit) >> libgnutls.so.13()(64bit) >> libgnutls.so.13(GNUTLS_1_3)(64bit) >> libhbclient.so.1()(64bit) >> liblrm.so.2()(64bit) <---- the exact same string >> thats in the libheartbeat2 provides section >> libncurses.so.5()(64bit) >> libpam.so.0()(64bit) >> libpam.so.0(LIBPAM_1.0)(64bit) >> libpe_rules.so.2()(64bit) >> libpe_status.so.2()(64bit) >> libpengine.so.3()(64bit) >> libpils.so.2()(64bit) >> libplumb.so.2()(64bit) >> librt.so.1()(64bit) >> libstonith.so.1()(64bit) >> libstonithd.so.0()(64bit) >> libtransitioner.so.1()(64bit) >> libuuid.so.1()(64bit) >> libxml2.so.2()(64bit) >> libxslt.so.1()(64bit) >> rpmlib(CompressedFileNames) <= 3.0.4-1 >> rpmlib(PartialHardlinkSets) <= 4.0.4-1 >> rpmlib(PayloadFilesHavePrefix) <= 4.0-1 >> rtld(GNU_HASH) >> >> So I'm at a loss to find anything wrong with the packages. >> Can you try bypassing YUM and just using rpm -Uvh ? >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
