thank you for your prompt reply!
it is running in daemon mode as specified by the following two lines in the
site config:
WSGIDaemonProcess kutbill.com python-path=/var/www/kutbill/ processes=2
threads=20 display-name=%{GROUP}
WSGIProcessGroup kutbill.com
(btw, the host name (kutbill.com) does not match the machine on which this
daemon is running.)
ok, will try to upgrade mod_wsgi and try. do i need to upgrade apache as
well?
pls. advise.
On Monday, July 27, 2015 at 10:08:25 AM UTC+5:30, Graham Dumpleton wrote:
>
> What is the mod_wsgi configuration form the Apache configuration file
> which you are using? Are you using embedded mode or daemon mode?
>
> Version 4.3.0 of mod_wsgi is 15+ releases behind, so somewhat old.
>
> That you are using Apache 2.4.10 also concerns me, because if Debian back
> ported a specific CVE fix from Apache 2.4.11, then it can cause older
> mod_wsgi versions such as you are using to crash in certain circumstances.
>
> Ideally if you could update to the latest mod_wsgi version and see if that
> helps, would be best. If it still occurs in the latest version, then we can
> investigate further.
>
> Graham
>
> On 27 Jul 2015, at 1:44 pm, Deva P. Seetharam <[email protected]
> <javascript:>> wrote:
>
> hello
>
> we are running debian linux stable (Jessie) with apache 2.4.10 and
> mod_wsgi 4.3.0-1 on a x86_64 machine.
> the list of modules as reported by apachectl -M are:
> Loaded Modules:
> core_module (static)
> so_module (static)
> watchdog_module (static)
> http_module (static)
> log_config_module (static)
> logio_module (static)
> version_module (static)
> unixd_module (static)
> access_compat_module (shared)
> alias_module (shared)
> auth_basic_module (shared)
> authn_core_module (shared)
> authn_file_module (shared)
> authz_core_module (shared)
> authz_host_module (shared)
> authz_user_module (shared)
> autoindex_module (shared)
> cgi_module (shared)
> deflate_module (shared)
> dir_module (shared)
> env_module (shared)
> filter_module (shared)
> mime_module (shared)
> mpm_worker_module (shared)
> negotiation_module (shared)
> perl_module (shared)
> rewrite_module (shared)
> setenvif_module (shared)
> socache_shmcb_module (shared)
> status_module (shared)
> wsgi_module (shared)
>
> we were getting segmentation faults when rest api clients were making
> requests. the apache error log has the following messages:
>
> [Mon Jul 27 09:04:38.375433 2015] [core:notice] [pid 32693:tid
> 140315326191488] AH00052: child pid 32700 exit signal Segmentation fault
> (11)
> [Mon Jul 27 09:04:38.375556 2015] [core:notice] [pid 32693:tid
> 140315326191488] AH00052: child pid 32701 exit signal Segmentation fault
> (11)
> [Mon Jul 27 09:04:39.379803 2015] [wsgi:info] [pid 385:tid
> 140315326191488] mod_wsgi (pid=385): Initializing Python.
> [Mon Jul 27 09:04:39.395480 2015] [wsgi:info] [pid 385:tid
> 140315326191488] mod_wsgi (pid=385): Attach interpreter ''.
> [Mon Jul 27 09:04:39.397131 2015] [wsgi:info] [pid 385:tid
> 140315326191488] mod_wsgi (pid=385): Imported 'mod_wsgi'.
>
> to find out what is going on, i started apache in debug mode using
> apachectl -X.
>
> we get the following error message before apache2 dies:
> [wsgi:crit] [pid 32367:tid 140681705703168] (70014)End of file found:
> mod_wsgi (pid=32367): Unable to read WSGI request.
>
> any clues/tips/suggestion/advice will be gratefully appreciated.
>
> best regards
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected] <javascript:>
> .
> Visit this group at http://groups.google.com/group/modwsgi.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.
