CentOS - Apr 2006 - bootup error - undefined symbol: lvm_snprintf after yum update

This is an x86_64 system that I just updated from 4.2 to 4.3
(including the csgfs stuff).

When I watch the bootup on the console, I see an error:

lvm.static: symbol lookup error: /usr/lib64/liblvm2clusterlock.so:
   undefined symbol: lvm_snprintf

This error comes immediately after the "Activating VGs" line, so it
appears to be triggered by the vgchange command in the clvmd startup
file.  I have another, identically configured, server which I have not
updated yet.  This server does not give this error.

Everything seems to be working fine, so is this something I need to
worry about?

--
Bowie

Hmm...no responses at all.  Has anyone else seen this error?  I'm
reluctant to move toward production with this server if I can't find
out something about this error.

Bowie

Bowie wrote:
> This is an x86_64 system that I just updated from 4.2 to 4.3
> (including the csgfs stuff).
> 
> When I watch the bootup on the console, I see an error:
> 
> lvm.static: symbol lookup error: /usr/lib64/liblvm2clusterlock.so:
>    undefined symbol: lvm_snprintf
> 
> This error comes immediately after the "Activating VGs" line, so
it
> appears to be triggered by the vgchange command in the clvmd startup
> file.  I have another, identically configured, server which I have not
> updated yet.  This server does not give this error.
> 
> Everything seems to be working fine, so is this something I need to
> worry about?

Johnny Hughes wrote:
> On Tue, 2006-04-18 at 16:25 -0400, Bowie Bailey wrote:
> > Hmm...no responses at all.  Has anyone else seen this error?  I'm
> > reluctant to move toward production with this server if I can't
find
> > out something about this error.
> 
> I have reinstalled all the CSGFS files and rebuilt the SRPM in question
> (lvm2-cluster-2.02.01-1.2.RHEL4.x86_64.rpm).  Try this RPM and see if
> you get the same error:
> 
>
http://centos.hughesjr.com/testing/RPMS/lvm2/lvm2-cluster-2.02.01-1.2.RHEL4.
x86_64.rpm
> 
> I also rebuilt the lvm2 SRPM as well ... If the above package
> reinstalled did not do anything, then try reinstalling this one:
> 
>
http://centos.hughesjr.com/testing/RPMS/lvm2/lvm2-2.02.01-1.3.RHEL4.x86_64.r
pm
> 
> I can not check the CentOS csgfs packages against the upstream ones as
> we do not have access to them, however I did check the second package
> (part of RHEL) against the upstream file and I did check the older
> packages built by CentOS against each of the newly built packages, and
> there was no differences at all.
> 
> Please install the top package first and test, then the second one and
> test. If installing both of these did not work, are you using a non
> CentOS kernel ... or maybe not the 2.6.9-34.EL or 2.6.9-34.ELsmp kernel
> provided by CentOS?
> 
> > Bowie wrote:
> > > This is an x86_64 system that I just updated from 4.2 to 4.3
> > > (including the csgfs stuff).
> > > 
> > > When I watch the bootup on the console, I see an error:
> > > 
> > > lvm.static: symbol lookup error:
/usr/lib64/liblvm2clusterlock.so:
> > >    undefined symbol: lvm_snprintf
> > > 
> > > This error comes immediately after the "Activating VGs"
line, so it
> > > appears to be triggered by the vgchange command in the clvmd
startup
> > > file.  I have another, identically configured, server which I
have not
> > > updated yet.  This server does not give this error.
> > > 
> > > Everything seems to be working fine, so is this something I need
to
> > > worry about?
The lvm2-cluster rpm is identical to the one already installed via
yum.

The lvm2 rpm is the same version, but there is apparently a difference
in the file somewhere.

Since these files have the same version number as what is already
installed, what is the cleanest way of reinstalling them?  I can
remove and reinstall lvm2-cluster, but I can't do this with lvm2 since
it is required by other things.

This system is a vanilla Centos 4 system that has been updated to
current via the standard yum repositories plus the csgfs repository.
There are a few applications that were built from source, but these
are all high-level applications and shouldn't affect the cluster at
all.

-- 
Bowie