PostgreSQL Discussion - Re: Access Problem After Version Upgrade -- Update

Author

Re: Access Problem After Version Upgrade -- Update

Doug McNaught

2006-01-26, 4:57 pm

Rich Shepard <rshepard@appl-ecosys.com> writes:

> So, now I can see the tables in the various databases, but SQL-Ledger still
> cannot:
>
> Internal Server Error
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> How do I get this fixed, please?

That's a webserver error usually meaning a CGI script crashed or gave
bad output. Look in the webserver error log file to see what
happened.

-Doug

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Jim Buttafuoco

2006-01-26, 4:57 pm

looks like perl/DBD::Pg is looking for libpq.so.3 but postgresql 8.1.X supplies libpq.so.4. You need to rebuild DBD::Pg
to get this to work (atleast that is what I have been doing for my upgrades from 7.4.X to 8.1.2)

Jim

---------- Original Message -----------
From: Rich Shepard <rshepard@appl-ecosys.com>
To: Doug McNaught <doug@mcnaught.org>
Cc: pgsql-general@postgresql.org
Sent: Thu, 26 Jan 2006 09:30:05 -0800 (PST)
Subject: Re: [GENERAL] Access Problem After Version Upgrade -- Update

> On Thu, 26 Jan 2006, Doug McNaught wrote:
>
>
> Doug,
>
> Sigh. All I see there are references to SQL-Ledger scripts not finding
> libraries (which are installed where SQL-Ledger is looking for them), and
> it's login.pl script failing to run. When I posted on that mail list, Dieter
> pulled the thread and wrote me an angry message that SQL-Ledger is not
> broken, but PostgreSQL is.
>
> The postmaster is running, and I (as an individual) can now see what
> databases are there. So, that permission error on the socket is fixed and it
> looks like postgres is doing just what it should be doing.
>
> Dieter Simander tells me there's nothing wrong with SL. Here's
> /var/log/apache/error_log:
>
> [Thu Jan 26 08:59:36 2006] [error] [client 127.0.0.1] Premature end of script headers: /usr/local/sql-ledger/login.pl
> install_driver(Pg) failed: Can't load '/usr/lib/perl5/site_perl/5.8.7/i486-linux/auto/DBD/Pg/Pg.so' for module
> DBD::Pg: libpq.so.3: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.7/i486-
> linux/DynaLoader.pm line 230. at (eval 8) line 3 Compilation failed in require at (eval 8) line 3. Perhaps a
> required shared library or dll isn't installed where expected at SL/User.pm line 116 Compilation failed in
> require at /usr/local/sql-ledger/login.pl line 92.
> [Thu Jan 26 09:03:29 2006] [error] [client 127.0.0.1] Premature end of script headers: /usr/local/sql-ledger/login.pl
>
> Now, when I point firefox at:
> http://eia.appl-ecosys.com/webcollab-1.70/index/php
>
> Up comes the Webcollab login page and I can log in.
>
> This suggests to me that there's nothing wrong with apache (httpd), either.
>
> Checkmate.
>
> Thanks,
>
> Rich
>
> --
> Richard B. Shepard, Ph.D. | Author of "Quantifying Environmental
> Applied Ecosystem Services, Inc. (TM) | Impact Assessments Using Fuzzy Logic"
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
------- End of Original Message -------

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Tom Lane

2006-01-26, 4:57 pm

Rich Shepard <rshepard@appl-ecosys.com> writes:
> install_driver(Pg) failed: Can't load '/usr/lib/perl5/site_perl/5.8.7/i486-linux/auto/DBD/Pg/Pg.so' for module DBD::Pg: libpq.so.3: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.7/i486-linux/DynaLoader.pm line 230.

This seems to be your problem right here. Is libpq.so.3 installed (as
opposed to some other version number)? Is it where the dynamic loader
will look for it?

I'm guessing your upgrade replaced libpq.so.3 with libpq.so.4. Did you
perhaps override RPM's complaints that there was a dependency on
libpq.so.3? (If there wasn't one, there's something wrong with the
packaging of DBD::Pg.) You probably need to either put back libpq.so.3,
or update DBD::Pg.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly

Sponsored Links