That was a bug in DBIx::Log4perl and is fixed in 0.22 which I've just uploaded. I didn't see your thread even though I am a perl monk because your subject did not grab me and I don't have time to read every one - perhaps there is a lesson to be learnt there. The fix correctly identified elsewhere in this thread is trivial and a little embarrassing although I have to admit to not using the OUTPUT logging in my own projects.