On Wed, 22 Dec 2010, Rolf Stöckli wrote:
Finding is not the problem, the path is correct (DBD::Pg means DBD/Pg.pm) . The file is not "loadable".
Rolf, But, I think that I have found the source of the problem. There are two Pg.pm on the system. I don't know how this happened, but I think perl is looking at the wrong one when trying to run the SL scripts. When I search the system for Pg.pm I find these: /usr/lib/perl5/site_perl/5.10.1/i486-linux-thread-multi/Bundle/DBD/Pg.pm /usr/lib/perl5/site_perl/5.10.1/i486-linux-thread-multi/DBD/Pg.pm On CPAN I noticed a bundle available for download as well as the single module tarball. I chose the latter. I suspect that I can delete the entire Bundle subdirectory to fix the problem, because when I check the file sizes and installation dates they differ. This is the one that I believe is correct: -r--r--r-- 1 root root 163956 2010-12-21 15:46 /usr/lib/perl5/site_perl/5.10.1/i486-linux-thread-multi/DBD/Pg.pm and this, I believe, is incorrect: -r--r--r-- 1 root root 545 2010-11-20 18:49 /usr/lib/perl5/site_perl/5.10.1/i486-linux-thread-multi/Bundle/DBD/Pg.pm My minimal understanding is that the bundle includes perl modules for other database backends in addition to postgres. The only other dbms I use here is sqlite and that's not with any applications written in perl. So, am I correct is assuming it is safe to delete the Bundle directory and see if that resolves the problem?
You really have no client PC where you could set up a virtual server until your server is working again?
The only extra (working) computer is my older Sony Vaio notebook. Thanks, Rich _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
