ZCS 3.0 Beta 3 Update Released

[KevinH]

Just released the Beta 3 update. The build number is M4_41 but we are calling it "Beta 3 Update" since they're are just a few critical bugs fixed.

- IMAP lockups
- Unable to login on IE
- Some HMTL messages can't be read

In the Network edition there are also updates and fixes in the Outlook Connector. The release notes for both the OS and Network edition are attached.

Please take extra care if you are upgrading directly from M2 or have a multi-node systems. There are a couple extra steps covered in the Release Notes.

[chanck]

Hi Kevin,

On page 4 of the Network edition Release notes, both titles are "Single-Server Upgrade Steps From Beta2 to Beta3 Update".

Rgds,
Thomas

[KevinH]

Thanks. We'll fix it and update ASAP.

[FunkyPenguin]

Just tried to upgrade ZCS on my CentOS 4.2 box and it failed

Below is what was output to screen:

Upgrading from 3.0.0_M3_436 to 3.0.0_M4_41
Proceed with upgrade? [No] y
Sat Jan 21 19:32:04 2006: Stopping zimbra services
Sat Jan 21 19:32:09 2006: Checking mysql status
Sat Jan 21 19:32:10 2006: Starting mysql
Sat Jan 21 19:32:11 2006: Checking logger mysql status
Sat Jan 21 19:32:13 2006: Starting logger mysql
Sat Jan 21 19:32:15 2006: SELECT value FROM config WHERE name = 'db.version'
Sat Jan 21 19:32:16 2006: SELECT value FROM config WHERE name = 'db.version'
This appears to be 3.0.0_M3, with no schema upgrade needed
Sat Jan 21 19:32:18 2006: Stopping mysql
Sat Jan 21 19:32:22 2006: Stopping logger mysql
Checking 3.0.M1

Checking 3.0.0_M2

Checking 3.0.0_M3

Sat Jan 21 19:32:26 2006: Updating from 3.0.0_M3
Sat Jan 21 19:32:26 2006: Checking ldap status
Sat Jan 21 19:32:27 2006: Starting ldap
Sat Jan 21 19:32:34 2006: ldap startup failed with exit code 1
UPGRADE FAILED - exiting

Any ideas? I even tried to start the zimbra service manually by running "service zimbra start" - I know this isn't the recommended way of doing it, but I'm starting to panick as now my beautiful Zimbra setup has died and I need my mail/contacts/calendar back pronto and the following was spat at me

# service zimbra start
Host hawk.forcev.net
        Starting ldap...Done.
FAILED
db_recover: Finding last valid log LSN: file: 1 offset 2441978
db_recover: Recovery starting from [1][2441854]
db_recover: Recovery complete at Sat Jan 21 19:36:11 2006
db_recover: Maximum transaction ID 800001c0 Recovery checkpoint [1][2441978]
ERROR - failed to start slapd

[marcmac]

until we figure out why ldap isn't starting, you'll get nowhere. sh -x bin/ldap start may help, or ldd openldap/libexec/slapd

[FunkyPenguin]

I'm trying the upgrade again to see if it was just a temporary glitch, and noticed the following:

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
   HOSTNAME=hawk.forcev.net
   LDAPHOST=
   LDAPPORT=
   SNMPTRAPHOST=hawk.forcev.net
   SMTPSOURCE=admin@hawk.forcev.net
   SMTPDEST=admin@hawk.forcev.net
   SNMPNOTIFY=yes
   SMTPNOTIFY=yes
   LDAPROOTPW=wndwt7lyg
   LDAPZIMBRAPW=wndwt7lyg
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...

It then went on to spout:

Operations logged to /tmp/zmsetup.log.8869
Setting defaults...Setting defaults from existing config...Done
Checking for port conflicts
Starting ldap...Done
Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException hawk.forcev.net:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException hawk.forcev.net:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException hawk.forcev.net:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException hawk.forcev.net:389)
Done
Checking ldap on localhost:389...FAILED

Finally it brought the selection screen:

Main menu

   1) Hostname:                                hawk.forcev.net
   2) Ldap master host:                        hawk.forcev.net
   3) Ldap port:                               389
   4) Ldap password:                           set
   5) zimbra-ldap:                             Enabled
   6) zimbra-store:                            Enabled
        +Create Admin User:                    no
        +SMTP host:                            hawk.forcev.net
