sql-ledger-users

[SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

   I just upgraded the PostgreSQL backend from -8.1.4 to -8.3.3, and I
restored the data to the new version. When I try to invoke SL I get a server
error.

   The relevant lines in /var/log/apache/error_log are:

[Wed Jun 18 10:52:44 2008] [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.8/i486-linux
/auto/DBD/Pg/Pg.so' for module DBD::Pg: libpq.so.4: cannot open shared
object file: No such file or directory at /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm 
line 230. at (eval 10) line 3 Compilation failed in require at (eval 10) line 3.
Perhaps a required shared library or dll isn't installed where expected at SL/User.pm line 103
Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
[Wed Jun 18 10:58:19 2008] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl

   Do these messages mean that the installed DBD::Pg module does not work
with the most recent version of Postgres, and that I need to update that
module? Or, is there something else going on here?

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Rich Shepard wrote:

>   Do these messages mean that the installed DBD::Pg module does not work
> with the most recent version of Postgres, and that I need to update that
> module?

   I just upgraded DBD::Pg, and now have different errors:

[Wed Jun 18 11:39:51 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
install_driver(Pg) failed: DBD::Pg object version undef does not match
bootstrap
  parameter 2.8.1 at /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm line 253.
Compilation failed in require at (eval 10) line 3.

  at SL/User.pm line 103
Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
[Wed Jun 18 11:39:57 2008] [error] [client 127.0.0.1] Premature end of
script he
aders: /usr/local/sql-ledger/login.pl

   My knowledge of Perl hovers around zero, so I'd really appreciate some
help on how to fix the problem.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Wallace R. C. <wrc...@gm...>]

On Wed, Jun 18, 2008 at 11:43 AM, Rich Shepard <rsh...@ap...> wrote:
...
>  at SL/User.pm line 103
> Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
> [Wed Jun 18 11:39:57 2008] [error] [client 127.0.0.1] Premature end of
> script headers: /usr/local/sql-ledger/login.pl

I've seen this error caused by something as simple as an
M$-WinDoze(tm) text file (with carriage-return+linefeed sequences to
terminate a line) on a Un*x (or Un*x-like, i.e., Linux) system, which
expects only linefeeds terminating lines.

If you edit your login.pl file with VIM (VI-iMproved), see what kind
of format the file has.  For example, when I edit a Un*x file, the
status line on the bottom of the screen will indicate so:

    "blah.xml" [unix] [readonly]  445L, 17033C   92,6-41    18%

To force the correct (Un*x) format of a non-Un*x file (on your Un*x
system), use the following command in VIM:

    :set ff=unix

Then save the file, & you're done.
-- 
Best Regards,
Wallace

Re: [SL] Server Error After Backend Upgrade

[Stuart L. <sl...@cc...>]

On 水, 2008-06-18 at 13:23 -0700, Wallace Roberts Consulting wrote:
> To force the correct (Un*x) format of a non-Un*x file (on your Un*x
> system), use the following command in VIM:
> 
>     :set ff=unix
> 
> Then save the file, & you're done.

Nice. You can also use the dos2unix utility, or load the file into emacs
and do C-x RET f and then enter undecided-unix. Or in emacs M-x
set-buffer-file-coding-system undecided-unix.
-- 
Stuart Luppescu -=- slu .at. ccsr.uchicago.edu        
University of Chicago -=- CCSR 
才文と智奈美の父 -=-    Kernel 2.6.24-gentoo-r8                
Distress, n.:  A disease incurred by exposure to
 the prosperity of a friend.   -- Ambrose Bierce,
 "The Devil's Dictionary" 
 
 

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> I've seen this error caused by something as simple as an M$-WinDoze(tm)
> text file (with carriage-return+linefeed sequences to terminate a line) on
> a Un*x (or Un*x-like, i.e., Linux) system, which expects only linefeeds
> terminating lines.

Wallace,

   That could be, but we've not done Microsoft here for more than a decade.
The only change here has been to the db back end, and the error seems to
refer to the perl DBD::Pg module.

> To force the correct (Un*x) format of a non-Un*x file (on your Un*x
> system), use the following command in VIM:

   I've used dos2unix, but that's not appropriate here.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Wallace R. C. <wrc...@gm...>]

On Wed, Jun 18, 2008 at 1:35 PM, Rich Shepard <rsh...@ap...> wrote:
> On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:
>
>> I've seen this error caused by something as simple as an M$-WinDoze(tm)
>> text file (with carriage-return+linefeed sequences to terminate a line) on
>> a Un*x (or Un*x-like, i.e., Linux) system, which expects only linefeeds
>> terminating lines.
>
> Wallace,
>
> That could be, but we've not done Microsoft here for more than a decade.
> The only change here has been to the db back end, and the error seems to
> refer to the perl DBD::Pg module.

My bad; I would check the new file,
/usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

-- 
Best Regards,
Wallace

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> My bad; I would check the new file,
> /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

Wallace,

   That's not been changed since 2006-09-01 21:39.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> My bad; I would check the new file,
> /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

Wallace,

   I think the problem is related to having two versions of Pg.pm installed.
Apparently, CPAM does not upgrade and older version by replacing it with the
newer version, but leaves both versions, and in different directories. One
of the local perl mongers is looking at the situation.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Paul T. <pt...@wa...>]

Are you sure your Postgresql db is running correctly?
I upgraded hardware and changed to opensuse 11.0 beta in the same run.
On starting postgresql, opensuse gave the warning that the DB would tremain
using 8.1 iso 8.3 version of Postgresql untill I had updated all db related
files. Something similar might be going on with two versions of Pg.pm but
without the nice warnings?


2008/6/18 Rich Shepard <rsh...@ap...>:

> On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:
>
> > My bad; I would check the new file,
> > /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.
>
> Wallace,
>
>   I think the problem is related to having two versions of Pg.pm installed.
> Apparently, CPAM does not upgrade and older version by replacing it with
> the
> newer version, but leaves both versions, and in different directories. One
> of the local perl mongers is looking at the situation.
>
> Thanks,
>
> Rich
>
> --
> Richard B. Shepard, Ph.D.               |  Integrity            Credibility
> Applied Ecosystem Services, Inc.        |            Innovation
> <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax:
> 503-667-8863
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>

Re: [SL] Server Error After Backend Upgrade -- FIXED!

[Rich S. <rsh...@ap...>]

On Thu, 19 Jun 2008, Paul Tammes wrote:

> Are you sure your Postgresql db is running correctly? I upgraded hardware
> and changed to opensuse 11.0 beta in the same run. On starting postgresql,
> opensuse gave the warning that the DB would tremain using 8.1 iso 8.3
> version of Postgresql untill I had updated all db related files. Something
> similar might be going on with two versions of Pg.pm but without the nice
> warnings?

Paul,

   When I looked at /var/log/apache/error_log I saw that the problem was most
likely with the DBD::Pg version; the installed one was too old. One of the
local perl mongers verified that.

   My first attempts to upgrade using the CPAN client failed. Today, I
removed the Pg.pm that was apparently broken and forced a re-installation.
This time it worked.

   Since I can now log in and use SL, this thread can be closed with success.
Thank you very much for your input, you are correct that it was the Pg.pm
module that needed to be updated.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863