note - upgrading from i386 to amd64 sameversion.

2007-03-05 Thread Paul Pruett

Re: yelp...bit screwed, cyrus-imap not starting after switch to 64bit

i am surprised that you didn't reinstall. seems easy enough provided you 
backup your mail directories, or, better yet, you move them to a different 
machine and then mount them via NFS until you're ready to migrate them back 
to the local machine, assuming that's where you want them.

best of luck,
jake


thanks for pointers Steve and other
I think I made it.  WHOOT!,  sleep tonite!

As promised, a RECAP for other fools
googling about upgrading
existing computers from i386 to amd64

For OpenBSD 4.0 stable
the OpenBSD upgrade from cdrom from
i386 to amd64 was a success.

The script knew to take care of the bootblock,
and everything came up.

Using the port mergemaster I did not see anything
critical in /etc that was different from amd64 and i386.
A few files needed updating, but I think
that may be just that those etc files like disktab may
have changed between BASE and STABLE.

Of course all the i386 ports needed to be changed
to amd64 ports, and to be safer I deleted ports
before upgrade, then installed usint saved pkg_info
list I made before deleting.

The SNAFU was the data for some port packages,
but that would likely be a problem migrating
to a new install if you just copied the files
over.

The mysql server did not give issues, nor PHP5.

I did not need a port like mod_frontpage that
only emulates on 32bit, so that was good.
Gotta check to make sure your ports
are availabe on amd64 also.

Ughs...

The openldap server would not with same
database after changing.  Fortunately my
backupscript does a ldiff, so I had reinstall
use ldapad to import from the plain text backup
file. (note I had to delete misc commands in the
ldif before it would import...)


The cyrus-imap server sould not run with
same database.   The logs hinted that
the issue was when cyrus tried to
recover the data, ctl_cyrusdb -r
Having never had a serious cyrus-imapd
failure, I panicked, and recreated
doing the following inelegantly...
# kill cyrus master if working
mv /var/imap /var/imap-fubar
mkdir /var/imap
sudo -u _cyrus /usr/local/share/examples/cyrus-imapd/tools/mkimap
sudo -u _cyrus /usr/local/libexec/cyrus-imapd/ctl_mboxlist -u  mboxlist.txt
sudo -u _cyrus /usr/local/libexec/cyrus-imapd/reconstruct
#pray and restart cyrus master

I am sure their maybe a better way to
recontruct or avoid recontructing but the above
worked for me, EXCEPT the imap folders
for squirrelmail had to be resubscribed.


-epilogue-


I suspect that anywhere ad berkely datafile was created
under i386 it may have problems being used under amd64
unless exported on i386 and imported on amd64?

And I am extremely grateful to past admins in postings that
advised adding these things to backups:

/usr/local/sbin/slapcat -f /etc/openldap/slapd.conf \
 | /usr/bin/gzip  /var/openldap-data/backup.ldif.gz

su - _cyrus -c /usr/local/libexec/cyrus-imapd/ctl_mboxlist -d \
/var/imap/mboxlist.txt


And I close by sincerely hoping that the hangup/freezing
some see with 4.0 i386 on K8ahtlons is gone for good,
because using a current i386 on an older stable,
was not stabe :)


rock on.



Re: note - upgrading from i386 to amd64 sameversion.

2007-03-05 Thread David Terrell
On Mon, Mar 05, 2007 at 06:14:17PM +, Paul Pruett wrote:
 I suspect that anywhere ad berkely datafile was created
 under i386 it may have problems being used under amd64
 unless exported on i386 and imported on amd64?

Yes, that's how Berkeley DB works.

 And I am extremely grateful to past admins in postings that
 advised adding these things to backups:
 
 /usr/local/sbin/slapcat -f /etc/openldap/slapd.conf \
  | /usr/bin/gzip  /var/openldap-data/backup.ldif.gz

Best practice anywhere a binary data format is involved, but
doubly so with bdb.

Good luck.  And next time, set up a test box and pilot this 
stuff without hosing your users.  Also a best practice. :)

-- 
David Terrell
[EMAIL PROTECTED]
((meatspace)) http://meat.net/