Re: verify database error
- Zitat von "Daniel L. Miller" <dmiller@...>:
> On 4/3/2012 10:32 AM, Wietse Venema wrote:With Postfix update you might "cleanup" the error message, with
>> Daniel L. Miller:
>>> I keep seeing the following in the log:
>>> postfix/verify: close database /var/lib/postfix/verify.db: No
>>> such file or directory
>> * With some Berkeley DB implementations, close fails with a
>> bogus ENOENT
>> * error, while it reports no errors with put+sync, no errors with
>> * del+sync, and no errors with the sync operation just before this
>> * comment. This happens in programs that never fork and that
>> never share
>> * the database with other processes. The bogus close error has been
>> * reported for programs that use the first/next iterator. Instead of
>> * making Postfix look bad because it reports errors that other programs
>> * ignore, I'm going to report the bogus error as a non-error.
>> if (DICT_DB_CLOSE(dict_db->db)< 0)
>> msg_info("close database %s: %m (possible Berkeley DB bug)",
> I'm currently using Postfix 2.7.1, with libdb4.8. Will an upgrade
> to either or both of these correct the issue?
Berkeley DB update you can clean up the root-cause. But be aware that
you should not mix-up different DB versions on the same host.