This script should do sql things. After processing sql thing, it shoulld print
some output. Now sql thing is correct because i can see that the data was
in database, but output got this message. So i don't think that DB connection
is timing out. Thanks for your reply
"Erich L. Markert" wrote:
> One other thing... Make sure your DB connections are timing out.
>
> Blue wrote:
> >
> > On Wed, 21 Jun 2000, darren chamberlain wrote:
> >
> > > The problem seems to arise when your handler returns something (a status
> > > code) but hasn't send any data. Turning off buffering ($|) will only help
> > > if you actually send something. Try telnetting to port 80 on the web server
> > > and issue some HTTP commands directly, and see what the response is; that
> > > might give you some insight.
> > >
> > > I am always careful to not call die or return until I have sent the header,
> > > since that can cause the situation you are seeing.
> >
> > ah, good call, darren. the other reason i've seen this happen is plain ol'
> > failure of the script to execute, for whatever reason. tailing the error
> > log or running the script manually is a good way to check for that.
> >
> > when this question first came up, i checked all the FAQS i could find to
> > see if there was somewhere i could point the poster. does anyone know of a
> > comprehensive addressing of perl/mod_perl cgi errors on the net?
> >
> > danke,
> >
> > --
> > Blue Lang Unix Systems Admin
> > QSP, Inc., 3200 Atlantic Ave, Ste 100, Raleigh, NC, 27604
> > Home: 919 835 1540 Work: 919 875 6994 Fax: 919 872 4015
>
> --
> __________________________________________________________
> Mr. Erich L. Markert [EMAIL PROTECTED]
> Computer Learning Center TEL (914)422-4328
> Pace University
> 1 Martine Ave
> White Plains, New York 10606-1932
>
> Those who do not understand Unix are condemned to reinvent it, poorly.
> -- Henry Spencer
