Mailing List Archive: Cherokee: users

504 Gateway Timeout

Index | Next | Previous | View Threaded

gour at gour-nitai

Jul 15, 2009, 6:50 AM

Post #1 of 7 (1038 views)
Permalink

504 Gateway Timeout

Hi!

I'm trying to access Cherokee's web interface from my laptop, but no
matter what I try I get: 504 Gateway Timeout.

On #cherokee, I was told that the issue is with old python - the server
has Debian Lenny with 2.4.4. but I've installed 2.5 under my account and
still have the same problem.

I see there is the following ticket

http://code.google.com/p/cherokee/issues/detail?id=445

but there is no workaround?

Anyone can shed some more light to it?

Sincerely,
Gour

--

Gour | Hlapicina, Croatia | GPG key: F96FF5F6
----------------------------------------------------------------

gour at gour-nitai

Jul 19, 2009, 2:19 AM

Post #2 of 7 (985 views)
Permalink

Re: 504 Gateway Timeout (SOLVED) [In reply to]

>>>>> "Gour" == Gour <gour [at] gour-nitai> writes:

Gour> I see there is the following ticket

Gour> http://code.google.com/p/cherokee/issues/detail?id=445

Gour> but there is no workaround?

Well, after reporting the issue on #cherokee, Alvaro jumped in and
provided patch which fix specific problem for my setup.

It will be, afaict, included in 0.99.21 release.

Cherokee development rocks (as well as the server itself)!!

Sincerely,
Gour

--

Gour (Gmail) | Hlapičina, Croatia | GPG key: F96FF5F6
---------------------------------------------------------------------------

alvaro at alobbs

Jul 19, 2009, 3:30 AM

Post #3 of 7 (977 views)
Permalink

Re: 504 Gateway Timeout (SOLVED) [In reply to]

On 19-jul-09, at 11:19, Gour wrote:

> Gour> I see there is the following ticket
> Gour> http://code.google.com/p/cherokee/issues/detail?id=445
> Gour> but there is no workaround?
>
> Well, after reporting the issue on #cherokee, Alvaro jumped in and
> provided patch which fix specific problem for my setup.
>
> It will be, afaict, included in 0.99.21 release.

Thank _you_ for reporting and following up on this issue. Your help
has been very valuable. :-)

--
Greetings, alo
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

alvaro at octality

Jun 26, 2010, 1:44 PM

Post #4 of 7 (695 views)
Permalink

Re: 504 Gateway Timeout [In reply to]

Hey pigmej,

On 26/06/2010, at 20:02, Jędrzej Nowak wrote:

> Alvaro I have the same problem, so 100% problem is inside admin.
> It usually uses ~100% of CPU. So that's definitelly the problem.

That has nothing to do with the previous problem. Patrick's system is plain broken, that's the issue. I guess I made perfectly clear that gettext is required. But, again, the only way to improve Cherokee to run even in such a dysfunctional environment would be to get the Python back-trace I asked for. Instead, I got a bunch of mails with no information and way too many exclamation marks.

> I have no idea now what's going on, but ...

We can get your CPU hogging issue fixed for sure. Please, drop me a line next time we meet at IRC, and we'll investigate what's going on.

Cheers!

> On Sat, Jun 26, 2010 at 7:17 PM, <Patrick_4321 [at] gmx> wrote:
>> to your information Alvaro Lopez,
>>
>> I have readed those documents and still have that problems.
>> Even after using the configure command I get
>> the recommendation on commandline I should use an
>> option --enable-nls but this option is stated nowhere !
>>
>> Then what should I with the docu cherokee-admin if I
>> get the Error Message
>> Gateway-Timeout before I even get the chance to
>> come to the admin screen stated on your documentation ?!
>>
>> For your info admin tool is still not running
>> says Gateway-Timeout !
>>
>> I ask myself how do you want to compete with Apache if
>> the simplest installation is such an dificult
>> thing ?
>>
>>
>>
>> -------- Original-Nachricht --------
>>> Datum: Sat, 26 Jun 2010 12:29:29 +0200
>>> Von: Alvaro Lopez Ortega <alvaro [at] octality>
>>> An: Patrick_4321 [at] gmx
>>> CC: cherokee [at] lists
>>> Betreff: Re: [Cherokee] 504 Gateway Timeout
>>
>>> On 26/06/2010, at 00:05, Patrick_4321 [at] gmx wrote:
>>>
>>>> Hello together seems to me
>>>> I got One step further.
>>>
>>> Yeah, it'd have been much easier if you read the documentation (that we
>>> took care to write and make available): http://www.cherokee-project.com/doc/
>>> . Specially the following entries:
>>>
>>> http://www.cherokee-project.com/doc/basics_installation_unix.html
>>> http://www.cherokee-project.com/doc/bundle_cherokee-admin.html
>>> http://www.cherokee-project.com/doc/bundle_cherokee.html
>>>
>>>> I see now the Login screen on 127.0.0.1:9090
>>>> but after login I get the Error message
>>>>
>>>> 504 Gateway Timeout
>>>
>>> Tenth time: If you execute "cherokee-admin -x" the error will be printed
>>> in the console.
>>>
>>> --
>>> Octality
>>> http://www.octality.com/
>>
>> --
>> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
>> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>> _______________________________________________
>> Cherokee mailing list
>> Cherokee [at] lists
>> http://lists.octality.com/listinfo/cherokee
>>
> _______________________________________________
> Cherokee mailing list
> Cherokee [at] lists
> http://lists.octality.com/listinfo/cherokee

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

