Are you using Debug toolbar?
Try this:
http://stackoverflow.com/questions/20963856/improperlyconfigured-the-included-urlconf-project-urls-doesnt-have-any-patte
cheers
L.
On 4 April 2014 11:14, Max Demars wrote:
> Greetings,
>
> I encounter the same error here. In latest gunicorn release, it's
Greetings,
I encounter the same error here. In latest gunicorn release, it's not
possible anymore to deploy gunicorn/django the old way doing python
manage.py run_gunicorn, so I'm stuck...I'd like to know if someone found
what causes this error.
-Max Demars
On Wednesday, November 28, 2012 6:0
Any progress on this? Does anyone know the causes?
On Sunday, June 23, 2013 2:55:16 PM UTC+5, Pratik Mandrekar wrote:
>
> Has anyone been able to resolve this?
>
> I am facing the same issue.
>
> On Sunday, March 24, 2013 8:46:26 PM UTC+5:30, Dan Gentry wrote:
>>
>> Andrei, I once received this er
Has anyone been able to resolve this?
I am facing the same issue.
On Sunday, March 24, 2013 8:46:26 PM UTC+5:30, Dan Gentry wrote:
>
> Andrei, I once received this error when the problem was actually in
> another python module being imported - in my case views.py. Hope this
> helps, Dan
--
Y
Andrei, I once received this error when the problem was actually in another
python module being imported - in my case views.py. Hope this helps, Dan
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiv
Hi again,
I have managed to run into the issue on a project not using Django CMS. It
also runs gunicorn with gevent.
Andrei
On Thursday, November 29, 2012 12:03:10 AM UTC+1, Michael Dippery wrote:
>
> I have a Django app running on a production server. It is handled with
> gunicorn 0.14.2 behi
Have you guys found a solution for this? This happens on one of our servers
that uses Django CMS and relies on gevent worker. Others using gevent work
fine. I am investigating other differences. Any suggestions?
Django==1.4.3
django-cms==2.3.1
eventlet==0.9.17
gevent==0.13.7
greenlet==0.4.0
guni
I've noticed this same behaviour as well but only with a higher loaded
production server and using the gunicorn gevent class, i've never seen this
happen with a sync class.
I'll take a wild guess that gevent worker class is handling requests before
django has had a chance to initialize. Perhaps
I have a Django app running on a production server. It is handled with gunicorn
0.14.2 behind nginx. When I reload the app (by reloading the gunicorn workers),
I get this error:
---
Traceback (most recent call last):
File
"/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/handlers/b
9 matches
Mail list logo
