[DBI script problem skipped]
> The error_log from Apache shows some problems, which *could* be related to
> mod_perl
>
> [Fri Dec 1 18:47:08 2000] [crit] (13)Permission denied: make_sock: could
> not bi
> nd to port 80
> [Fri Dec 1 18:56:06 2000] [crit] (13)Permission denied: make_sock: could
> not bi
> nd to port 80
> [Tue Dec 5 09:42:27 2000] [crit] (13)Permission denied: make_sock: could
> not bi
> nd to port 80
> [Tue Dec 5 09:42:31 2000] [crit] (13)Permission denied: make_sock: could
> not bi
> nd to port 80
Uhm, before we try to solve the problem in hand, I don't understand your
statement of Apache showing *some* problems. What port are you running
mod_perl server at? 80? do you run a single mod_perl server or is there a
front-end server?
Second, you should make your code more debug friendly. Replace:
$dbh = DBI->connect('dbi:mysql:vip;host=####', '###', '###');
with
$dbh = DBI->connect('dbi:mysql:vip;host=####', '###', '###')
or die $DBI::errstr;
what error do you get? You don't really need to trace to get the reason of
why the connect call fails.
(BTW, die $DBI::errstr; is in the DBI manpage)
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
