In short:
1.) I had the problem to get the "Setup of CGI.pm failed" error message
sometimes. I could not reproduce this error, no matter what i tried.
2.) So i wrote Gerald and asked him for help.
3.) His answer was that this happens if someone sends inco
ltipart() in CGI.pm called,
upload length 949716
> 10:30:30 - my logging in CGI.pm reports first file of batch started
> 10:31:58 - my logging in CGI.pm reports first file of batch completed
successfully
> 10:31:58 - my logging in CGI.pm reports second file of batch started
> 10:32:17 - S
part() in CGI.pm called, upload
length 949716
10:30:30 - my logging in CGI.pm reports first file of batch started
10:31:58 - my logging in CGI.pm reports first file of batch completed successfully
10:31:58 - my logging in CGI.pm reports second file of batch started
10:32:17 - Setup of CGI.pm fail
>
> > When CGI fails, does it contain any usefull information ?
>
> It's empty. Always.
>
ok, I just wanted to make sure it didn't get lost, because there was nothing
in the Embperl error message. So we have verified that CGI.pm really doesn't
set's $@
>
> Also the user often (but not always) ge
On Thu, Oct 04, 2001 at 09:07:40PM +0200, Gerald Richter wrote:
>
> Could you print out $@ directly after the
>
> eval { $cgi = new CGI } ;
> When CGI fails, does it contain any usefull information ?
It's empty. Always.
>
> In past sometimes it has helped to upgrade CGI.pm in such cases,
>
> Thanks Gerald - unfortunately I still don't know *WHY* CGI.pm dies -
> and I am lost about how to find out.
>
> I have put in a log line just after the eval to dump %ENV, but this
> does not look particularly unusual.
>
Could you print out $@ directly after the
eval { $cgi = new CGI } ;
>
> Nope, nothing except that line (and an email from the customer
complaining).
>
Does it normaly work ? Any chance to reproduce it ? If yes, does it only
occur with a special browser ?
> Anywhere I could put some code for extra logging?
>
You can take a look at the CGI.pm docu if there is any
On Wed, Aug 22, 2001 at 01:41:00PM +0200, Gerald Richter wrote:
>
>
> >
> > Any ideas as to where I might start looking for
> > what is causing this??
> >
>
> That means that "new CGI" returns undef. I guess that something with the
> fileupload goes wrong. Any additional error messages ?
>
No
> I am repeatedly getting the following messages in
> my server error log:
>
> [6432]ERR: 44: Line 1: Setup of CGI.pm failed:
>
> I'd guess that this is coming from Embperl,
Yes
>
> Any ideas as to where I might start looking for
> what is causing this??
>
I am repeatedly getting the following messages in
my server error log:
[6432]ERR: 44: Line 1: Setup of CGI.pm failed:
I'd guess that this is coming from Embperl, as Apache
puts in a date, time, and the file that generated
the error.
Any ideas as to where I might start looking for
wh
10 matches
Mail list logo
