TypeError in mailin logging

[Christian Zagrodnick]

There is an error in the logging of "something". I don't know what "something" though. This bug probably shadows some other problem.

2011-07-13 08:43:09,542 INFO karl.system: Running mailin
2011-07-13 08:43:09,542 INFO karlserve.scripts.mailin: Processing mailin for ariadne
Traceback (most recent call last):
  File "/usr/lib/python2.6/logging/__init__.py", line 776, in emit
    msg = self.format(record)
  File "/usr/lib/python2.6/logging/__init__.py", line 654, in format
    return fmt.format(record)
  File "/usr/lib/python2.6/logging/__init__.py", line 436, in format
    record.message = record.getMessage()
  File "/usr/lib/python2.6/logging/__init__.py", line 306, in getMessage
    msg = msg % self.args
TypeError: not all arguments converted during string formatting
2011-07-13 08:43:09,646 INFO karl.mailin: Processed 0 messages
2011-07-13 08:43:09,647 INFO karl.mailin: Bounced 0 messages
2011-07-13 08:43:10,930 INFO karl.system: Finished mailin

[Paul Everitt (paul-agendaless)]

Put this in for next week.

[Chris Rossi (chris-archimedeanco)]

Unfortunately, this one is next to impossible to figure out unless I can reproduce reliably locally. I did debug something like this locally one time and traced it to a bad logging call in a zope package somewhere. Unfortunately, the logging module uses a worker thread which completely obfuscates the source of the error in the stack trace. When I debugged this error locally, I had to hack the Python standard library so I could get information about the log message and take it from there. I can do this locally if I can reproduce, but I can't do this on Gocept's servers.