[SOLVED] Zimbra Upgrade from 5.0.12 to 6.0.4

[folioguru]

We are currently running 5.0.12. According to the Zimbra 6.0.4 release notes:

Paths to getting on latest ZCS version:
6.0.x > 6.0.4
5.0.2 - 5.0.21 > 6.0.4
4.5.7 - 5.0.1 > 5.0.21 > 6.0.4
4.5.0 - 4.5.6 > 4.5.11 > 5.0.21 > 6.0.4
(LDAP replicas additional step when going 4.5 > 5.0)

I just want to verify: Does this mean we must first upgrade to 5.0.21 before upgrading to 6.0.4? Thanks for any assistance.

-ron

[mmorse]

5.0.12 can go directly to 6.0.4.

The line "5.0.2 - 5.0.21 > 6.0.4" means versions 5.0.2 through 5.0.21 can upgrade straight to 6.0.4 without an intermediate step.

As always be sure to backup. (Commercial certs tend to be the most common issue.)

[folioguru]

Went forward with install but immediately ran into this problem:
Checking for prerequisites...
FOUND: NPTL
FOUND: sudo-1.6.7p5-30.1.3
FOUND: libidn-0.5.6-1
FOUND: gmp-4.1.4-3
FOUND: compat-libstdc++-33-3.2.3-47.3
FOUND: /usr/lib/libstdc++.so.5
FOUND: /usr/lib/libstdc++.so.6
Checking for suggested prerequisites...
FOUND: perl-5.8.5
MISSING: sysstat does not appear to be installed.

###WARNING###

The suggested version of one or more packages is not installed.
This could cause problems with the operation of Zimbra.

Do you wish to continue? [N]

My question is: Will the Zimbra 5.0.21 upgrade install sysstat automatically? If so, then that's the route for us to go.

Ours is a Linux RHEL system with a minimal install of only what was needed to install Zimbra (2 years ago). We no longer have "up2date" subscription with RHEL. Not even gcc is installed, so we can't compile sysstat from scratch. So tried installing and executing "yum":

Dependencies Resolved

================================================== ===========================
Package Arch Version Repository Size
================================================== ===========================
Installing:
sysstat i386 5.0.5-25.el4 base 117 k

Transaction Summary
================================================== ===========================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 117 k
Is this ok [y/N]: Y
Downloading Packages:
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 443e1821


Public key for sysstat-5.0.5-25.el4.i386.rpm is not installed

If the Zimbra 5.0.21 upgrade will install this package, then that's what we'll do. Any suggestions welcomed. Thanks.

-ron

[phoenix]

Originally Posted by folioguru

Checking for suggested prerequisites...
FOUND: perl-5.8.5
MISSING: sysstat does not appear to be installed.

###WARNING###

The suggested version of one or more packages is not installed.
This could cause problems with the operation of Zimbra.

Do you wish to continue? [N]

My question is: Will the Zimbra 5.0.21 upgrade install sysstat automatically? If so, then that's the route for us to go.

That's a 'suggested' prerequisite not a 'required' one, if you don't install it you'll miss out on the statistics info but that's all that happens.

[folioguru]

Thanks. I got past that error by locating a sysstat rpm that installed on our system.

Got all the way through install with no apparent failures. Yet, now I can't get to our zimbra site. Here is the zmcontrol results:

[zimbra@zimbra bin]$ zmcontrol status
Host
antispam Running
antivirus Running
convertd Running
ldap Running
logger Running
mailbox Stopped
zmmtaconfig is running.
mailboxd is not running.
zmmailboxdctl is not running
mta Running
snmp Running
spell Running
stats Running
[zimbra@zimbra bin]$ ./zmmailboxdctl start
Starting mailboxd...done.
[zimbra@zimbra bin]$ zmcontrol status
Host
antispam Running
antivirus Running
convertd Running
ldap Running
logger Running
mailbox Stopped
zmmtaconfig is running.
mailboxd is not running.
zmmailboxdctl is not running
mta Running
snmp Running
spell Running
stats Running

Can't get mailboxd or zmmailboxdctl running. Any suggestions on what to do to resolve this? Thanks!

p.s. I did some research.

I tried the suggestions here, to no avail: Mailboxd fails to start

My mailboxd.out:

