Thanks for the quick response. Yes I received your mail multiple times and somehow all of them went to spam. I will take the code today, build it and let you know.
Regards Varun Dua On Saturday, May 31, 2014 5:20:19 PM UTC+5:30, Graham Dumpleton wrote: > > Try version 4.1.2 of mod_wsgi. > > https://github.com/GrahamDumpleton/mod_wsgi/releases > https://pypi.python.org/pypi/mod_wsgi > > to see if that now addresses your problem. > > Graham > > On 31/05/2014, at 8:33 PM, Graham Dumpleton <[email protected] > <javascript:>> wrote: > > See: > > https://github.com/GrahamDumpleton/mod_wsgi/issues/12 > > We believe we are on to the cause of this one. > > I was holding off on a new release because of some other work I was almost > done with, but I will look at doing a patch level release at this point now > as also have an issue with using 4.1.1 with Django management command. > > Sorry if this message has come through multiple times. Google mail > is giving me no end of problems right now with Apple Mail program by > delivering emails from wrong account and so keep getting rejected by > mailing list. > > Graham > > > On 31 May 2014 18:14, Varun Dua <[email protected] <javascript:>> wrote: > >> Hi, >> >> I installed apache with the worker mpm and then build mod_wsgi as >> specified in the Quick Installation Guide >> <https://code.google.com/p/modwsgi/wiki/QuickInstallationGuide>. Then I >> setup my Virtual Host using the configuration provided in Quick >> Configuration Guide >> <https://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide>. The >> sample wsgi application that was provided in the configuration was working >> fine. >> >> But when I add the WSGIDaemonProcess and WSGIProcessGroup directives as >> specified in the Configuration Guide >> >> *WSGIDaemonProcess example.com <http://example.com/> processes=2 >> threads=15 display-name=example.com <http://example.com/>* >> *WSGIProcessGroup example.com <http://example.com/>* >> >> my client recieves 503 Service Temporary Error. I looked in the server >> logs and the error was >> >> *(22)Invalid argument: mod_wsgi (pid=25676): Unable to connect to WSGI >> daemon process 'example.com <http://example.com/>' on >> '/var/run/apache2/wsgi.25672.0.1.sock'.* >> >> My apache server is running with the default user www-data. I checked for >> the file wsgi.25672.0.1.sock, it exists and has the read/write permission >> to the user www-data. Here is the outcome of the command *ls -al* >> *srwx------ 1 www-data root 0 May 31 12:28 >> /var/run/apache2/wsgi.25672.0.1.sock* >> >> I also checked whether the daemon process was working using the >> command ps -ax | grep -i example.com and it showed me two process (as >> mentioned in the the directive) and both of them (and apache as well) are >> running under the user www-data. >> >> I also tried adding WSGISocketPrefix directive in my server configuration >> but still getting the same error, though this time the location of the >> socket file was different. >> >> *Platform Configuration:* >> Ubuntu 13.04 >> >> *Apache Configuration (using apache2ctl -V)*: I have installed apache >> using apt-get (apt-get install apache2 apache2-mpm-worker >> apache2-threaded-dev) >> Server version: Apache/2.2.22 (Ubuntu) >> Server loaded: APR 1.4.6, APR-Util 1.4.1 >> Compiled using: APR 1.4.6, APR-Util 1.4.1 >> Architecture: 32-bit >> Server MPM: Worker >> threaded: yes (fixed thread count) >> forked: yes (variable process count) >> Server compiled with.... >> -D APACHE_MPM_DIR="server/mpm/worker" >> -D APR_HAS_SENDFILE >> -D APR_HAS_MMAP >> -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) >> -D APR_USE_SYSVSEM_SERIALIZE >> -D APR_USE_PTHREAD_SERIALIZE >> -D APR_HAS_OTHER_CHILD >> -D AP_HAVE_RELIABLE_PIPED_LOGS >> -D DYNAMIC_MODULE_LIMIT=128 >> -D HTTPD_ROOT="/etc/apache2" >> -D SUEXEC_BIN="/usr/lib/apache2/suexec" >> -D DEFAULT_PIDLOG="/var/run/apache2.pid" >> -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" >> -D DEFAULT_ERRORLOG="logs/error_log" >> -D AP_TYPES_CONFIG_FILE="mime.types" >> -D SERVER_CONFIG_FILE="apache2.conf >> >> *Mod_WSGI Version* >> 4.1.1 >> >> I am not sure whether this is the issue with mod_wsgi or apache, but I >> searched the internet and couldn't find a solution for this problem. Can >> anyone please help me fix this issue ? >> >> Regards >> Varun Dua >> >> -- >> 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.
