Обсуждение: Fedora 13 killed dblink this week...
I think that something bad has happened to Fedora 13 this week.
This morning when I tried the following:
select dblink_connect('host=mbp user=levan dbname=levan password=xxxxxx')
I got the following error:
Error: could not load library "/usr/lib/pgsql/dblink.so": /usr/lib/libldap_r-2.4.so.2: undefined symbol:
ber_sockbuf_io_udp
The above worked ok last week...
I am running postgresql 8.4.4 from the rpms
[jerry@bigbox ~]$ rpm -qa | grep postgres
postgresql-8.4.4-1PGDG.fc12.i386
postgresql-server-8.4.4-1PGDG.fc12.i386
postgresql-pltcl-8.4.4-1PGDG.fc12.i386
postgresql-docs-8.4.4-1PGDG.fc12.i386
postgresql-libs-8.4.4-1PGDG.fc12.i386
postgresql-contrib-8.4.4-1PGDG.fc12.i386
postgresql-plpython-8.4.4-1PGDG.fc12.i386
postgresql-devel-8.4.4-1PGDG.fc12.i386
Also:
[jerry@bigbox ~]$ ldd /usr/lib/libldap_r-2.4.so.2
linux-gate.so.1 => (0x00852000)
liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x03c30000)
libresolv.so.2 => /lib/libresolv.so.2 (0x009a8000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x03aaa000)
libssl.so.10 => /usr/lib/libssl.so.10 (0x037fc000)
libcrypto.so.10 => /lib/libcrypto.so.10 (0x034da000)
libpthread.so.0 => /lib/libpthread.so.0 (0x0080f000)
libc.so.6 => /lib/libc.so.6 (0x00681000)
libdl.so.2 => /lib/libdl.so.2 (0x0082c000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00597000)
libgssapi_krb5.so.2 => /lib/libgssapi_krb5.so.2 (0x037cc000)
libkrb5.so.3 => /lib/libkrb5.so.3 (0x036e4000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00dfa000)
libk5crypto.so.3 => /lib/libk5crypto.so.3 (0x0379f000)
libz.so.1 => /lib/libz.so.1 (0x0086a000)
/lib/ld-linux.so.2 (0x0065f000)
libfreebl3.so => /lib/libfreebl3.so (0x005c9000)
libkrb5support.so.0 => /lib/libkrb5support.so.0 (0x00646000)
libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00637000)
libselinux.so.1 => /lib/libselinux.so.1 (0x00981000)
This happens on *both* of my Fedora 13 boxen...
Any suggestions
Jerry
17.Tem.2010 tarihinde 16:10 saatinde, Jerry LeVan
<jerry.levan@gmail.com> şunları yazdı:
> I think that something bad has happened to Fedora 13 this week.
>
> This morning when I tried the following:
>
> select dblink_connect('host=mbp user=levan dbname=levan
> password=xxxxxx')
>
> I got the following error:
>
> Error: could not load library "/usr/lib/pgsql/dblink.so": /usr/lib/
> libldap_r-2.4.so.2: undefined symbol: ber_sockbuf_io_udp
PostgreSQL RPMs need to be rebuilt against new ldap RPMs, I think. You
need to bug the PG repo maintainers.
Still, it is also Fedora's fault, too.
--
Devrim GÜNDÜZ
PostgreSQL DBA @ Akinon/Markafoni, Red Hat Certified Engineer
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
Jerry LeVan <jerry.levan@gmail.com> writes:
> I think that something bad has happened to Fedora 13 this week.
> This morning when I tried the following:
> select dblink_connect('host=mbp user=levan dbname=levan password=xxxxxx')
> I got the following error:
> Error: could not load library "/usr/lib/pgsql/dblink.so": /usr/lib/libldap_r-2.4.so.2: undefined symbol:
ber_sockbuf_io_udp
> The above worked ok last week...
Works for me, too, using the standard Fedora postgresql RPMs.
Theory 1: there's something wrong with the PGDG RPMs.
Theory 2: this week's F-13 update to openldap misfired on your box.
(If so, forcibly removing and reinstalling openldap might fix it.)
regards, tom lane
I wrote:
> Theory 2: this week's F-13 update to openldap misfired on your box.
> (If so, forcibly removing and reinstalling openldap might fix it.)
Oh, and Theory 3: see if restarting your postgresql server fixes it.
If you didn't restart then the old openldap libraries are probably
still in the server's address space. I'm not sure exactly how that
might lead to this symptom, but it sure looks like your libldap and
liblber are out of sync somehow.
regards, tom lane
On 07/17/2010 08:12 AM, Tom Lane wrote: > I wrote: > Oh, and Theory 3: see if restarting your postgresql server fixes it. > If you didn't restart then the old openldap libraries are probably > still in the server's address space. I'm not sure exactly how that > might lead to this symptom, but it sure looks like your libldap and > liblber are out of sync somehow. FWIW, I just tested on fedora 13 and sure enough, I started with the same error, and fixed it with a postgres restart. Joe -- Joe Conway credativ LLC: http://www.credativ.us Linux, PostgreSQL, and general Open Source Training, Service, Consulting, & Support
Вложения
On Sat, 2010-07-17 at 08:49 -0700, Joe Conway wrote: > On 07/17/2010 08:12 AM, Tom Lane wrote: > > I wrote: > > Oh, and Theory 3: see if restarting your postgresql server fixes it. > > If you didn't restart then the old openldap libraries are probably > > still in the server's address space. I'm not sure exactly how that > > might lead to this symptom, but it sure looks like your libldap and > > liblber are out of sync somehow. > > FWIW, I just tested on fedora 13 and sure enough, I started with the > same error, and fixed it with a postgres restart. > > Joe > > Wow, <wizard> Tom </wizard> strikes again... The server restart fixed the problem. I wish whoever is in charge of the yum rpm depository would get cracking on building the Fedora 13 repo... Jerry
Jerry LeVan <jerry.levan@gmail.com> writes:
> I wish whoever is in charge of the yum rpm depository would get
> cracking on building the Fedora 13 repo...
Uhm ... what's wrong with the Fedora-supplied PG RPMs?
regards, tom lane
On Jul 17, 2010, at 1:21 PM, Tom Lane wrote: > Jerry LeVan <jerry.levan@gmail.com> writes: >> I wish whoever is in charge of the yum rpm depository would get >> cracking on building the Fedora 13 repo... > > Uhm ... what's wrong with the Fedora-supplied PG RPMs? > > regards, tom lane For a long time Fedora rpms lagged the rpms that Devrim made for the yum repository. That is apparently no longer the case so I may well switch back :) Jerry
Jerry LeVan <jerry.levan@gmail.com> writes:
> On Jul 17, 2010, at 1:21 PM, Tom Lane wrote:
>> Uhm ... what's wrong with the Fedora-supplied PG RPMs?
> For a long time Fedora rpms lagged the rpms that Devrim made for
> the yum repository.
Well, I'm not allowed to bump to a new major PG version within a
stable Fedora release, but other than that I believe I've kept up...
regards, tom lane
17.Tem.2010 tarihinde 22:54 saatinde, Tom Lane <tgl@sss.pgh.pa.us> şunları yazdı: > Jerry LeVan <jerry.levan@gmail.com> writes: >> On Jul 17, 2010, at 1:21 PM, Tom Lane wrote: >>> Uhm ... what's wrong with the Fedora-supplied PG RPMs? > >> For a long time Fedora rpms lagged the rpms that Devrim made for >> the yum repository. > > Well, I'm not allowed to bump to a new major PG version within a > stable Fedora release, but other than that I believe I've kept up... That's I did create PostgreSQL RPM Repository ;) -- Devrim GÜNDÜZ PostgreSQL DBA @ Akinon/Markafoni, Red Hat Certified Engineer devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz