Red Hat Bugzilla – Bug 1032101
Default settings cause masses of deprecation warnings in httpd error log
Last modified: 2015-11-22 09:22:41 EST
Description of problem:
Some settings in /usr/lib/python2.6/site-packages/graphite/app_settings.py from the graphite-web package cause the following messages to appear in /var/log/httpd/error_log (even though the graphite-web vhost uses another error log) whenever one navigates to the graphite-web vhost.
[Tue Nov 19 15:00:52 2013] [error] /usr/lib/python2.6/site-packages/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead.
[Tue Nov 19 15:00:52 2013] [error] "use STATIC_URL instead.", DeprecationWarning)
[Tue Nov 19 15:00:52 2013] [error] /usr/lib/python2.6/site-packages/django/core/cache/__init__.py:82: DeprecationWarning: settings.CACHE_* is deprecated; use settings.CACHES instead.
[Tue Nov 19 15:00:52 2013] [error] DeprecationWarning
Version-Release number of selected component (if applicable):
Name : graphite-web
Arch : noarch
Version : 0.9.12
Release : 5.el6
Size : 8.9 M
Repo : installed
From repo : epel
refer to the following steps
Steps to Reproduce:
1. Install graphite-web
2. set dns to point graphite-web to the host you installed on
3. browse to http://graphite-web
4. look at /var/log/httpd/error_log
error_log contains deprecation warnings
No deprecation warnings due to an updates configuration file
There are 2 Log entries per step one takes on the graphite web interface so the logs get swamped with log entries.
What are your thoughts on this? Should we just patch in the new variables?
(In reply to Jonathan Steffan from comment #1)
> What are your thoughts on this? Should we just patch in the new variables?
We should probably patch, as nobody likes thousands of deprecation warnings. Just need to make sure we test the changes.