Hi,
I'm using libapreq to do http file uploads, works just fine on my
Debian/unstable desktop system, running Apache 1.3.14, mod_perl 1.25.
When I use the exact same code to do the same on my RedHat 7.0 server,
running Apache 1.3.14, mod_perl 1.24 - the access_log shows that the
POST occurs, but
On Mon, May 21, 2001 at 01:35:11AM -0700, Thomas K. Burkholder wrote:
> Hi,
>
> I'm using libapreq to do http file uploads, works just fine on my
> Debian/unstable desktop system, running Apache 1.3.14, mod_perl 1.25.
>
<...>
>
> The HTML looks something like this:
>
>
>
>
> ACTION="area
--
mod_perl digest
May 13, 2001 - May 19, 2001
--
Recent happenings in the mod_perl world...
Features
o m
On Fri, 18 May 2001 23:28:06 -0400, Neil Conway wrote:
> I'd like to be able to use something similar to CGI.pm's HTML
> generation methods in a PerlHandler I'm writing. Since I'm
> not ever going to be using CGI directly (and also, the HTML
> I'm doing is pretty simple), CGI.pm seems like overkil
On Mon, 21 May 2001, Geoffrey Young wrote:
> --
>
> mod_perl digest
>
> May 13, 2001 - May 19, 2001
>
> --
[ .
We've just upgraded a SunOS machine from Apache 1.3.9 + mod_perl 1.21
(dynamically linked) to Apache 1.3.19 + mod_perl 1.25 (statically
linked). I have a CGI/Perl script, handled as normal by perl-script
and Apache::Registry. Now, this CGI script sometimes returns a page
with status something li
You are totally correct; you've saved me the cost of a new monitor, which
was about to receive my forehead through it if I stared at this any longer.
Can't believe I made such a silly error - I have other forms where I
deliberately used the hidden field in exactly the way you point out, to
avoid
This is driving me crazy... is there anything special I need to do when
using DBI (DBD::MySQL) with mod_perl. A script that works just fine sans
mod_perl dies with error 500 (Internal Server Error) when mod_perl is
enabled for that file type:
Web Server: Apache/1.3.19(Win32) mod_perl/1.24_01 o
"Jonathan M. Hollin" wrote:
> This is driving me crazy... is there anything special I need to do when
> using DBI (DBD::MySQL) with mod_perl. A script that works just fine sans
> mod_perl dies with error 500 (Internal Server Error) when mod_perl is
> enabled for that file type:
>
> Web Server
Hmm... Tried that, it returns nothing!!! :-(
Kindest regards,
Jonathan M. Hollin
Digital-Word.com
:: "Jonathan M. Hollin" wrote:
::
:: > This is driving me crazy... is there anything special I need
:: to do when
:: > using DBI (DBD::MySQL) with mod_perl. A script that works
:: just fine sans
> A script that works just fine sans
> mod_perl dies with error 500 (Internal Server Error) when mod_perl is
> enabled for that file type:
This indicates that ~something~ should have gone to the error log. Can you
tell us what else is there?
Can you get a DB connection with regular CGI?
---
Ro
:: This indicates that ~something~ should have gone to the error
:: log. Can you tell us what else is there?
Nothing, except:
[Tue May 22 00:44:37 2001] nul: DBI->connect failed: Can't connect to MySQL
server on 'localhost' (10061) at e:/pad/htdocs/internet/system/frontpage.cgi
line 29
[Tue May
JH> If I comment out the DBI code the rest of the script works fine. I have
JH> test the MOD_PERL environment string and mod_perl is definitely running
JH> okay.
You have several pieces of mod_perl configuration. If you leave it all in
place, and try some mod_perl CGI without a DB connection, wh
:: You have several pieces of mod_perl configuration. If you leave it all in
:: place, and try some mod_perl CGI without a DB connection, what happens?
Everything works fine (tested several scripts yet and had no other
problems - none of the others use DBI though). I am also using CGI.pm in
the
[EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
>[EMAIL PROTECTED] (Mike Cameron) wrote:
>:: how bout adding a 'or die DBI->errstr' to the above line to find
>:: out whats
>:: happening.
>
>Hmm... Tried that, it returns nothing!!! :-(
This is suspicious. The connect() is definitely where the erro
Oh the connect is definitely where it's failing. If I comment that out then
everything works fine...
I'll try your code though - watch this space.
Kindest regards,
Jonathan M. Hollin
Digital-Word.com
:: >:: how bout adding a 'or die DBI->errstr' to the above line to find
:: >:: out whats
:: >
Hey Jon,
You sent this one straight to me...
- Original Message -
From: Jonathan M. Hollin <[EMAIL PROTECTED]>
JH> Yes I also have PHP4 installed and running properly (and am able to
connect
JH> to the MySQL server fine with PHP). I'll comment out the PHP code from
JH> httpd.config an
:: This is suspicious. The connect() is definitely where the error is
:: happening given what you wrote earlier. Try making sure, change it to:
::
:: use DBI();
:: $driver = "mysql";
:: $dsn = "DBI:$driver:database=shapeshifter;host=localhost";
:: $dbh = DBI->con
:: JH> Yes I also have PHP4 installed and running properly (and am able to
:: connect
:: JH> to the MySQL server fine with PHP). I'll comment out the
:: PHP code from
:: JH> httpd.config and see if that helps...
::
:: Cool, that could be it. If not, I'd get suspicious of anything
:: else that ca
JH> Yes I also have PHP4 installed and running properly (and am able
JH> to connect to the MySQL server fine with PHP).
Good, that establishes that your DB is working.
JH> Removed PHP from Apache, that didn't help.
JH> Nothing else is connecting to the MySQL server.
I've never used a non-*NIX
[EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
>:: This is suspicious. The connect() is definitely where the error is
>:: happening given what you wrote earlier. Try making sure, change it to:
>::
>:: use DBI();
>:: $driver = "mysql";
>:: $dsn = "DBI:$driver:database=shap
:: JH> Yes I also have PHP4 installed and running properly (and am able
:: JH> to connect to the MySQL server fine with PHP).
::
:: Good, that establishes that your DB is working.
Yes the database is working fine. Let me reiterate: DB is accessible via
mysqladmin; DB is accessible via PHP; DB i
:: What does 'failed' mean? What was the error? That's the point, you
:: have to see the particular error string, starting with "Error:", to find
:: out what's happening.
I appreciate what you were looking for Ken. But that's the point - I don't
get an error string. All I get is an "Internal
> I appreciate what you were looking for Ken. But that's the point - I don't
> get an error string. All I get is an "Internal Server Error".
>
Sorry if I'm pointing out the obvious, but that's what you usually see in
the browser. The real error message will be in your apache logs,
quite often
:: Sorry if I'm pointing out the obvious, but that's what you usually see in
:: the browser. The real error message will be in your apache logs,
:: quite often in /var/log/httpd/error_log, but defined in your apache
:: configuration.
I know Tom. I already posted the error log entry, but here goe
I see what Tom is saying. You said that you found this in your error log:
> [Tue May 22 01:39:47 2001] [error] DBI->connect failed: Can't connect to
> MySQL server on 'localhost' (10061) at
> e:/pad/htdocs/internet/system/frontpage.cgi line 33
But a previous message suggested trying to propogate
:: I see what Tom is saying. You said that you found this in your error log:
::
:: > [Tue May 22 01:39:47 2001] [error] DBI->connect failed: Can't
:: connect to
:: > MySQL server on 'localhost' (10061) at
:: > e:/pad/htdocs/internet/system/frontpage.cgi line 33
::
:: But a previous message suggest
[EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
>:: Tom is saying that your error message should actually include the string:
>:: 'Error: '. I'm wondering the same thing, what did ~that ~ error
>:: message say?
>
>That's my point. I DO have the "or die" code in my script - it hasn't
>changed the me
Okay...
Rebooting the computer made no difference whatsoever.
So I built a minimal script as follows:
#!perl
print ("Content-type: text/html\n\n");
use strict;
use vars qw($query $dsn $driver $db_username $db_password $dbh);
require 5.006; $| = 1; ($0 =~ m,(.*)/[^/]+,) && unshift (@INC, "$1"
:: Okay, then that's the problem. It's not running the script you think
:: it's running. If you don't see 'Error:' in the error log, then you
:: could change that script all day and your changes will never have any
:: effect.
But it is running the script I am requesting - I know this because w
> $db_username = "";
> $db_password = "";
> warn "Before DBI->connect(): [$$]";
> $dbh = DBI->connect($dsn, $db_username, $db_password, {'RaiseError' => 1})
> or die sprintf "Error: %s.\n", DBI->errstr;
You're probably not getting your error message because you have RaiseError on.
:: You're probably not getting your error message because you have
:: RaiseError on.
Have corrected that - but the results haven't changed in any way.
Kindest regards,
Jonathan M. Hollin
Digital-Word.com
OK, here's the relevant part of your conf:
# BEGIN MOD_PERL CONFIG
LoadModule perl_module modules/ApacheModulePerl
ScriptAlias /perl-bin/ "perl-bin/"
PerlSendHeader On
SetHandler perl-script
PerlHandler Apache::Registry
Options ExecCGI
Rodney,
:: I propose that you reduce it to:
::
:: # BEGIN MOD_PERL CONFIG
:: LoadModule perl_module modules/ApacheModulePerl
::
::
:: SetHandler perl-script
:: PerlHandler Apache::Registry
::
::
:: # END MOD_PERL CONFIG
::
:: You'll see that I'm using *.mpl. This wil
Incidentally, I am using the following module versions:
DBD-MySQL [1.2214];
DBI [1.13]
Does this have any bearing on my problem?
Kindest regards,
Jonathan M. Hollin
Digital-Word.com
LATEST NEWS: Digital-Word.com releases e-gateway v3.0. See:
http://e-gateway.1-1IT.Net/ for further details.
[EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
>I'm probably going to have to forfeit mod_perl after all. :-(
Okay, last idea: you say you can connect to mysql from the command line,
from regular CGI, and from PHP. I'm guessing that in all of those
situations, you're acting as the same user (win
:: Okay, last idea: you say you can connect to mysql from the command line,
:: from regular CGI, and from PHP. I'm guessing that in all of those
:: situations, you're acting as the same user (win2k user, not mysql user).
:: However, under mod_perl you'll be acting as whatever user your web
:: ser
[EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
>:: Okay, last idea: you say you can connect to mysql from the command line,
>:: from regular CGI, and from PHP. I'm guessing that in all of those
>:: situations, you're acting as the same user (win2k user, not mysql user).
>:: However, under mod_perl
Ken Williams wrote:
> [EMAIL PROTECTED] (Jonathan M. Hollin) wrote:
> >:: Okay, last idea: you say you can connect to mysql from the command line,
> >:: from regular CGI, and from PHP. I'm guessing that in all of those
> >:: situations, you're acting as the same user (win2k user, not mysql use
I know you all want me to go away, so I apologise for the noise. Anyway, at
http://perl.apache.org/guide/databases.html#Why_Relational_SQL_Databases
there is a reference to an "Apache::DBI" module. I DON'T have this module
installed - is this the reason why CGI connects work yet mod_perl request
On Tue, 22 May 2001, Jonathan M. Hollin wrote:
> I know you all want me to go away, so I apologise for the noise. Anyway, at
> http://perl.apache.org/guide/databases.html#Why_Relational_SQL_Databases
> there is a reference to an "Apache::DBI" module. I DON'T have this module
> installed - is th
"Jonathan M. Hollin" wrote:
> I know you all want me to go away, so I apologise for the noise. Anyway, at
> http://perl.apache.org/guide/databases.html#Why_Relational_SQL_Databases
> there is a reference to an "Apache::DBI" module. I DON'T have this module
> installed - is this the reason why
Hi,
This is a follow up of mails sent to this mailing
list last month.
We were benchmarking several db access methods and
comparing them with postgres.
Lots of people advised us to try pg 7.1 instead of
pg 6.5.3
This turns out to be good advice as regards
performance. (We would like to i
Hi,
These are my 5 cents to the problem :)
In the error log is a error code 10061 (Which stands for connection refused)
this means that the application cannot even open a connection to the mysql
server. Maybe you should also provide the DSN with a port number. Or try to
use 127.0.0.1 instead of
On Tue, 22 May 2001, Jonathan M. Hollin wrote:
> This is driving me crazy... is there anything special I need to do when
> using DBI (DBD::MySQL) with mod_perl. A script that works just fine sans
> mod_perl dies with error 500 (Internal Server Error) when mod_perl is
> enabled for that file typ
45 matches
Mail list logo
