Apache timeout preventing long Sequest searches - fixed

[Kristian]

Hey all-

I've seen this issue addressed in a few different threads, but I
thought I'd add my experience here.

I run Sequest searches on a Windows machine with TPP 4.2. I was
having a problem with the GUI stalling out after only completing three
or four of the searches I had queued up (that is, after about 5 hours
of searching), a problem I never had with the Cygwin-based TPP.

Jimmy advised me to look at the httpd.conf file in Apache
(Start-->Programs-->Apache HTTP Server 2.2-->Configure Apache Server--
>Edit the Apache httpd.conf Configuration File).

Down near the very bottom of the file were the lines
# Add 5-hour timeout
Timeout 18000

I changed the timeout to 360000 (100 hours) and now I can have
searches running all weekend without stalling. Thanks, Jimmy!

Do any of the developers know if setting "Timeout 0" or just deleting
that line will eliminate the timeout completely?

[Joe Slagel]

Hi Kristian,

Deleting the line will result in Apache using the default value of 300 seconds for the timeout.  Generally a good idea to set this value to 0 (no timeout), or to a too large value as it can tie up computing resources and potentially lock out users from accessing the web server.  But in your case where there is only a single user accessing the server it should be fine.

-Joe

--
Joe Slagel
Institute for Systems Biology
jsl...@systemsbiology.org

[Eileen Yue]

Hello:

I tried to covert my raw file to mzxml file but I got the failed information in each time. Is anything wrong or some configuration that I need set?

 

Thanks

[Kristian]

Do you have XCalibur installed on the machine? You have to have a
licensed version of Thermo's software installed on the machine you try
to convert on (something about their .dll libraries).

[Kristian]

Setting the time out to 0 causes the TPP to become unusable. Setting
a ridiculously large timeout works just fine.

On Jul 22, 12:52 pm, Joe Slagel <jsla...@systemsbiology.org> wrote:
> Hi Kristian,
>
> Deleting the line will result in Apache using the default value of 300
> seconds for the timeout.  Generally a good idea to set this value to 0 (no
> timeout), or to a too large value as it can tie up computing resources and
> potentially lock out users from accessing the web server.  But in your case
> where there is only a single user accessing the server it should be fine.
>
> -Joe
>

> On Wed, Jul 22, 2009 at 10:16 AM, Kristian <kristian.swearin...@gmail.com>wrote:
>
>
>
>
>
>
>
> > Hey all-
>
> > I've seen this issue addressed in a few different threads, but I
> > thought I'd add my experience here.
>
> > I run Sequest searches on a Windows machine with TPP 4.2.  I was
> > having a problem with the GUI stalling out after only completing three
> > or four of the searches I had queued up (that is, after about 5 hours
> > of searching), a problem I never had with the Cygwin-based TPP.
>
> > Jimmy advised me to look at the httpd.conf file in Apache
> > (Start-->Programs-->Apache HTTP Server 2.2-->Configure Apache Server--
> > >Edit the Apache httpd.conf Configuration File).
>
> > Down near the very bottom of the file were the lines
> >     # Add 5-hour timeout
> >     Timeout 18000
>
> > I changed the timeout to 360000 (100 hours) and now I can have
> > searches running all weekend without stalling.  Thanks, Jimmy!
>
> > Do any of the developers know if setting "Timeout 0" or just deleting
> > that line will eliminate the timeout completely?
>
> --
> Joe Slagel
> Institute for Systems Biology

> jsla...@systemsbiology.org- Hide quoted text -
>
> - Show quoted text -