What instructions are telling you to set it up in this way? That is, setting the WSGI script file to be a path inside of the installed Python installation. This is highly unconventional and wouldn't usually be done.
Also concerning that setting python-path to the site-packages of the Python installation. This is also wrong. If this is necessary it suggests that you mod_wsgi version may not even be compiled for Python 2.7, which may be part of the problem, as you would be mixing Python packages with extensions compiled for Python 2.7, with a mod_wsgi compiled for a different Python version. > On 30 Jun 2020, at 7:18 pm, bo li <[email protected]> wrote: > > ''' > Listen 0.0.0.0:8777 > > LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" > combined > > <VirtualHost *:8777> > LogLevel info > WSGIDaemonProcess ceilometer-api processes=4 threads=8 user=ceilometer > group=ceilometer display-name=%{GROUP} > python-path=/usr/lib/python2.7/site-packages > WSGIProcessGroup ceilometer-api > > WSGIScriptReloading On > WSGIScriptAlias / /usr/lib/python2.7/site-packages/ceilometer/api/app.wsgi > > WSGIApplicationGroup %{GLOBAL} > > <Directory "/usr/lib/python2.7/site-packages/ceilometer/api"> > <IfVersion >= 2.4> > Require all granted > </IfVersion> > <IfVersion < 2.4> > Order allow,deny > Allow from all > </IfVersion> > </Directory> > ErrorLog /dev/stdout > CustomLog /dev/stdout combined > </VirtualHost> > ''' > > this is my wsgi configuraton. > > is it correctly? > > Thanks > > 在 2020年6月30日星期二 UTC+8下午4:16:31，Graham Dumpleton写道： > Provide the mod_wsgi configuration you are using so can verify you are in > fact setting it up correctly. > > Also check: > > https://modwsgi.readthedocs.io/en/develop/user-guides/checking-your-installation.html#sub-interpreter-being-used > > <https://modwsgi.readthedocs.io/en/develop/user-guides/checking-your-installation.html#sub-interpreter-being-used> > > and indicate what you get. > >> On 30 Jun 2020, at 6:03 pm, bo li <[email protected] <>> wrote: >> >> I have the same problem >> >> i also Using WSGIApplicationGroup %{GLOBAL}, but it appear " Daemon process >> deadlock timer expired, stopping process" >> >> if u have solved the problem , can you reply to me ? >> >> Thanks >> >> 在 2019年1月22日星期二 UTC+8下午10:37:58，Shakim Mohammed写道： >> Hello, >> >> I have a Flask + Sqlalchemy application(connecting to a Sybase database) >> that I am trying to run in Apache + mod_wsgi setup >> >> Few pointers on my wsgi setup: >> Using WSGIDaemonProcess <nameOfApp> processes=x threads=y >> Using WSGIApplicationGroup %{GLOBAL} >> No matter what combination of values of x and y I use, after processing some >> request, my apache/mod_wsgi hangs up for sometime showing logs like : >> Daemon process deadlock timer expired, stopping process <> >> Shutdown process <nameOfApp> >> Aborting process <nameOfApp> >> Exiting process <nameOfApp> >> I believe it hangs for 300 seconds(which is default deadlock-timeout) >> If I set deadlock-timeout = 60, apache/mod_wsgi recovers in 60sec >> >> Few other logs that I see are : >> Truncated or oversized response headers received from daemon process >> <nameOfApp> >> server seems busy, (you may need to increase StartServers, or >> Min/MaxServers, spawning 16 children, there are three idle >> What could be the reason of this deadlock and other logs shown above? >> >> Could this be because of a rogue C extension as pointed out by Graham at >> various places? >> >> There are bunch of third party modules that I am using which has C extension >> like -> http://python-sybase.sourceforge.net/download.html >> <http://python-sybase.sourceforge.net/download.html> >> >> Is there anyway to fix this or make it more stable(not going into deadlock >> too frequently and giving 500 to clients)? >> >> FYI, I am using prefork instead of worker at this moment. I am not loading >> unnecessary modules like mod_php. >> The only modules that I am loading in my apache conf are >> "mod_authz_host.so", "mod_log_config.so" and "mod_wsgi.so" >> I believe the issue I am trying to highlight is totally independent of >> whether it is a prefork or worker setup >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/modwsgi/c13f4ce5-4010-4fa6-a3fd-219bf2e9bbbbo%40googlegroups.com >> >> <https://groups.google.com/d/msgid/modwsgi/c13f4ce5-4010-4fa6-a3fd-219bf2e9bbbbo%40googlegroups.com?utm_medium=email&utm_source=footer>. > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/modwsgi/6e0c27b4-6bb1-4805-949e-b86ce05e4369o%40googlegroups.com > > <https://groups.google.com/d/msgid/modwsgi/6e0c27b4-6bb1-4805-949e-b86ce05e4369o%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/modwsgi/7205B9E0-05EF-49ED-BD2E-AA03EF8DA43F%40gmail.com.
