Hi Wietse, > On Nov 11, 2017, at 8:37 AM, Wietse Venema <wie...@porcupine.org> wrote: > > J Doe: >> Is this really the only way to fix this, though ? This feels a bit like a >> workaround as opposed to the ?correct? solution (assuming that there is a >> ?more correct? solution). > > Why bother with all this? The database is synced without error. > It is in a consistent state. Only the close operation complains > because of some DB bug. This does not affect correctness.
Thanks for your reply. When Googling for this problem, a number of the posts I found referenced this situation happening in jailed deployments and that’s what I’m running. Most of these posts are from some time ago, so I assumed that with me running Postfix 3.1 on a modern distro, the bug(s) in the Berkeley DB libraries that cause this issue would be fixed by the Berkeley DB developers. The other reason is that the volume of these warnings seemed quite large. I can, of course, filter that out, but I wondered if there was a workaround for this to suppress the warnings. The workaround that I found works, I just wasn’t sure if it was the best solution. - J
