X-Original-To: pgsql-admin@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 69942925BB9 for ; Fri, 23 May 2003 10:38:08 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 11968-03 for ; Fri, 23 May 2003 10:37:49 -0400 (EDT) Received: from mail.virginia.edu (mail.Virginia.EDU [128.143.2.9]) by developer.postgresql.org (Postfix) with SMTP id 825F9924B00 for ; Fri, 23 May 2003 09:53:38 -0400 (EDT) Received: from smtp.mail.virginia.edu by mail.virginia.edu id aa23850; 23 May 2003 9:53 EDT Received: from virginia.edu (d-128-19-222.bootp.Virginia.EDU [128.143.19.222]) by smtp.mail.Virginia.EDU (8.11.7/8.11.6) with ESMTP id h4NDrVl13186 for ; Fri, 23 May 2003 09:53:32 -0400 Message-ID: <3ECE29A4.2010107@virginia.edu> Date: Fri, 23 May 2003 10:01:08 -0400 From: Jodi Kanter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Postgres Admin List Subject: upgrade issue Content-Type: multipart/alternative; boundary="------------000306030500040209040409" X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/329 X-Sequence-Number: 8891 --------------000306030500040209040409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit We just upgraded one of our Red Hat 7.3 machines from postgresql version 7.2.3 to version 7.3.2. All seemed to go smoothly until we received an error via our web interface. The following error occurred: install_driver(Pg) failed: Can't load '/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/DBD/Pg/Pg.so' for module DBD::Pg: libpq.so.2: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.6.1/i386-linux/DynaLoader.pm line 206, line 57. at (eval 4) line 3 Compilation failed in require at (eval 4) line 3, line 57. Perhaps a required shared library or dll isn't installed where expected at sessionlib.pl line 1507 The Pg driver is present, and was working before the upgrade. From this error I understand that Pg.so can't load libpq.so.2. No surprise since there is no /usr/lib/libpq.so.2 It appears that a symlink was created to file that does not exist. We solved the problem by moving libpq.so.2 from another machine. That machine has not been upgraded yet and is still running postgresql version 7.2.3. I was hoping someone could give me some insight to why this occured. Did we miss some part of the installation? I still have two machines to upgrade and would like to avoid this on the others. The rpms all appeared to have run without trouble. So, why didn't it install? Thanks Jodi -- _______________________________ Jodi L Kanter BioInformatics Database Administrator University of Virginia (434) 924-2846 jkanter@virginia.edu --------------000306030500040209040409 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit We just upgraded one of our Red Hat 7.3 machines from postgresql version 7.2.3 to version 7.3.2. All seemed to go smoothly until we received an error via our web interface. The following error occurred:

install_driver(Pg) failed: Can't load '/usr/lib/perl5/site_perl/5.6.0/i386-linux/auto/DBD/Pg/Pg.so' for module DBD::Pg: libpq.so.2: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.6.1/i386-linux/DynaLoader.pm line 206, <OR> line 57.
 at (eval 4) line 3
Compilation failed in require at (eval 4) line 3, <OR> line 57.
Perhaps a required shared library or dll isn't installed where expected
 at sessionlib.pl line 1507

The Pg driver is present, and was working before the upgrade. From this error I understand that Pg.so can't load libpq.so.2. No surprise since there is no /usr/lib/libpq.so.2   It appears that a symlink was created to file that does not exist.

We solved the problem by moving libpq.so.2 from another machine. That machine has not been upgraded yet and is still running postgresql version 7.2.3.

I was hoping someone could give me some insight to why this occured. Did we miss some part of the installation?  I still have two machines to upgrade and would like to avoid this on the others. The rpms all appeared to have run without trouble. So, why didn't it install?

Thanks
Jodi

--
________________________________

_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu


 

 

 

--------------000306030500040209040409--