Re: newbie: up2date snafu (more info)

[Tim Wunder <wundertp rescobaltimore com>]

It seems that openssl may be one of the culprits. My webserver error log
is complaining about a line in my httpd.conf file:
Cannot load /etc/httpd/modules/libssl.so into server: symbol __sysconf,
version GLIBC_2.2 not defined in file libc.so.6 with link time reference

I assume that up2date uses openssl/openssh for connection to the redhat
network. I'm gonna try backing out the openssl and openssh RPMS and
reinstalling the originals. I'll see if that changes anything...

Regards, 
Tim


Tim Wunder wrote:
> 
> Hi,
> New to the list.
> Been using RedHat 7.0 for several months now as a samba server and
> intranet web server, no real problems.
> 
> Doing some maintenance with up2date and performed updates to the
> following:
>  gnorpm-0.95.1-6
>  mod-perl-1.24-6
>  nfs-utils-0.3.1-7
>  openssh 2.5.2p2-1 (openssh-askpass, openssh-askpass-gnome,
> openssh-clients, openssh-server too)
>  perl-0.5.6-10a
>  procmail-3.21-0
>  rpm-4.02 (rpm-build, rpm-devel, rpm-python too)
>  sendmail-8.11.6
>  xinetd-2.3.3-1
>  openssl-0.95.9
>  python-xmlrpc-1.4-1
> 
> Now, when I run up2date, it gives me this error:
> 
> [root localserver RPMs]# up2date
> Traceback (innermost last):
> File "/usr/sbin/up2date", line16, in ?
> import up2date
> File "/usr/share/rhn/up2date/up2date.py", line 13, in ?
> import socket
> ImportError: symbol __sysconf, version GLIBC_2.2 not defined in file
> libc.so.6 with link time reference
> 
> If I remove the 2.5.4-1 version of up2date and re-install the 2.0.5
> version, I still get the same error. How do I fix this? It seems to me
> that something wants glibc 2.2 and I have 2.1.92 still installed. I'd
> rather not try to update glibc at this point, but if that's the way to
> go, I'll do it.
> 
> I've contemplated removing the rpm updates, but that's complicated by
> the fact that you kinda need rpm around to use it for updating rpms.
> 
> I posted a message on the RedHat Network support forum, then noticed
> several other posts with the same problem. Nobody's responded with any
> solution, yet.
> 
> Any help would be appreciated.
> 
> Regards,
> 
> Tim Wunder