Thanks for your answer. Is there a way to check the flags used during the compilation of cyrus-sasl package? I simply installed the package from the repository (yum install cyrus-sasl) but I guess this install only supports Berkeley DB…
I read the database recommended format is Berkeley DB; is there a tool or script available that can accomplish the conversion (gdbm -> berkeley)? Thanks, Olivier From: Cyrus-sasl <cyrus-sasl-bounces+klirstr=gmail....@lists.andrew.cmu.edu> on behalf of Ken Murchison <mu...@fastmail.com> Date: Friday, September 22, 2017 20:27 To: <cyrus-sasl@lists.andrew.cmu.edu> Subject: Re: Migrate SASLDB2 to a new server You have 2 options: - Make sure that SASL on the new machine is compiled to use gdbm for sasldb - Find a tool to migrate your gdbm database to whatever format SASL on the new machine expects On 09/22/2017 02:37 AM, Olivier wrote: I’m trying to migrate my database to a new Linux server (CentOS 6.9 x64). Old Server: Cyrus SASL 2.1.18 New Server: Cyrus SASL 2.1.23 I copied the database from the old server to the new server: /etc/sasldb2 But when I execute sasldblistusers2 I get below error: /etc/sasldb2: unexpected file type or format listusers failed # file /etc/sasldb2 /etc/sasldb2: GNU dbm 1.x or ndbm database, little endian Is there anything I’m missing? Is there a specific procedure to migrate the database to a new server? Thanks, Olivier -- Kenneth Murchison Cyrus Development Team FastMail Pty Ltd