Configuring Django's runserver Logging Output

The issue you're experiencing is likely related to Django's logging configuration. Since Django 1.10, the runserver command's output goes through the Django logging framework instead of directly to sys.stderr. This change might be affecting how you see HTTP request logs in your Ubuntu environment.

Solution

You need to ensure your Django project has the proper logging configuration for the django.server logger. Add or update the following in your settings.py file:

PYTHONCopied
LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'formatters': {
        'django.server': {
            '()': 'django.utils.log.ServerFormatter',
            'format': '[%(server_time)s] %(message)s',
        }
    },
    'handlers': {
        'django.server': {
            'level': 'INFO',
            'class': 'logging.StreamHandler',
            'formatter': 'django.server',
        },
    },
    'loggers': {
        'django.server': {
            'handlers': ['django.server'],
            'level': 'INFO',
            'propagate': False,
        }
    },
}

This configuration ensures that the django.server logger (which handles request and response logging for the development server) will output to the console with the appropriate formatting.

Why This Happens

The difference you're seeing between Linux Mint and Ubuntu might be due to:

1. Different Django versions between your installations
2. Different default logging configurations in your Python environments
3. Different terminal configurations that might affect how logging output is displayed

The logging configuration above should resolve the issue regardless of these differences by explicitly setting up the server logger to output to the console.

After adding this configuration to your settings, restart the development server and you should see the HTTP request logs again.