Hi Jeremy, > Hi Daniel, > >> We have quite a few of these sitting in our queue :-( > > After a bit of time with some extra debug enabled for the buildroot mail > feed, I see this for the failed parsemail invocations where we've > returned a temp-fail: > > No handlers could be found for logger > "patchwork.management.commands.parsemail" > > If you recall, we had to alter the logging configuration for the ozlabs > instance: > > --- a/patchwork/settings/production.py > +++ b/patchwork/settings/production.py > @@ -70,7 +70,7 @@ > STATIC_URL = '/static/' > > > -LOGGING = { > +_LOGGING = { > 'version': 1, > 'disable_existing_loggers': False, > 'formatters': { > > [this was your suggested fix an issue with parsemail failing with the > shipped LOGGING configuration, but I don't have the specifics of that..] > Ergh, I was wondering when that would come back to bite us.
Would you mind sending me a copy of your LOGGING stanza (or just the whole production.py file, appropriately redacted)? I have no idea how yours fails as production.py is site specific and not managed by git. Regards, Daniel > So, it appears that this workaround needs to be reworked? > > Regards, > > > Jeremy _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork