Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Louis wrote: The script can be also be executed from the command line. It can take anywhere between 2 to 3 hrs to complete. So does this mean that I cannot get it to run via browser ? What about parsing the call via LWP ? If the browser times out would the LWP url called still run anyway ? Louis. Not sure if this is still an issue, but I doubt you'd get a web server/browser combination to control a script that runs for 2-3 hrs. What you'd be better of doing is something like modifying the script to output to a plain text file (for example) and then initiate it in the background from a web-based page. The returned page from the initiating page then polls the server every 5, 10, or whatever minutes to see if it has finished and displays any results. Did that make any sense? Not sure if this will do what you want Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Hi Phil: Thanks for the suggestion. I am looking at a way to deal with this. But I want to see if I understood you here. Source : The script that runs for 2-3 hrs; Caller : Initiates Source, and polls every so and so and update may be a progress window that the user sees. So then to start off with, Caller starts off with an LWP on Source. It sounds like with this approach Source has to regularly send something back to Caller , and not wait till the end (2 - 3 hrs). But when u say polls the server every so and so what do u mean here ? The Caller if server is in Sussex mode does not know process ids etc.. (not su here). Can you please clarify here ? I will look further into this as well. Thanks Louis. -Original Message- From: Phil Scarratt [mailto:[EMAIL PROTECTED] Sent: Friday, 15 October 2004 16:37 To: Louis Cc: [EMAIL PROTECTED] Subject: Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Louis wrote: The script can be also be executed from the command line. It can take anywhere between 2 to 3 hrs to complete. So does this mean that I cannot get it to run via browser ? What about parsing the call via LWP ? If the browser times out would the LWP url called still run anyway ? Louis. Not sure if this is still an issue, but I doubt you'd get a web server/browser combination to control a script that runs for 2-3 hrs. What you'd be better of doing is something like modifying the script to output to a plain text file (for example) and then initiate it in the background from a web-based page. The returned page from the initiating page then polls the server every 5, 10, or whatever minutes to see if it has finished and displays any results. Did that make any sense? Not sure if this will do what you want Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
I think what he ment is that: 1. Access http://initiate-2-hour-process.cgi This runs the script which writes to an HTML file and returns an HTTP header with redirects the browser to another URL. The script forks into the background so the parent returns the HTTP redirect (if evrything startted fine) and the son runs the long-term process whic writes to poll-the-html-file.html 2. The browser goes to the redirected URL: http://poll-the-html-file.html This is the file being generated by the 2 hour process child. Its content can tell the browser to come back and re-fetch the file every few seconds/minutes. In addition, it content might show progress like time of last update and number of records processed so far and such. Does that make better sense? Cheers, --Amos Louis wrote: Hi Phil: Thanks for the suggestion. I am looking at a way to deal with this. But I want to see if I understood you here. Source : The script that runs for 2-3 hrs; Caller : Initiates Source, and polls every so and so and update may be a progress window that the user sees. So then to start off with, Caller starts off with an LWP on Source. It sounds like with this approach Source has to regularly send something back to Caller , and not wait till the end (2 - 3 hrs). But when u say polls the server every so and so what do u mean here ? The Caller if server is in Sussex mode does not know process ids etc.. (not su here). Can you please clarify here ? I will look further into this as well. Thanks Louis. -Original Message- From: Phil Scarratt [mailto:[EMAIL PROTECTED] Sent: Friday, 15 October 2004 16:37 To: Louis Cc: [EMAIL PROTECTED] Subject: Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Louis wrote: The script can be also be executed from the command line. It can take anywhere between 2 to 3 hrs to complete. So does this mean that I cannot get it to run via browser ? What about parsing the call via LWP ? If the browser times out would the LWP url called still run anyway ? Louis. Not sure if this is still an issue, but I doubt you'd get a web server/browser combination to control a script that runs for 2-3 hrs. What you'd be better of doing is something like modifying the script to output to a plain text file (for example) and then initiate it in the background from a web-based page. The returned page from the initiating page then polls the server every 5, 10, or whatever minutes to see if it has finished and displays any results. Did that make any sense? Not sure if this will do what you want Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
[EMAIL PROTECTED] wrote: I think what he ment is that: 1. Access http://initiate-2-hour-process.cgi This runs the script which writes to an HTML file and returns an HTTP header with redirects the browser to another URL. The script forks into the background so the parent returns the HTTP redirect (if evrything startted fine) and the son runs the long-term process whic writes to poll-the-html-file.html 2. The browser goes to the redirected URL: http://poll-the-html-file.html This is the file being generated by the 2 hour process child. Its content can tell the browser to come back and re-fetch the file every few seconds/minutes. In addition, it content might show progress like time of last update and number of records processed so far and such. Does that make better sense? Cheers, --Amos This is what i meant Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Title: Message The script can be also be executed from the command line. It can take anywhere between 2 to 3 hrs to complete. So does this mean that I cannot get it to run via browser ? What about parsing the call via LWP ? If the browser times out would the LWP url called still run anyway ? Louis. -Original Message-From: Roger Barnes [mailto:[EMAIL PROTECTED] Sent: Wednesday, 13 October 2004 09:06To: LouisSubject: RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Assuming your web browser is apache, I believe there is a Timeout parameter set in the httpd.conf file. Keep in mind that the problem may be the browser timing out, and any web page request that runs for more than a minute should really be optimised or delivered in a different way. - R From: Louis [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 October 2004 8:21 PMTo: Roger BarnesCc: [EMAIL PROTECTED]Subject: RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Hi Roger: The browser is Internet Explorer. Red hat Linux 7.3 The script runs on the web server and I have root access for it. Where do I check timeouts on the web server for cgi requests ? Thanks Louis. -Original Message-From: Roger Barnes [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 October 2004 09:31To: LouisSubject: RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! What browser, what server, what linux (trying to keep it on topic)? Are you running the script locally or through a web server? If web server, is the web server configured to time out CGI requests? If you are not the system administrator, have you contacted them? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LouisSent: Monday, 11 October 2004 8:27 PMTo: [EMAIL PROTECTED]Subject: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Hi Sluggers: When I call a script via the browser that takes some times to run I get this error from the browser and it stops the script. Server Error The following error occurred: [code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator. Please contact the administrator How can I deal with this to get the script to run right to the end ? Thanks. Louis. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Title: Message Hi Roger: The browser is Internet Explorer. Red hat Linux 7.3 The script runs on the web server and I have root access for it. Where do I check timeouts on the web server for cgi requests ? Thanks Louis. -Original Message-From: Roger Barnes [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 October 2004 09:31To: LouisSubject: RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! What browser, what server, what linux (trying to keep it on topic)? Are you running the script locally or through a web server? If web server, is the web server configured to time out CGI requests? If you are not the system administrator, have you contacted them? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LouisSent: Monday, 11 October 2004 8:27 PMTo: [EMAIL PROTECTED]Subject: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Hi Sluggers: When I call a script via the browser that takes some times to run I get this error from the browser and it stops the script. Server Error The following error occurred: [code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator. Please contact the administrator How can I deal with this to get the script to run right to the end ? Thanks. Louis. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Hi Phil: Script is written in Perl. Yes server is under my control. But if the server was not under my control how do I deal with this with perl scripts ? And the fact that it's under my control how do I Increase the timeout requests ? I am on red hat 7.3. Thanks Louis. -Original Message- From: Phil Scarratt [mailto:[EMAIL PROTECTED] Sent: Tuesday, 12 October 2004 09:35 To: Louis Cc: [EMAIL PROTECTED] Subject: Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE ! Louis wrote: Hi Sluggers: When I call a script via the browser that takes some times to run I get this error from the browser and it stops the script. Server Error The following error occurred: [code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator. Please contact the administrator How can I deal with this to get the script to run right to the end ? Thanks. Louis. What is the script written in? Is the server under you're control? I'm guessing not. If it's PHP then the PHP docs have some tips on getting around long run-time scripts. Push output to the client earlier or something like that Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Louis wrote: Hi Phil: Script is written in Perl. Yes server is under my control. But if the server was not under my control how do I deal with this with perl scripts ? And the fact that it's under my control how do I Increase the timeout requests ? I am on red hat 7.3. Thanks Louis. I'm not aware of any timeout limits on Perl CGI under Apache 1.3 (I can't remember specificaly what RH7.3 bundled with it but I'm guessing Apache 1.3) - not that that means a lot. There's a general timeout of 300 seconds set on Apache but not sure if that would affect the CGI execution time. I would start by looking in the access and error logs of the web server. Take a look in /var/log/httpd (may also be in /etc/httpd/ somewhere - it's been awhile since RH7.3 and things may have moved since then). Try running the script in a shell...how long does it take? Sorry can't be of more help... Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Title: Message Hi Sluggers: When I call a script via the browser that takes some times to run I get this error from the browser and it stops the script. Server Error The following error occurred: [code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator. Please contact the administrator How can I deal with this to get the script to run right to the end ? Thanks. Louis. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Scirpt Via browser Gives code=SERVER_RESPONSE_CLOSE !
Louis wrote: Hi Sluggers: When I call a script via the browser that takes some times to run I get this error from the browser and it stops the script. Server Error The following error occurred: [code=SERVER_RESPONSE_CLOSE] The server closed the connection while reading the response. Contact your system administrator. Please contact the administrator How can I deal with this to get the script to run right to the end ? Thanks. Louis. What is the script written in? Is the server under you're control? I'm guessing not. If it's PHP then the PHP docs have some tips on getting around long run-time scripts. Push output to the client earlier or something like that Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