******* +Web server HTTP port:                 UNSET
******* +Web server HTTPS port:                UNSET
        +Web server mode:                      both
        +IMAP server port:                     143
        +IMAP server SSL port:                 993
        +POP server port:                      110
        +POP server SSL port:                  995
        +Use spell check server:               yes
        +Spell server URL:                     http://hawk.forcev.net:7780/aspell.php

   7) zimbra-mta:                              Enabled
   8) zimbra-snmp:                             Enabled
   9) zimbra-logger:                           Enabled
  10) zimbra-spell:                            Enabled
   r) Start servers after configuration        yes
   s) Save config to file
   x) Expand menu
   q) Quit

Address unconfigured (**) items or correct ldap configuration  (? - help)

Any reason why there is no LDAP info, and why HTTP/HTTPS ports require setting?

[FunkyPenguin]

marcmac,

Here are the outputs from your suggested commands:

# sh -x bin/ldap start
+ PID=
+ PIDFILE=/opt/zimbra/openldap/var/run/slapd.pid
+ mkdir -p /opt/zimbra/openldap/var/run/
+ case "$1" in
+ start
+ checkrunning
+ getpid
+ '[' -f /opt/zimbra/openldap/var/run/slapd.pid ']'
+ '[' x = x ']'
+ RUNNING=0
+ '[' 0 = 0 ']'
+ '[' -x /opt/zimbra/sleepycat/bin/db_recover ']'
+ /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data -v
db_recover: Finding last valid log LSN: file: 1 offset 2445064
db_recover: Recovery starting from [1][2444940]
db_recover: Recovery complete at Sat Jan 21 20:05:08 2006
db_recover: Maximum transaction ID 80000073 Recovery checkpoint [1][2445064]
+ sudo /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h 'ldaps:// ldap://:389/' -f /opt/zimbra/conf/slapd.conf
+ sleep 2
+ getpid
+ '[' -f /opt/zimbra/openldap/var/run/slapd.pid ']'
+ '[' x = x ']'
+ echo 'ERROR - failed to start slapd'
ERROR - failed to start slapd
+ echo ''

+ exit 1

# ldd openldap/libexec/slapd
        libsasl2.so.2 => /opt/zimbra/cyrus-sasl/lib/libsasl2.so.2 (0x002cc000)
        libssl.so.4 => /lib/libssl.so.4 (0x0086e000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x00783000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x005bc000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x005e9000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00413000)
        libdl.so.2 => /lib/libdl.so.2 (0x0053f000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00706000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x0071c000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x0056a000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00616000)
        libz.so.1 => /usr/lib/libz.so.1 (0x0057a000)
        /lib/ld-linux.so.2 (0x003fa000)

[marcmac]

When you upgrade, we start ldap, then get defaults from your ldap config - but if ldap refuses to start, we can't get that info (like, mail port).

what's that ldd returning?

[marcmac]

+ sudo /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h 'ldaps:// ldap://:389/' -f /opt/zimbra/conf/slapd.conf

ldd looks good. Try:

su - root
/opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h 'ldaps:// ldap://:389/' -f /opt/zimbra/conf/slapd.conf

I think there's a -d or -D option that will enable debugging for slapd. Could this be a cert problem? Did you have to remove the ldaps and hack the slapd.conf when you last installed?

[FunkyPenguin]

# ldd openldap/libexec/slapd
        libsasl2.so.2 => /opt/zimbra/cyrus-sasl/lib/libsasl2.so.2 (0x002cc000)
        libssl.so.4 => /lib/libssl.so.4 (0x0086e000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x00783000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x005bc000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x005e9000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00413000)
        libdl.so.2 => /lib/libdl.so.2 (0x0053f000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00706000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x0071c000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x0056a000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00616000)
        libz.so.1 => /usr/lib/libz.so.1 (0x0057a000)
        /lib/ld-linux.so.2 (0x003fa000)

[/QUOTE]

I've gone into the LDAP option in the menu and it has create domain as no is that correct?

P.S. - Can I change the SPAM/HAM training addresses and then send mail that is SPAM/HAM to those addresses?