Skip to main content

Unable to configure handler 'console': __init__() got an unexpected keyword argument 'strm'

Django and upgraded from 2.6 to Python 2.7

Hopefuly this quick post will save someone time, I recently upgraded our Debian servers from stable (squeeze) to testing (wheezy).

Unfortunately this resulted in an odd error:

Traceback (most recent call last):
  File "manage.py", line 12, in 
    execute_from_command_line(sys.argv)
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/core/management/__init__.py", line 453, in execute_from_command_line
    utility.execute()
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/core/management/__init__.py", line 263, in fetch_command
    app_name = get_commands()[subcommand]
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/core/management/__init__.py", line 109, in get_commands
    apps = settings.INSTALLED_APPS
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/conf/__init__.py", line 53, in __getattr__
    self._setup(name)
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/conf/__init__.py", line 49, in _setup
    self._configure_logging()
  File "/srv/www/django/development.FOO.com/virtualenv/src/github-django-django-stable/django/conf/__init__.py", line 84, in _configure_logging
    logging_config_func(self.LOGGING)
  File "/usr/lib/python2.7/logging/config.py", line 777, in dictConfig
    dictConfigClass(config).configure()
  File "/usr/lib/python2.7/logging/config.py", line 575, in configure
    '%r: %s' % (name, e))
ValueError: Unable to configure handler 'console': __init__() got an unexpected keyword argument 'strm'
(virtualenv)root@klisrv10:/srv/www/django/development.FOO.com/src/django-project#

The solution is relatively simple but not easily foundable in Google or Bing. The logging definition in settings.py needs to be updated to use the new Python 2.7 'stream' keyword argument instead of 'strm'. My updated default project logging settings below:

LOGGING = {
 'version': 1,
 'disable_existing_loggers': True,
 'filters': {
        'require_debug_false': {
            '()': 'django.utils.log.RequireDebugFalse'
        }
    },
 'formatters': {
  'verbose': {
   'format': '%(levelname)s %(name)s %(asctime)s %(module)s %(process)d %(thread)d %(pathname)s@%(lineno)s: %(message)s'
  },
  'simple': {
   'format': '%(levelname)s %(name)s %(filename)s@%(lineno)s: %(message)s'
  },
 },
  # let the 'handlers' get all messages and filter level in 'loggers'
 'handlers': {
  'null': {
   #'level':'DEBUG',
   'class':'django.utils.log.NullHandler',
  },
  'console':{
   #'level':'WARNING',
   'class':'logging.StreamHandler',
   'formatter': 'simple',
   'stream': sys.stderr,
   # 'stream': sys.stdout
   # see https://code.google.com/p/modwsgi/wiki/ApplicationIssues#Writing_To_Standard_Output
   
  },
  'mail_admins': {
   #'level': 'ERROR',
   'filters': ['require_debug_false'],
   'class': 'django.utils.log.AdminEmailHandler',
   'formatter': 'verbose'
  }
 },
 'loggers': {
  # catch all logger ex. any logger = logging.getLogger(__name__)
  '': { 
   'handlers': ['mail_admins', 'console'],
   'level': 'WARNING',
  },
 }
}

As always if you found this useful feel free to follow me here or via twitter @danielsokolowski.

Comments

Popular posts from this blog

Storing passwords in PuTTY

How to save SSH username/password for auto login in PuTTy The answer is you can't do it...at least in plain PuTTy. However there is an awesome fork with that let's you store the username and password and other additional features called KiTTy . So grab yourself a copy and +1 this if you do, thanks.

Softeher 'Error occurred. (Error code: 2)' sollution

Protocol error occurred. Error was returned from the destination server. The Softether server by default to run on port 443 , if you server also hosts normal https then 443 is already taken and so Softether can't bind to it. When you run `vpncmd` it attempts to connect, find an active port, but of course fails with 'Protocol error occurred. Error was returned from the destination server.' because it's not actually connecting to the vpn server. By default Softether also listens on 992 , 1194 , and 5555 so the sollution is to modify specify `localhost:5555` when executing the `vpncmnd`. If this has helped you feel free to comment or follow me on twitter @danielsokolows .

LightScribe Template Labeler for Windows 10

LightScribe Template Labeler installation "Operating System Inadequate" Issue Unfortunately 'LightScribe Template Labeler' installation will not work on Windows 8 and Windows 10 machines as the install simply will error out with 'Operating System Inadequate'. Trying to install using compatibility mode did not help. Installing LightScribe Template Labeler Workaround However if you simply copy the installed folder from an older machine like Windows 7 into your `C:\\Program Files (x86)\LightScribe Template Labeler`, create a shortcut, then the software will still happily work, see: http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/lightscribe-templatesimple-labeler-the-system-is/c2ebee28-bfb5-4aef-beb3-a43329561da8?db=5&auth=1 So you can install Windows 7 machine in a virtual machine, install 'LightScribe Template Labeler', and then copy the resulting folder to your Windows 8 or Windows 10 machine. For my own convenien...