Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Lachlan Musicman]

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 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:03:10 PM UTC-5, Michael Dippery wrote:
>>
>> 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/base.py",
>> line 101, in get_response
>>request.path_info)
>>
>>  File
>> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>> line 250, in resolve
>>for pattern in self.url_patterns:
>>
>>  File
>> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>> line 283, in _get_url_patterns
>>raise ImproperlyConfigured("The included urlconf %s doesn't have any
>> patterns in it" % self.urlconf_name)
>>
>> ImproperlyConfigured: The included urlconf myapp.urls doesn't have any
>> patterns in it
>> ---
>>
>> Others with this problem have commonly noted that it occurs while using
>> reverse in a URLconf, but I am not using reverse in any URLconfs (nor are
>> they used in any third-party apps). Also, this error only occurs in
>> production -- never in development (using the Django dev server) or on my
>> staging server (also using gunicorn 0.14.2 behind nginx). It also doesn't
>> seem to cause trouble with the site at any other time then during reloads.
>> And it only happens for the first 10-20 requests on the website (which makes
>> me wonder if it's some sort of race condition, perhaps).
>>
>> Any ideas what's causing the problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/b9653b7b-c3bc-408a-9b38-e8cd10e6e4d7%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
>From this perspective it is natural that anarchism be marked by
spontaneity, differentiation, and experimentation that it be marked by
an expressed affinity with chaos, if chaos is understood to be what
lies outside or beyond the dominant game or system. Because of the
resistance to definition and categorisation, the anarchist principle
has been variously interpreted as, rather than an articulated
position, “a moral attitude, an emotional climate, or even a mood”.
This mood hangs in dramatic tension between utopian hope or dystopian
nihilism...
-
http://zuihitsu.org/godspeed-you-black-emperor-and-the-politics-of-chaos

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGBeqiPpOEFjUDPEREYgwxCvciUqgejJy7%2BzObf1STQjNUyPnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Max Demars]

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:03:10 PM UTC-5, Michael Dippery wrote:
>
> 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/base.py",
>  
> line 101, in get_response 
>request.path_info) 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 250, in resolve 
>for pattern in self.url_patterns: 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 283, in _get_url_patterns 
>raise ImproperlyConfigured("The included urlconf %s doesn't have any 
> patterns in it" % self.urlconf_name) 
>
> ImproperlyConfigured: The included urlconf myapp.urls doesn't have any 
> patterns in it 
> --- 
>
> Others with this problem have commonly noted that it occurs while using 
> reverse in a URLconf, but I am not using reverse in any URLconfs (nor are 
> they used in any third-party apps). Also, this error only occurs in 
> production -- never in development (using the Django dev server) or on my 
> staging server (also using gunicorn 0.14.2 behind nginx). It also doesn't 
> seem to cause trouble with the site at any other time then during reloads. 
> And it only happens for the first 10-20 requests on the website (which 
> makes me wonder if it's some sort of race condition, perhaps). 
>
> Any ideas what's causing the problem?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/b9653b7b-c3bc-408a-9b38-e8cd10e6e4d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Ahmed Khan]

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 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 receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/6df3be6b-e0a6-41d0-b41a-40bae2e52d8c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Pratik Mandrekar]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Dan Gentry]

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 receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Andrei]

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 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/base.py",
>  
> line 101, in get_response 
>request.path_info) 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 250, in resolve 
>for pattern in self.url_patterns: 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 283, in _get_url_patterns 
>raise ImproperlyConfigured("The included urlconf %s doesn't have any 
> patterns in it" % self.urlconf_name) 
>
> ImproperlyConfigured: The included urlconf myapp.urls doesn't have any 
> patterns in it 
> --- 
>
> Others with this problem have commonly noted that it occurs while using 
> reverse in a URLconf, but I am not using reverse in any URLconfs (nor are 
> they used in any third-party apps). Also, this error only occurs in 
> production -- never in development (using the Django dev server) or on my 
> staging server (also using gunicorn 0.14.2 behind nginx). It also doesn't 
> seem to cause trouble with the site at any other time then during reloads. 
> And it only happens for the first 10-20 requests on the website (which 
> makes me wonder if it's some sort of race condition, perhaps). 
>
> Any ideas what's causing the problem?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Andrei]

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
gunicorn==0.14.6

Andrei


On Monday, December 3, 2012 6:48:12 AM UTC+1, Garth Cumming wrote:
>
> 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 django does some sort 
> of blocking on startup and the gevent monkey patching prevents this 
> blocking behaviour on startup. Just a wild guess.
>
> On Wednesday, November 28, 2012 3:03:10 PM UTC-8, Michael Dippery wrote:
>>
>> 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/base.py",
>>  
>> line 101, in get_response 
>>request.path_info) 
>>
>>  File 
>> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>>  
>> line 250, in resolve 
>>for pattern in self.url_patterns: 
>>
>>  File 
>> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>>  
>> line 283, in _get_url_patterns 
>>raise ImproperlyConfigured("The included urlconf %s doesn't have any 
>> patterns in it" % self.urlconf_name) 
>>
>> ImproperlyConfigured: The included urlconf myapp.urls doesn't have any 
>> patterns in it 
>> --- 
>>
>> Others with this problem have commonly noted that it occurs while using 
>> reverse in a URLconf, but I am not using reverse in any URLconfs (nor are 
>> they used in any third-party apps). Also, this error only occurs in 
>> production -- never in development (using the Django dev server) or on my 
>> staging server (also using gunicorn 0.14.2 behind nginx). It also doesn't 
>> seem to cause trouble with the site at any other time then during reloads. 
>> And it only happens for the first 10-20 requests on the website (which 
>> makes me wonder if it's some sort of race condition, perhaps). 
>>
>> Any ideas what's causing the problem?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Django throws ImproperlyConfigured error when loading URLconf on startup

[Garth Cumming]

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 django does some sort of 
blocking on startup and the gevent monkey patching prevents this blocking 
behaviour on startup. Just a wild guess.

On Wednesday, November 28, 2012 3:03:10 PM UTC-8, Michael Dippery wrote:
>
> 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/base.py",
>  
> line 101, in get_response 
>request.path_info) 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 250, in resolve 
>for pattern in self.url_patterns: 
>
>  File 
> "/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py",
>  
> line 283, in _get_url_patterns 
>raise ImproperlyConfigured("The included urlconf %s doesn't have any 
> patterns in it" % self.urlconf_name) 
>
> ImproperlyConfigured: The included urlconf myapp.urls doesn't have any 
> patterns in it 
> --- 
>
> Others with this problem have commonly noted that it occurs while using 
> reverse in a URLconf, but I am not using reverse in any URLconfs (nor are 
> they used in any third-party apps). Also, this error only occurs in 
> production -- never in development (using the Django dev server) or on my 
> staging server (also using gunicorn 0.14.2 behind nginx). It also doesn't 
> seem to cause trouble with the site at any other time then during reloads. 
> And it only happens for the first 10-20 requests on the website (which 
> makes me wonder if it's some sort of race condition, perhaps). 
>
> Any ideas what's causing the problem?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/KhaMhHaubnEJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Django throws ImproperlyConfigured error when loading URLconf on startup

[Michael Dippery]

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/base.py", 
line 101, in get_response
   request.path_info)

 File 
"/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py", 
line 250, in resolve
   for pattern in self.url_patterns:

 File 
"/opt/app/venv/myapp/lib/python2.6/site-packages/django/core/urlresolvers.py", 
line 283, in _get_url_patterns
   raise ImproperlyConfigured("The included urlconf %s doesn't have any 
patterns in it" % self.urlconf_name)

ImproperlyConfigured: The included urlconf myapp.urls doesn't have any patterns 
in it
---

Others with this problem have commonly noted that it occurs while using reverse 
in a URLconf, but I am not using reverse in any URLconfs (nor are they used in 
any third-party apps). Also, this error only occurs in production -- never in 
development (using the Django dev server) or on my staging server (also using 
gunicorn 0.14.2 behind nginx). It also doesn't seem to cause trouble with the 
site at any other time then during reloads. And it only happens for the first 
10-20 requests on the website (which makes me wonder if it's some sort of race 
condition, perhaps).

Any ideas what's causing the problem?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.