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

Post a Comment

Popular posts from this blog

Duplicate value found: duplicates value on record with id: <unknown>.

System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>. The above error is triggered in the database layer and caused by a trigger or workflow outside of your main code of block that is bubbling this exception. This is rather difficult to track down especially if you are unfamiliar with the code, I am sharing my procedure in the hopes this saves you time - if you find this helpful drop me a line or follow me on twitter @danielsokolows . This error is caused by unique field constraint on the object, so the first step is to examine the object and locate the API names of all unique fieds. You can do this through SF direclty 'Setup < Customize &lt <object being inserted> &lt Fields' or by downloading the `src/objects` metadata information and searching for <unique> ; I preffer the latter and actually download ALL matadata i
3 comments
Read more

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 .
6 comments
Read more

How to child proof a fireplace

DIY - Do it yourself fireplace child guard Our wonderful 8.5 month old Sofia has become a crawling race car with an untamed thirst for exploration. And so with the cold nights approaching we needed to child proof the fireplace. This however proved to be more difficult than would reasonably expect, I've checked the local Toys "R" Us, Walmart, and even a Canadian Tire with no success for a ready to use product. Internet search was more fruitful and returned a few online stores one could order from, however in all honestly they didn't look too sturdy to me. So I build my own relatively quickly and inexpensively. Materials needed is a privacy plastic lattice - the smallest hole pattern - a few screws and anchors; tools needed are a drill, and a handsaw if you don't have the lattice cut at the store - that’s it. The construction consits of screwing the lattice into the wall and the final product is easiest explained through following pictures.
11 comments
Read more