On 19 January 2012 19:01, nitin chandra <[email protected]> wrote: > Thank you Graham, > > The following is my apache config setting With Virtual Host. I have > been trying to set IP based, therefore some lines are commented.
Why are you even trying to use IP binding for VirtualHost? It is a rather special ability of Apache which you do not need unless you are multihoming with IP addresses. Using it if you don't need it usually just causes problems. In your case it certainly is causing confusion. > WSGIImportScript ?? :P :) , now where does that go in the following config ? Ignore I ever mentioned it. You are not using it now so you don't need it. > TIA > > Nitin > > ************************************************ > Listen 192.168.1.6:81 (Main ApAcHe setting) > > > > NameVirtualHost 192.168.1.6:81<VirtualHost 192.168.1.6:81> > #ServerName www.healthcare.in #ServerAlias healthcare.in > #Redirect / https://www.healthcare.in/index.py > Redirect / https://192.168.1.6/index.py > WSGIDaemonProcess healthcare.in processes=6 threads=15 > display-name=%{GROUP} # WSGIDaemonProcess 192.168.1.6 processes=6 > threads=15 display-name=%{GROUP} You have the WSGIDaemonProcess for 192.168.1.6 commented out yet following WSGIProcessGroup are still referring to it. You do not need to have changed the names you were using. The name for the daemon process group does not need to be the same as either ServerName or the IP address a VirtualHost may be listening on. You can call it whatever you want, it is just a name used such that WSGIProcessGroup can refer to a daemon process group set up by WSGIDaemonProcess. Graham > # WSGIProcessGroup healthcare.in WSGIProcessGroup 192.168.1.6 > WSGIScriptAlias /wsgi-scripts/ /home/dev/wsgi-scripts/index.py > <Directory /home/dev/wsgi-scripts> Options Indexes MultiViews > +FollowSymLinks +ExecCGI Order allow,deny Allow from all > AddHandler wsgi-script .py > # WSGIProcessGroup healthcare.in WSGIProcessGroup 192.168.1.6 > </Directory></VirtualHost> > Listen 192.168.1.6:443AddType application/x-x509-ca-cert .crtAddType > application/x-pkcs7-crl .crlSSLPassPhraseDialog > builtinSSLSessionCache > "shmcb:/tmp/ssl_scache(512000)"SSLSessionCacheTimeout 300SSLMutex > "file:/tmp/ssl_mutex" > <VirtualHost 192.168.1.6:443> > DocumentRoot "/home/dev/wsgi-scripts/" > > # ServerName www.healthcare.in > ServerName 192.168.1.6 > > ServerAdmin [email protected] > SSLEngine on > SSLCipherSuite > ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL > SSLCertificateFile "/etc/cups/ssl/server.crt" > SSLCertificateKeyFile "/etc/cups/ssl/server.key" > <FilesMatch "\.(cgi|shtml|phtml|php|py|pyc)$"> > SSLOptions +StdEnvVars > </FilesMatch> > <Directory /home/dev/wsgi-scripts> > Options MultiViews +FollowSymLinks > Order allow,deny > Allow from all > SSLOptions +StdEnvVars > Options Indexes +ExecCGI > AddHandler wsgi-script .py > > WSGIProcessGroup healthcare.in > # WSGIProcessGroup 192.168.1.6 > > </Directory> > BrowserMatch ".*MSIE.*" \ > nokeepalive ssl-unclean-shutdown \ > downgrade-1.0 force-response-1.0 > </VirtualHost> > > #<IfModule ssl_module> > SSLRandomSeed startup builtin > SSLRandomSeed connect builtin > #</IfModule> > > *************************************************************** > > > On Thu, Jan 19, 2012 at 4:56 AM, Graham Dumpleton > <[email protected]> wrote: >> The first argument to WSGIDaemonProcess can be any value so long as >> WSGIProcessGroup matches it. The issue is the placement and ordering in some >> cases. You likely therefore have simply defined it in the wrong place for >> where the WSGIProcessGroup is that you have set up to refer to it. >> >> You will need to provide more of the configuration, showing where >> WSGIDaemonProcess and WSGIProcessGroup are defined. In other words, whether >> in or outside of VIrtualHost and which VirtualHost. Also show where >> WSGIScriptAlias is in relation to that and what the full arguments are to it >> are, plus if using WSGIImportScript, where that is defined and the full >> arguments. >> >> Graham > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
