On 3/31/2014 11:50 AM, Viktor Dukhovni wrote:
Why on earth do people routinely truncate log entries to leave out
the name of the daemon that is logging the message???
Cause sometimes they forget. By the way the daemon in question is
postfix/tlsmgr but you already knew that.
What Postfix service (daemon) logged this message? Was it after
a Postfix reload, restart, or some other time?
No it happens seemingly at random.
Have you changed the master.cf entry for tlsmgr(8) from its default
configuration? It must have a process limit of 1.
tlsmgr unix - - n 1000? 1 tlsmgr
Yes, the master.cf entry for tlsmgr has a process limit of 1 and it
looks just your example above.
The database in question is not safe for multiple writers. Beyond
that you might have a buggy Berkeley DB, or SELinux blocking access.
SELinux is not installed. How would I determine if Berkeley DB is buggy?
Postfix tlsmgr(8) truncates the TLS session cache database whe it
restarts, so there should not be any errors even if the database
was previously corrupted.
Agreed, yet it still happens.