me at pigmej

Jun 26, 2010, 2:57 PM

Post #5 of 7 (704 views)
Permalink

Re: 504 Gateway Timeout [In reply to]

Hmm....

Sorry , I haven't read the whole Patrick's posts...
Pozdrawiam
Jędrzej Nowak

2010/6/26 Alvaro Lopez Ortega <alvaro [at] octality>:
> Hey pigmej,
>
> On 26/06/2010, at 20:02, Jędrzej Nowak wrote:
>
>> Alvaro I have the same problem, so 100% problem is inside admin.
>> It usually uses ~100% of CPU. So that's definitelly the problem.
>
> That has nothing to do with the previous problem. Patrick's system is plain broken, that's the issue. I guess I made perfectly clear that gettext is required. But, again, the only way to improve Cherokee to run even in such a dysfunctional environment would be to get the Python back-trace I asked for. Instead, I got a bunch of mails with no information and way too many exclamation marks.
>
>> I have no idea now what's going on, but ...
>
> We can get your CPU hogging issue fixed for sure. Please, drop me a line next time we meet at IRC, and we'll investigate what's going on.
>
> Cheers!
>
>
>> On Sat, Jun 26, 2010 at 7:17 PM, <Patrick_4321 [at] gmx> wrote:
>>> to your information Alvaro Lopez,
>>>
>>> I have readed those documents and still have that problems.
>>> Even after using the configure command I get
>>> the recommendation on commandline I should use an
>>> option --enable-nls but this option is stated nowhere !
>>>
>>> Then what should I with the docu cherokee-admin if I
>>> get the Error Message
>>> Gateway-Timeout before I even get the chance to
>>> come to the admin screen stated on your documentation ?!
>>>
>>> For your info admin tool is still not running
>>> says Gateway-Timeout !
>>>
>>> I ask myself how do you want to compete with Apache if
>>> the simplest installation is such an dificult
>>> thing ?
>>>
>>>
>>>
>>> -------- Original-Nachricht --------
>>>> Datum: Sat, 26 Jun 2010 12:29:29 +0200
>>>> Von: Alvaro Lopez Ortega <alvaro [at] octality>
>>>> An: Patrick_4321 [at] gmx
>>>> CC: cherokee [at] lists
>>>> Betreff: Re: [Cherokee] 504 Gateway Timeout
>>>
>>>> On 26/06/2010, at 00:05, Patrick_4321 [at] gmx wrote:
>>>>
>>>>> Hello together seems to me
>>>>> I got One step further.
>>>>
>>>> Yeah, it'd have been much easier if you read the documentation (that we
>>>> took care to write and make available): http://www.cherokee-project.com/doc/
>>>> . Specially the following entries:
>>>>
>>>> http://www.cherokee-project.com/doc/basics_installation_unix.html
>>>> http://www.cherokee-project.com/doc/bundle_cherokee-admin.html
>>>> http://www.cherokee-project.com/doc/bundle_cherokee.html
>>>>
>>>>> I see now the Login screen on 127.0.0.1:9090
>>>>> but after login I get the Error message
>>>>>
>>>>> 504 Gateway Timeout
>>>>
>>>> Tenth time: If you execute "cherokee-admin -x" the error will be printed
>>>> in the console.
>>>>
>>>> --
>>>> Octality
>>>> http://www.octality.com/
>>>
>>> --
>>> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
>>> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>>> _______________________________________________
>>> Cherokee mailing list
>>> Cherokee [at] lists
>>> http://lists.octality.com/listinfo/cherokee
>>>
>> _______________________________________________
>> Cherokee mailing list
>> Cherokee [at] lists
>> http://lists.octality.com/listinfo/cherokee
>
> --
> Octality
> http://www.octality.com/
>
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

js at yllq

Mar 19, 2012, 2:49 PM

Post #6 of 7 (405 views)
Permalink

Re: 504 Gateway Timeout [In reply to]

On Tue, 2012-03-13 at 19:51 -0700, Leonel Nunez wrote:
> Hello:
>
> I have a python app on with an Information Source. That information source
> is using localhost:9999
>
> This app needs to wait for a sync process, this process is taking sometime
> to complete, that time it's ok.
>
> I guess is taking more time to complete and cherokee returns 504 Gateway
> Timeout
>
> Searched the docs and the cherokee admin how to increase that timeout but
> found nothing about it.
>
> Is there a way to increase the timeout ?

I usually increase spawning timeout on source...

--
Mateusz Pawlowski <js [at] yllq>

Attachments:

smime.p7s (3.89 KB)

listas at enelserver

Mar 25, 2012, 11:47 AM

Post #7 of 7 (404 views)
Permalink

Re: 504 Gateway Timeout [In reply to]

> On Tue, 2012-03-13 at 19:51 -0700, Leonel Nunez wrote:
>> Hello:
>>
>> I have a python app on with an Information Source. That information
>> source
>> is using localhost:9999
>>
>> This app needs to wait for a sync process, this process is taking
>> sometime
>> to complete, that time it's ok.
>>
>> I guess is taking more time to complete and cherokee returns 504 Gateway
>> Timeout
>>
>> Searched the docs and the cherokee admin how to increase that timeout
>> but
>> found nothing about it.
>>
>> Is there a way to increase the timeout ?
>
>
> I usually increase spawning timeout on source...
>
>
> --
> Mateusz Pawlowski <js [at] yllq>
>
>

Thank you .. I believed that timeout was only for a new interpreter in
case the information source died

Leonel

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads