On 01/12/2014, at 9:38 PM, r van dam <[email protected]> wrote: > Strange, when I setup a second domain for daemon mode this domain has this > error in his logs: > > [Mon Dec 01 11:32:38.383772 2014] [wsgi:error] [pid 17357] (2)No such file or > directory: [client 81.58.150.99:60383] mod_wsgi (pid=17357): Unable to > connect to WSGI daemon process 'jouwsta' on > '/etc/httpd/var/run/apache.17353.0.1.sock'., referer: > http://www.jouwstacaravan.nl/achterhoek/
This gets back to what I said about WSGISocketPrefix needing to be an absolute path. Looks like it will still actually be added below server root if you don't. It also is meant to still have the 'wsgi' name at the end. http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGISocketPrefix Thus: WSGISocketPrefix /var/run/apache2/wsgi If you don't, it is actually trying to create them in a directory above where you intended them to be. If that is now only just showing up when you add a new virtual host, there is really something screwy going on with how your Apache configuration files are organised. Do you have everything in the one httpd.conf, or using a Lunux like setup where spread over many files and with sites in separate files? 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 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.