CompilerOracle: exclude com/zimbra/cs/session/SessionMap.putAndPrune
CompilerOracle: exclude com/zimbra/cs/mailbox/MailItem.delete
CompilerOracle: exclude org/apache/xerces/impl/XMLDocumentFragmentScannerImpl$FragmentContentDisp atcher.dispatch
0 INFO [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
Total time for which application threads were stopped: 0.0002110 seconds
Total time for which application threads were stopped: 0.0002120 seconds
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Fatal error: exception while binding to ports
java.net.SocketException: Unbound server sockets not implemented
at javax.net.ServerSocketFactory.createServerSocket(S erverSocketFactory.java:80)
at com.zimbra.common.util.NetUtil.newBoundServerSocke t(NetUtil.java:95)
at com.zimbra.common.util.NetUtil.bindServerSocket(Ne tUtil.java:163)
at com.zimbra.common.util.NetUtil.bindSslTcpServerSoc ket(NetUtil.java:54)
at com.zimbra.common.handlers.PrivilegedHandler.openP orts(PrivilegedHandler.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.xml.XmlConfiguration.call(XmlConfigura tion.java:542)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:252)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:214)
at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:974)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.start.Main.start(Main.java:441)
at org.mortbay.start.Main.main(Main.java:119)
Heap
par new generation total 139200K, used 12407K [0x86230000, 0x8f930000, 0x8f930000)
eden space 123776K, 10% used [0x86230000, 0x86e4de08, 0x8db10000)
from space 15424K, 0% used [0x8db10000, 0x8db10000, 0x8ea20000)
to space 15424K, 0% used [0x8ea20000, 0x8ea20000, 0x8f930000)
concurrent mark-sweep generation total 466944K, used 0K [0x8f930000, 0xac130000, 0xac230000)
concurrent-mark-sweep perm gen total 131072K, used 5745K [0xac230000, 0xb4230000, 0xb4230000)

I also did this:

su - zimbra
zmcontrol stop
netstat -an

Here is the output:

[zimbra@zimbra bin]$ netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address Stat
e
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LIST
EN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LIST
EN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LIST
EN
tcp 0 0 0.0.0.0:989 0.0.0.0:* LIST
EN
tcp 0 0 127.0.0.1:10025 127.0.0.1:34225 TIME
_WAIT
tcp 0 0 127.0.0.1:10025 127.0.0.1:34250 TIME
_WAIT
tcp 0 0 :::80 :::* LIST
EN
tcp 0 0 :::22 :::* LIST
EN
tcp 0 0 :::443 :::* LIST
EN
tcp 0 0 ::1:34311 ::1:34310 TIME
_WAIT
tcp 0 0 ::ffff:66.6.218.100:22 ::ffff:192.168.218.3:3044 ESTA
BLISHED
tcp 0 0 ::ffff:66.6.218.100:22 ::ffff:192.168.218.3:3067 ESTA
BLISHED
tcp 0 2308 ::ffff:66.6.218.100:22 ::ffff:192.168.218.3:2985 ESTA
BLISHED
udp 0 0 0.0.0.0:983 0.0.0.0:*

udp 0 0 0.0.0.0:986 0.0.0.0:*

udp 0 0 0.0.0.0:111 0.0.0.0:*

