There is nothing out of the ordinary in that as far as logs.
One further suggestion. If you are using daemon mode, and only host the one
WSGI application, it is recommended that you use:
WSGIApplicationGroup %{GLOBAL}
in addition to the WSGIProcessGroup directory that delegates the WSGI
Thanks Graham for your suggestion.
I got hold of the httpd log and saw this (which seems normal to me),
(LogLevel is set to Info)
[Wed May 08 00:01:02.370191 2019] [core:notice] [pid 87977:tid
140036195301504] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu May 09 00:01:09.003672
> On 16 May 2019, at 3:32 pm, Sujai Kumar wrote:
>
> Hi Graham,
>
> Please find attached the inspect.py file.
>
> The process is running in Daemon mode.
>
> mod_wsgi configuration
> WSGIScriptAlias /rest
> /data/dev/deployment/production/release/server-python/sf_django/sf_app/wsgi.py
>
Hi Graham,
The python version is Python-3.6.3 and not 3.6.7. I have built this from
source. Inspect module came from build of Python. That code was not
manually edited. I still feel that the error has happened to occur with
'inspect' module once. It could have happened with any other module
Haha, for some reason I read it as Python 2.6 when I said ancient.
Anyway, can you grab section of code around line 825 in
/data/dev/Python-3.6.3s/lib/python3.6/inspect.py.
Python 3.6.7 doesn't match that code at that line number, so wondering whether
you are using older patch revision which
Hi Graham,
Here are the version of softwares being used.
*Python -> 3.6*
*mod_wsgi -> 4.6.4*
Sujai@machine0009:/usr/lib64/httpd/modules> ldd mod_wsgi.so
linux-vdso.so.1 => (0x7ffc74cd7000)
libpython3.6m.so.1.0 =>
/data/ev/Python-3.6.3s/lib/libpython3.6m.so.1.0
As already mentioned, if it is only on process shutdown (caused by a reload),
then it is possibly because it is trying to execute code when the interpreter
has been half destroyed. You cut off the file system paths and so I can't see
what:
File ".core/api/api_util.py", line 15, in
Are you sure you mod_wsgi is pulling in the correct Python shared library,
given that it looks like you are using a custom Python installation.
Is Python 3.6 installed as system Python?
Are you wanting to actually use a separate Python installation you installed
from source code?
Did you
Thanks for looking into this.
Well, the stack trace doesn't have much information. The issue happens when
caller function name was about to be logged (using the inspect module).
This was a working application for over an year and suddenly the situation
has occurred.
My inference is that the
Hard to tell just from the information you have given because you have
truncated the file system paths so can't tell what package this code is
executed from. The stack trace doesn't even look complete.
At a guess you are hitting an issue where there if there is a background thread
running when
Hello All,
We have a Apache/Python/Django using modwsgi. We hit upon a situation where
the following error is happening in the site,
*Error Log*
2019-05-09 09:18:08,471 - root - ERROR] - Error : Traceback (most recent
call last):
File ".core/api/api_util.py", line 15, in
11 matches
Mail list logo
