-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
| (1) The failure via the mod_perl route (Apache::DBI not in use):
|
| DBI 1.605-ithread default trace level set to 0x0/15 (pid 27667) at
| Database.pm line 184 via Base.pm line 97
*| -> DBI->connect(dbi:Pg:dbname=contacts, ron, ****)
| -> DBI->install_driver(Pg) for linux perl=5.010000 pid=27667 ruid=1
| ...
*| <- $DBI::errstr= 'FATAL: Ident authentication failed for user "ron"'
| DBI connect('dbname=contacts','ron',...) failed: FATAL: Ident
| authentication failed for user "ron"
| DBI connect('dbname=contacts','ron',...) failed: FATAL: Ident
| authentication failed for user "ron"
| at /home/ron/perl.modules/Local-Contacts/lib/Local/Contacts/App/Database.pm
line 185
*| -> DBI->connect(, , ****)
| [Dispatch] ERROR: Can't connect to data source '' because I can't work
| out what driver to use (it doesn't seem to contain a 'dbi:driver:'
So it looks as though the first connect fails as it should, and throws an
exception (it's not clear what above is coming from trace, what from
stderr, might want to use DBI->trace(10, 'filename'). What's odd is
that second "DBI->connect(, , ****)" which seems to indicate that your
script is calling connect a second time, immediately after the first
one has failed. It does look as though DBI::errstr is being set, which
is good.
It might also help to see that portion of the script. Right now, it's
still to hard to tell if the second connect is by your script, by some
weird mod_perl interaction, or something else.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200809162152
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkjQYzEACgkQvJuQZxSWSsiPzwCgxuVaSUKBkmrjITD+8fniNKPM
j20AnA6u/X6ds1fSodyObCM8EUSn9FMa
=C3NQ
-----END PGP SIGNATURE-----
