warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree

Upgraded a server, and moved it to Arch Linux. And along the way the Postfix version was also upgraded. Suddenly there is a warning in the logfile: warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree. Turns out that is easy to fix.

I don’t know which version of Postfix the old server was using, it’s already wiped. The new version is 3.7.11.

1
2

# postconf mail_version
mail_version = 3.7.11

The configuration is rolled out using an Ansible role and a template. This template had a couple of entries which are no longer supported:

1
2

smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

The error in the logfile:

1
2

Jul 27 21:15:00 server postfix/tlsmgr[342431]: warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree
Jul 27 21:15:00 server postfix/tlsmgr[342431]: warning: btree:/var/lib/postfix/smtp_scache is unavailable. unsupported dictionary type: btree

I was curious and wanted to know which version of Postfix changed this. It is not a change in Postfix, rather this is a change in Arch Linux, the distribution removed support for BDB and switched the default to LMDB. The forum discussion cites license issues as reason for the change.

Now there is a post_upgrade notification, however I was installing the role on a fresh system, just using an existing template. Perks of using Ansible, I suppose.

Anyway, the necessary change is easy: replace btree with lmdb in the configuration, and run postconf again. That part is already handled in my Playbook if the configuration changes.

Header image

Image by OpenClipart-Vectors from Pixabay, modifications by me.

Comments

With an account on the Fediverse or Mastodon, you can respond to this post. Known replies are displayed below:

Load Comments from Fediverse

Note: This will load data from mastodon.social.

Learn how this is implemented here.