On Dec 6, 3:18 am, "Uros Trebec" <[EMAIL PROTECTED]> wrote:
I am sorry to report that this method does NOT work on my
machine/account. I've tried different users (on the same machine) and
it does not work. Symptoms are the same.
Hey,
I've run into next-level 500 Internal Server Error
I am sorry to report that this method does NOT work on my
machine/account. I've tried different users (on the same machine) and
it does not work. Symptoms are the same.
I guess it's just my machine the one that is F00! And they refuse to
move my account to another one. :(
Anyone knows about any
Mike,
I was experiencing the same problems: incomplete headers and timeouts.
I did a simple trick that made my Django application run smoothly.
Perhaps you can try the same thing (it requires simple changes). I
described it on my blog:
Uros Trebec wrote:
> On Nov 27, 6:55 pm, "Uros Trebec" <[EMAIL PROTECTED]> wrote:
>
>> ATM, if I go to "http://localhost:8484/django.fcgi; I only get "403
>> Forbidden" response.
>
> OK, nevermind... I had to run "django-fcgi.py" too.
> http://manuals.textdrive.com/read/book/15
>
>> Now, how
On Nov 27, 6:55 pm, "Uros Trebec" <[EMAIL PROTECTED]> wrote:
> ATM, if I go to "http://localhost:8484/django.fcgi; I only get "403
> Forbidden" response.
OK, nevermind... I had to run "django-fcgi.py" too.
http://manuals.textdrive.com/read/book/15
> Now, how do I get Apache to redirect all
On 11/27/06, Gábor Farkas <[EMAIL PROTECTED]> wrote:
> >> If anyone has questions about how to do this let me know.
> >
> >
> > I for one, would VERY MUCH like to know how to do that.
> >
> > My django app has a downtime of 2 weeks now, because of the "incomplete
> > headers" :(
>
> and btw. are
I think I have a solution. It's not great but it will have to do while
I stay with Dreamhost (or until Dreamhost has formal Django support).
Apache answers the requests, passes them on to lighttpd running on a
different port which then talks to fcgi. This gives me full control
over the whole
On 19 Nov 2006, at 05:35, coulix wrote:
> mikeb i have the same problem it takes few minutes to come back and i
> see a lot of python process waiting for whatever.
> kill kill all ect have no effects.
> But once it runs its all good.
I have never found that the "touching" thing ever worked, but
mikeb i have the same problem it takes few minutes to come back and i
see a lot of python process waiting for whatever.
kill kill all ect have no effects.
But once it runs its all good.
mikeb wrote:
> I just did that. Thanks for the pointer :)
>
> On Nov 18, 6:08 pm, "chasfs" <[EMAIL
I just did that. Thanks for the pointer :)
On Nov 18, 6:08 pm, "chasfs" <[EMAIL PROTECTED]> wrote:
> Hi Mike,
> Sorry I can't help you directly. Have you voted for Dreamhost
> feature:
>
> 2005-07-25 New FeaturesAdd support for Django (a python
> web-development framework).
>
>
Hi Mike,
Sorry I can't help you directly. Have you voted for Dreamhost
feature:
2005-07-25 New FeaturesAdd support for Django (a python
web-development framework).
You vote on http://panel.dreamhost.com, click on Home and then
Suggestions and then scroll down or search for Django.
I'm on dreamhost, which provides FastCgi but not mod_python. FastCGI
has always been flaky there, where when I touch my django.fcgi file
django sometimes takes a few minutes to come back. kill, killall, kill
-9, kill -USR1 etc doesn't help.
Lately it has gotten much worse. Whenever I touch
12 matches
Mail list logo