udp 0 0 0.0.0.0:631 0.0.0.0:*

Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 17174 /tmp/.gdm_socket
unix 2 [ ACC ] STREAM LISTENING 7297 /tmp/.font-unix/fs7100
unix 2 [ ACC ] STREAM LISTENING 17328 /tmp/.X11-unix/X0
unix 8 [ ] DGRAM 6705 /dev/log
unix 2 [ ACC ] STREAM LISTENING 7241 /dev/gpmctl
unix 2 [ ACC ] STREAM LISTENING 7080 /var/run/acpid.socket
unix 2 [ ACC ] STREAM LISTENING 7383 /var/run/dbus/system_bu
s_socket
unix 2 [ ] DGRAM 7525 @/var/run/hal/hotplug_s
ocket
unix 2 [ ] DGRAM 4338 @udevd
unix 2 [ ] DGRAM 90694
unix 3 [ ] STREAM CONNECTED 46830
unix 3 [ ] STREAM CONNECTED 46829
unix 3 [ ] STREAM CONNECTED 46828
unix 3 [ ] STREAM CONNECTED 46827
unix 3 [ ] STREAM CONNECTED 17718 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 17717
unix 3 [ ] STREAM CONNECTED 17716 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 17715
unix 3 [ ] STREAM CONNECTED 17681 /tmp/.font-unix/fs7100
unix 3 [ ] STREAM CONNECTED 17680
unix 3 [ ] STREAM CONNECTED 17685 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 17437
unix 3 [ ] STREAM CONNECTED 7524 /var/run/dbus/system_bu
s_socket
unix 3 [ ] STREAM CONNECTED 7523
unix 3 [ ] STREAM CONNECTED 7420 /var/run/dbus/system_bu
s_socket
unix 3 [ ] STREAM CONNECTED 7419
unix 2 [ ] DGRAM 7404
unix 3 [ ] STREAM CONNECTED 7386
unix 3 [ ] STREAM CONNECTED 7385
unix 2 [ ] DGRAM 7260
unix 2 [ ] DGRAM 7240
unix 2 [ ] DGRAM 7222
unix 3 [ ] STREAM CONNECTED 6941
unix 3 [ ] STREAM CONNECTED 6940
unix 2 [ ] DGRAM 6777
unix 2 [ ] DGRAM 6713

-ron

[phoenix]

What errors do you see in the log files? Was the certificate on this server up to date? If it's a self-signed certificate you may need to regenerate it.

[folioguru]

This is the error from zmmailboxd.out:

Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Fatal error: exception while binding to ports
java.net.SocketException: Unbound server sockets not implemented
at javax.net.ServerSocketFactory.createServerSocket(S erverSocketFactory.java:80)
at com.zimbra.common.util.NetUtil.newBoundServerSocke t(NetUtil.java:95)
at com.zimbra.common.util.NetUtil.bindServerSocket(Ne tUtil.java:163)
at com.zimbra.common.util.NetUtil.bindSslTcpServerSoc ket(NetUtil.java:54)
at com.zimbra.common.handlers.PrivilegedHandler.openP orts(PrivilegedHandler.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.xml.XmlConfiguration.call(XmlConfigura tion.java:542)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:252)
at org.mortbay.xml.XmlConfiguration.configure(XmlConf iguration.java:214)
at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:974)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.start.Main.start(Main.java:441)
at org.mortbay.start.Main.main(Main.java:119)

This is what is in zimbra.log:

Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: status requested
Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: assuming no other instance is running
Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: assuming no other instance is running
Jan 3 00:50:07 zimbra zmmailboxdmgr[15513]: no manager process is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: status requested
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: assuming no other instance is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: assuming no other instance is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16606]: no manager process is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: status requested
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: assuming no other instance is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: assuming no other instance is running
Jan 3 00:50:56 zimbra zmmailboxdmgr[16637]: no manager process is running
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: status requested
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: assuming no other instance is running
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: assuming no other instance is running
Jan 3 00:52:08 zimbra zmmailboxdmgr[17464]: no manager process is running
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: status requested
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: assuming no other instance is running
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: assuming no other instance is running
Jan 3 00:52:22 zimbra zmmailboxdmgr[18089]: no manager process is running
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: status requested
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: stale pid 9205 found in /opt/zimbra/log/zmmailboxd_manager.pid: No such process
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: assuming no other instance is running
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: assuming no other instance is running
Jan 3 00:52:23 zimbra zmmailboxdmgr[18119]: no manager process is running

[folioguru]

More complete version of zimbra.log after zmcontrol is used to restart zimbra is attached (I hope).

[Klug]

How old are your SSL certs and CA ?

[folioguru]

In reviewing Release Notes, the certificate was more than a year old. So I followed the instructions IN THE RELEASE NOTES and they failed. Apparently this failure has been around since 5.0.x and I do not understand why they have not been fixed.

Finally after another search on the failure to update certificates I was ended up at Recreating a Self-Signed SSL Certificate - Zimbra :: Wiki

Following step-by-step it was finally resolved.

My real concern as a VAR/HSP is why do we have to jump through these hoops, particularly with a major upgrade and know deployment issue. Please excuse the rant but this one seems like a no-brainer.

Appreciate the help.