Upgrade to Debian 5 with Zimbra 6.0

[Storm16]

I just wanted a quick sanity check before I jumped. I have Zimbra 5.0.16 running on a Debian 4 (etch) box. I have downloaded Zimbra 6.0.1, and want to upgrade, but at the same time, I want to upgrade the machine, since Debian 4 is extremely long in the tooth. Here is how I propose to do it:

1. Shut down Zimbra, back up my data stores, etc. (also disable auto startup of Zimbra)

2. Change /etc/apt/sources.list to point to lenny; apt-get dist-upgrade.

3. After the reboot, upgrade Zimbra.

Once everything is upgraded, Zimbra 6.0 should fire up without problems or data loss...

Anyone see any problems with this procedure?

Thanks,
--storm

[uxbod]

Just make sure you shutdown ZCS, and no zimbra processes are still running, and you backup the whole of /opt/zimbra and confirm that the backup is indeed valid.

[Storm16]

Just make sure you shutdown ZCS, and no zimbra processes are still running, and you backup the whole of /opt/zimbra and confirm that the backup is indeed valid.

I did this, did the dist-upgrade, and rebooted. When I then ran install.sh, I got the following:

...
Prerequisite check complete.
Checking current number of databases...
df: no file systems processed

Do you want to verify message store database integrity? [Y]
Verifying integrity of message store databases.  This may take a while.
Starting mysqld...done.
mysqld is alive
perl: symbol lookup error: /opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi/auto/IO/IO.so: undefined symbol: Perl_Tstack_sp_ptr
mysqld is alive
Stopping mysqld... done.
[root@merrimac zcs-6.0.1_GA_1816.DEBIAN5.20090911170746]#

I saw something similar when trying to install Zimbra 5.x on a lenny box, but since the 6.0 I am attempting to install is compiled against Debian 5 (lenny), shouldn't it work with the newer version of perl (5.10)?

Thanks,
--storm

[Storm16]

I did this, did the dist-upgrade, and rebooted. When I then ran install.sh, I got the following:

...
Prerequisite check complete.
Checking current number of databases...
df: no file systems processed

Do you want to verify message store database integrity? [Y]
Verifying integrity of message store databases.  This may take a while.
Starting mysqld...done.
mysqld is alive
perl: symbol lookup error: /opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi/auto/IO/IO.so: undefined symbol: Perl_Tstack_sp_ptr
mysqld is alive
Stopping mysqld... done.
[root@merrimac zcs-6.0.1_GA_1816.DEBIAN5.20090911170746]#

I saw something similar when trying to install Zimbra 5.x on a lenny box, but since the 6.0 I am attempting to install is compiled against Debian 5 (lenny), shouldn't it work with the newer version of perl (5.10)?

Thanks,
--storm

Anyone? Please?

[Hivos]

What does "perl -v" say? (srry for asking, but you can never be too sure ))

[Storm16]

What does "perl -v" say? (srry for asking, but you can never be too sure ))

Understood. No offense taken

[storm@merrimac ~]$ perl -v

This is perl, v5.10.0 built for i486-linux-gnu-thread-multi

Copyright 1987-2007, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

Which is pretty much what I expected from Debian lenny...

Looking at the error, it appears that it is not perl itself, but rather in one of the modules within Zimbra itself (which has not been upgraded).

Zimbra folks: Has this procedure ever been performed before? e.g. upgrading to 6, and upgrading to lenny on the same box? Where do I need to go from here? Would the upgrade complete if I bypass the message store database integrity? Or will I run into some other perl-related issue?

I would go ahead and try it, but the last upgrade didn't go well for me and I wound up losing about 2 months of email traffic because I had to roll back to an older backup of Zimbra, so I'm a little hesitant to just try to force the upgrade in place.

Thanks,
--vr

[Hivos]

Thanks for double-checking. I'm afraid I can't help you any further now but, since I also have a Debian Etch + Zimbra 6.0.1 install running, which I eventually wish to upgrade to Lenny, I'll try the procedure you followed in a test-environment. Might take a while though...

[Storm16]

It appears I fixed the problem. When upgrading from Debian 4 to Debian 5, do not check the message store integrity. The message store check uses the old perl libraries. I completed the upgrade and am waiting for the servers to start up.

Okay. The install worked, however, I am having a problem now with getting zmmailboxd to start. I followed some of the steps in [SOLVED] zmmailboxdctl is not running but nothing worked. I tried removing the pid files (in this case, zmmailboxd_manager and zmmailboxd_java) and restarting zmmailboxd, to no avail. I umounted and fscked the filesystem (reiser3), again, no bueno...So I rebooted.

Found another problem, Zimbra, when it modifies syslog-ng.conf, uses source(src). My source is s_all, so syslog was not starting therefore not creating /dev/log, which prevented zimbra from starting.

Once I got that straightened out, I am still not able to get zmmailboxd to start.

Any suggestions?

--Storm