Re: [cobalt-users] WARN - handler "cgi-wrapper" not found for ...

[flash22@xxxxxxx]

On Fri, 25 Jan 2002, Fred McKinnon wrote:

> Hello everyone -
> I've spent several days this week (and over the last
> months, at random) searching the net and the Cobalt
> archives as to the "cgi-wrapper" handler not found
> warning that shows up in my "log files".  
> 
> I've understood that the error message is only a
> "warning", and I understand the problem in Perl that
> creates this warning . . but

Hmm, then you read something into something that isn't there, because it
has nothing to do with perl ;P

And in any case you are looking for the right answer to the wrong
problem..
> 
> The perl scripts on my RaQ3 are opertating at
> UNACCEPTABLE speed - for example, visit
> http://www.hppchristianhosting.com/consultation.html
> and submit this simple formmail.pl script (I've

Man are you gonna get spam....

Try searching the archives for what the problem is, and you will likely
find that once a week someone asks why form to mail scripts take forever
to post, and you will usually see someone patiently explain for the
hundredth time that this is a dns issue, either your dns doesn't work
right, or you are trying to send to a domain that's doesn't really exist
relative to your machiens domain name..

> upgraded the FormMail to version 1.9 due to hackers) .

About time, that exploit is only a year and a half old ;P

> Sometimes, it only takes a second - othertimes, it
> takes 30-45 seconds, or more!  

login via ssh (or telnet if you must) , send mail using the command line
mail program, see how long it takes....if it's slow, you can start from
that point...

> Regardless of how long it takes, I usually see that
> "WARN - Handler "cgi-wrapper" not found for
> /home/sites/web/cgi-bin/formmail.pl" in the

That is totally unrelated, it's an apache issue for cgi's , it's harmless,
tho annoying, the archives do explain how to work around it if it really
bugs you, but i wouldn't bother unless you get so much traffic it's
impacting your log files.

> I don't think that it's "overload" on Perl or too high
> a demand - there are only about 30 domains on this,
> and they are pretty "inactive", "stagnant" sites, if
> you know what I mean.

Not really, how much stuff is lying around on the disk really says nothing
about how busy the machine is, what's the load averate? memory
usage? those are the things you should normally ask when something is slow
;P

But that's not your problem, it's dns , take it on faith ;P

> 
> Resolutions?  I've tried to edit the access.conf file,
> as mentioned in the archives, and couldn't restart
> httpd until I took that edit out.  I've disabled CGI

That more or less tells me you shouldn't play with the conf files ;P

Seriously, read the apache docs before you play there, munging your access
file is really really dangerous, you will give the haqqers a field day if
you botch it ;P

> for the virtual site(s), and then re-enabled CGI
> again.  Of course, I've restarted the server, etc.

It's not broken , restarting it all day won't fix it ;)
It's not windows, restarting it all day won't fix it ;)

gsh