Re: [Marketing Mail] [Caution: Message contains Redirect URL content] Re: Migration from 2.5 to 3.4

On 15/09/2021 10:40 pm, Jim Wallis wrote:
> Can you use the procedure described in section 6 on page 
> https://www.cyrusimap.org/imap/download/upgrade.html#backup-and-copy-existing-data 
> of the upgrade guide?
>
> It is for the mail databases but assume it will work on cyrus-sasl 
> databases too?
>
> You need to run the database conversion (cvt_cyrusdb) on a copy of the 
> database on the old server before you copy it to the new server, 
> because the new one doesn't know how to deal with berkeley database 
> files to do the conversion. There is a man page for cvt_cyrusdb on the 
> website, and it should be installed on the server.


On the old server, running as root :

  /usr/pkg/cyrus/bin/cvt_cyrusdb /usr/pkg/etc/sasldb.bdb berkeley 
/usr/pkg/etc/newsasl.skiplist skiplist
Converting from /usr/pkg/etc/sasldb.bdb (berkeley) to 
/usr/pkg/etc/newsasl.skiplist (skiplist)
fatal error: can't open old database

I'll fix you ..

bash-4.3# ls -la /usr/pkg/etc/sasldb.bdb
-rw-rw-rw-  1 root  wheel  28672 Sep 16 09:46 /usr/pkg/etc/sasldb.bdb

Still no.  It didn't work as the cyrus user either.

Huh?  The file is a copy of the live one, not the actual live one, but 
it doesn't make any difference - I've tried that as well, with 
read/write perms for all.

On the old server,

bash-4.3# ./cvt_cyrusdb
Usage: ./cvt_cyrusdb [-C altconfig] <old db> <old db backend> <new db> 
<new db backend>
Usable Backends:  berkeley, berkeley-nosync, berkeley-hash, 
berkeley-hash-nosync, flat, skiplist, quotalegacy


I can't see why it won't operate?




>
> On 15/09/2021 12:59, Carl Brewer wrote:
>> I'm in the early stages of doing something similar, moving an old 
>> 2.4.x to 3.4, across operating systems too - from an old NetBSD 
>> server to a new FreeBSD 13 server. Lots of little, annoying changes.  
>> Also, sendmail to postfix!  Easy! Erm ...
>>
>> Anyway ...
>>
>> I've copied over my old sasldb password database but it doesn't seem 
>> to like it much. I can't log in using it.  My old server was set up 
>> with unix domain sep, maybe that's a problem? I'm kinda guessing ...
>>
>> Oddly, when I create a raw, new sasldb, it works, sorta - oddly 
>> enough, but reports that it's a berkeley DB, I thought this wasn't 
>> supported anymore?
>>
>>  # ls -la sasldb*
>> -rw-r-----  1 carl   wheel  28672 Sep 10 17:06 sasldb.db
>> -rw-r-----  1 cyrus  mail   28672 Sep 15 21:41 sasldb2.berkeleydb
>> -rw-------  1 cyrus  mail   16384 Sep 15 21:53 sasldb2.db
>> -rw-r-----  1 cyrus  mail   16384 Sep  9 18:44 sasldb2.db.fcs
>>
>> # file sasldb*
>> sasldb.db:          Berkeley DB 1.85 (Hash, version 2, native 
>> byte-order)
>> sasldb2.berkeleydb: Berkeley DB 1.85 (Hash, version 2, native 
>> byte-order)
>> sasldb2.db:         Berkeley DB 1.85 (Hash, version 2, native 
>> byte-order)
>> sasldb2.db.fcs:     Berkeley DB 1.85 (Hash, version 2, native byte-orde
>>
>> By "sorta" I can log in, but cannot create any mailboxes.  Cyrus has
>> write permission in /var/imap and /var/spool/imap (the right
>> directories according to the FreeBSD's locations in
>> cyrus.conf/imapd.conf)
>>
>> Is there some magic I can use to check the format of the copied over
>> sasldb database and mash it into shape so new saslauthd will read it?
>> Or at least check it and report meaningful errors?  I can create new
>> users if I have to, and get them all to reset their passwords, but I'd
>> prefer not to unless there's no alternate.
>>
>> Thanks!
>>
>> Carl
>>




------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T31d4933e422af363-M314cf8735c069b6a2fbe22a8
Delivery options: https://cyrus.topicbox.com/groups/info/subscription