I am not a Django person, but strikes me that: django.contrib.sessions sessions
would conflict as application name likely taken from name of last sub module in path. Graham On 13/12/2014, at 10:02 AM, Jennifer Mehl <[email protected]> wrote: > INSTALLED_APPS = ( > 'django.contrib.auth', > 'django.contrib.contenttypes', > 'django.contrib.sessions', > 'django.contrib.sites', > 'django.contrib.messages', > 'django.contrib.staticfiles', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > 'django.contrib.admindocs', > 'myproject.duo_app', > 'myproject.myapp', > 'sessions', > ) > > How can I figure out which of the 2 sessions apps listed, is in use? And if > they are both in use, I presume I need to rename one of them in the code? > > I realize this out of scope for the mod_wsgi group, but do appreciate the > help. :-) > > —Jennifer > >> On Dec 12, 2014, at 2:57 PM, Graham Dumpleton <[email protected]> >> wrote: >> >> What do you have in INSTALLED_APPS of the Django settings file? >> >> Graham >> >> On 13/12/2014, at 9:39 AM, Jennifer Mehl <[email protected]> wrote: >> >>> Thank you Joonas and Graham - you guys are lifesavers! That really helped. >>> >>> This moves me to the next error: >>> >>> >>> mod_wsgi (pid=17140): Target WSGI script >>> '/var/www/transfergateway/myproject/wsgi.py' cannot be loaded as Python >>> module. >>> >>> mod_wsgi (pid=17140): Exception occurred processing WSGI script >>> '/var/www/transfergateway/myproject/wsgi.py'. >>> >>> Traceback (most recent call last): >>> >>> File "/var/www/transfergateway/myproject/wsgi.py", line 30, in <module> >>> application = get_wsgi_application() >>> >>> File "/usr/local/lib/python2.7/dist-packages/django/core/wsgi.py", line 14, >>> in get_wsgi_application django.setup() >>> >>> File "/usr/local/lib/python2.7/dist-packages/django/__init__.py", line 21, >>> in setup apps.populate(settings.INSTALLED_APPS) >>> >>> File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py", line >>> 89, in populate >>> >>> "duplicates: %s" % app_config.label) ImproperlyConfigured: Application >>> labels aren't unique, duplicates: sessions >>> >>> >>> I am not the developer of this application, so I'm not sure where to look >>> to fix this. I did install all of the dependent django and python packages >>> that I know of, inside the chroot. >>> >>> --Jennifer >>> >>> >>> On Friday, December 12, 2014 2:25:19 PM UTC-8, Graham Dumpleton wrote: >>> >>> On 13/12/2014, at 8:12 AM, Joonas Lehtolahti <[email protected]> wrote: >>> >>>> On Fri, 12 Dec 2014 22:55:42 +0200, Jennifer Mehl <[email protected]> >>>> wrote: >>>> >>>> ... >>>> >>>>> WSGIDaemonProcess chroot user=daemon group=daemon processes=2 threads=25 >>>>> chroot=/var/chroot python-path=/var/chroot/var/www/transfergateway >>>> >>>> ... >>>> >>>>> I believe my issue now is relating to the PythonPath directive and access >>>>> to the project/Python my chroot, but am unsure how to resolve. >>>>> >>>>> I'm kind of stuck-- so I appreciate the help! >>>>> >>>>> --Jennifer >>>>> >>>> >>>> Just a thought from an outsider: since the Python interpreter is running >>>> inside chroot, perhaps the python-path option needs to point to a path >>>> local to the root, that is, it shouldn't contain /var/chroot. >>> >>> Yes, that is correct. >>> >>> General Apache configuration should use /var/chroot as well as >>> WSGIScriptAlias. >>> >>> But anything that would be applied when handling a request shouldn't have >>> /var/chroot as it is being used by the application inside of the chroot. >>> >>> So I would agree that should probably be: >>> >>> WSGIDaemonProcess chroot user=daemon group=daemon processes=2 threads=25 \ >>> chroot=/var/chroot python-path=/var/www/transfergateway >>> >>> Thanks Joonas, you beat me to it. :-) >>> >>> 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. >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "modwsgi" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/modwsgi/sOrtcm7JV50/unsubscribe. >> To unsubscribe from this group and all its topics, 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. > > -- > 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. -- 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.
