> On 23 Jul 2024, at 4:09 PM, RajKumar Ambadipelli <[email protected]> wrote: > > I am using Apache Server with mod_wsgi for hosting my python django > applications. Versions: Python 3.9.18 Server version: Apache/2.4.57 > mod-wsgi==4.7.1 > > One of my application virtual host configuration with two different versions: > > ... > > So, When the source code is modified I can referesh the wsgi daemon using > touch /home/uoadmin/releases/1.1.0/students/conf/wsgi.py touch > /home/uoadmin/releases/1.0.0/students/conf/wsgi.py But when I added new > virtualhost to the above configuration file or else when I modify above file > the apache server unable to recognize modifications made the existing > virtualhost or newly added virtualhost until doing apachectl graceful (or) > apachectl restart (or) systemctl reload httpd but all the commands above > killing the ongoing requests forcefully directly terminating them. > > How to handle above situation. > > I want to know how will apache server recognize modifications to virtualhost > or newly added virtual host without reloading or restarting. > It can't, Apache httpd requires you to perform a restart (reload) in order to read changes to the Apache configuration files. That is how it works.
> If above is not possible then is there anyway for restarting or reloading > apache server gracefully that is without terminating or killing other ongoing > requests or daemons while using apache server + mod_wsgi for serving python > with django? > Unfortunately not. The way Apache httpd manages the mod_wsgi daemon processes it will force a restart of those as well and even though Apache has a concept of graceful restart for it's own worker child processes, it doesn't extend that to managed process like the mod_wsgi daemon process and always restarts them immediately even when it is a graceful restart. There is nothing that can be done about this. The only way you could handle it if you need to be able to freely restart the main Apache server and have it not affect your Python web applications, is to run the Python web applications in distinct secondary web server processes and use the main Apache server to only proxy requests through to the secondary web servers. For the second web servers you could use mod_wsgi-express to make things easier, but you could also just not use mod_wsgi for the secondary web servers and use gunicorn or some other standalone Python WSGI/asyncio web server. Graham -- 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/2292A86D-092F-46D1-A3CE-A9906DBC42C8%40gmail.com.
