logmessage: received a naive datetime while time zone support is active
the logs are filling with this error on what seems to be every web request. ~500MB per day of.
Aug 17 09:00:19 scinage-p01.private.uwaterloo.ca uwsgi[469]: RuntimeWarning)
Aug 17 09:00:19 scinage-p01.private.uwaterloo.ca uwsgi[469]: [pid: 689|app: 0|req: 317608/3889706] 129.97.58.107 () {42 vars in 723 bytes} [Wed Aug 17 13:00:19 2016] GET /screens/ping/dp-5th-floor/ => generated 19 bytes in 38 msecs (HTTP/1.1 200) 2 headers in 80 bytes (1 switches on core 0)
Aug 17 09:00:19 scinage-p01.private.uwaterloo.ca uwsgi[469]: /usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py:1474: RuntimeWarning: DateTimeField Screen.last_connect received a naive datetime (2016-08-17 13:00:19.855058) while time zone support is active.
Aug 17 09:00:19 scinage-p01.private.uwaterloo.ca uwsgi[469]: RuntimeWarning)
Aug 17 09:00:19 scinage-p01.private.uwaterloo.ca uwsgi[469]: [pid: 690|app: 0|req: 286872/3889707] 129.97.58.107 () {42 vars in 723 bytes} [Wed Aug 17 13:00:19 2016] GET /screens/ping/dp-8th-floor/ => generated 19 bytes in 34 msecs (HTTP/1.1 200) 2 headers in 80 bytes (1 switches on core 0)
Aug 17 09:00:20 scinage-p01.private.uwaterloo.ca uwsgi[469]: /usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py:1474: RuntimeWarning: DateTimeField Screen.last_connect received a naive datetime (2016-08-17 13:00:20.014137) while time zone support is active.
Aug 17 09:00:20 scinage-p01.private.uwaterloo.ca uwsgi[469]: RuntimeWarning)seems to be an issue with how time is passed to a django model.
http://stackoverflow.com/questions/18622007/runtimewarning-datetimefield-received-a-naive-datetime