On 10 December 2010 19:38, Haes <[email protected]> wrote:
> On Dec 9, 10:33 pm, Graham Dumpleton <[email protected]>
> wrote:
>> Do you schedule regular Apache restarts during the day, or do it
>> manually due to Apache configuration changes? Would any restarts
>> coincide with when you see the issue?
>
> No, there are no periodic Apache restarts going on. Besides that, the
> times of these log messages are completely random.
>
> Maybe playing with the mod_wsgi max-requests option would help?
The maximum-requests option on daemon mode processes shouldn't make a
difference.
Ideally you would never set maximum-requests option for a production system.
>> Are you using mod_ssl in Apache and accepting requests via HTTPS?
>
> Yes, there is also a HTTPS virtualhost defined, which is more or less
> used for the admin pages. But the requests that lead to these error
> messages where both from HTTP and HTTPS requests.
>
> Is there anything that should be taken care of when using HTTPS
> and mod_wsgi?
Because of issues caused by mod_ssl in some Apache versions, always
suggest people use latest Apache 2.X. I think the issues were fixed in
Apache 2.2.14 or 2.2.15. So, if using older Apache, you might be
encountering the problems which were caused by mod_ssl.
>> Other than that, that error can arise when HTTP client connection is
>> broken before complete response is returned. Usually this would with
>> daemon mode necessitate the response being quite large though.
>
> A "common" HTML page is served, not a large file download or
> something similar.
>
>> BTW, if all your Django instances are actually the same, you should
>> really force them to run in same sub interpreter, otherwise you could
>> be using up much more memory than you need based on your multiple
>> WSGIScriptAlias directives. Ie., try setting 'WSGIApplicationGroup
>> %{GLOBAL}'. This has nothing to do with your issue however.
>
> Thanks for the tip, actually there are about 7 Django instances and
> 4 WSGIApplicationGroups defined for them. I guess I'm going to
> clean up the wsgi configuration then.
You can only merge them if have exact same Django settings file. Also
possibly will only work if all in same virtual host as well.
Graham
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
