44
Just came across the same issue – in my case it happened because the database server was down
EDIT: Django version 1.9
20
when django can’t connect to your database django run hangs at
System check identified no issues (0 silenced).
totally issue related database config:
- check database service is up
- check database Host name and Port
- check database UserName and Password
- check database User permission in DB side.
- [Django]-Is the Lift framework as "easy" as Ruby on Rails or Django?
- [Django]-Additional field while serializing django rest framework
- [Django]-Parsing a Datetime String into a Django DateTimeField
14
I my case I was attempting to connect to a remote database that wasn’t responding to connection requests.
Try python manage.py dbshell. This gave me no output. Then I went into amazon web services and relaxed the security settings.
- [Django]-How to limit columns returned by Django query?
- [Django]-Proper way to handle multiple forms on one page in Django
- [Django]-Generating a Random Hex Color in Python
5
It may be a database connection error.
If you are using AWS for your database, go to the RDS instances tab, click on the security group(s) and edit their inbound/outbound rules to allow connections from the correct host (or from anywhere for a quick fix)
- [Django]-Django: How to check if the user left all fields blank (or to initial values)?
- [Django]-Django csrf token + Angularjs
- [Django]-Django template how to look up a dictionary value with a variable
3
It might worth to read about the System Check framework.
Serious errors will prevent Django commands (such as runserver) from running at all. Minor problems are reported to the console. If you have inspected the cause of a warning and are happy to ignore it, you can hide specific warnings using the SILENCED_SYSTEM_CHECKS setting in your project settings file.
If you don’t see any issue being displayed is probably because there were no issues running the system check, if something else is not working the error may not be related, then we need more information.
- [Django]-CORS: Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true
- [Django]-Django: best practice for splitting up project into apps
- [Django]-Django can' t load Module 'debug_toolbar': No module named 'debug_toolbar'
3
I had this same issue and realized it was because i had recently reactivated my VPN so if anyone has a VPN that may be why. Youll need to follow Harry’s directions for the fix
- [Django]-Django or Ruby-On-Rails?
- [Django]-Paginate relationship in Django REST Framework?
- [Django]-No handlers could be found for logger
- [Django]-How to check if django template variable is defined?
- [Django]-"Fixed default value provided" after upgrading to Django 1.8
- [Django]-Create Custom Error Messages with Model Forms
0
There is no test_ function in my case. Please make sure your file is named test_~.py and it must have def test_~: inside.
- [Django]-What is a "slug" in Django?
- [Django]-Apache or Nginx to serve Django applications?
- [Django]-Django REST framework serializer without a model
0
I got exactly the same error because I ran $ python manage.py runserver when I was in a Toronto Library.
As soon as I got home, I ran it again, and got no error any more.
I guess that it is because the library firewall blocks port 5432, which AWS databases run on.
- [Django]-How to convert a Django QuerySet to a list?
- [Django]-How to change empty_label for modelForm choice field?
- [Django]-Default value for user ForeignKey with Django admin
0
DATABASES = {
"default": {
"ENGINE": "django.db.backends.sqlite3",
"NAME": BASE_DIR / "db.sqlite3",
}
}
if your server gets killed without any error, try this, worked for me
comment above line from settings.py
- [Django]-Django Debug Toolbar: understanding the time panel
- [Django]-How do you know if memcached is doing anything?
- [Django]-Loop backwards using django template