Page 1 of 3 123 LastLast
Results 1 to 10 of 28

Thread: ZCS 3.0 Beta 3 Update Released

  1. #1
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default ZCS 3.0 Beta 3 Update Released

    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.
    Attached Files Attached Files
    Last edited by KevinH; 01-20-2006 at 09:59 AM.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  2. #2
    Join Date
    Oct 2005
    Posts
    56
    Rep Power
    10

    Default Mixing title

    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

  3. #3
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Thanks. We'll fix it and update ASAP.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  4. #4
    Join Date
    Dec 2005
    Location
    Peterborough, UK
    Posts
    140
    Rep Power
    9

    Exclamation Upgrade from M3_436 to M4_41 failed

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

    Below is what was output to screen:

    Code:
    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

    Code:
    # 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

  5. #5
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default ldap not starting

    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

  6. #6
    Join Date
    Dec 2005
    Location
    Peterborough, UK
    Posts
    140
    Rep Power
    9

    Question Possible cause?

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

    Code:
    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:

    Code:
    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:

    Code:
    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?

  7. #7
    Join Date
    Dec 2005
    Location
    Peterborough, UK
    Posts
    140
    Rep Power
    9

    Default Output from suggested commands

    marcmac,

    Here are the outputs from your suggested commands:

    Code:
    # 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
    Code:
    # 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)

  8. #8
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default ldap

    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?

  9. #9
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default starting ldap

    + 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?

  10. #10
    Join Date
    Dec 2005
    Location
    Peterborough, UK
    Posts
    140
    Rep Power
    9

    Default

    Code:
    # 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?

Similar Threads

  1. Trouble Sending mail - All Messages deferred!
    By SiteDiscovery in forum Administrators
    Replies: 7
    Last Post: 09-03-2009, 05:52 AM
  2. Update Received Date in Folder-Listing
    By Oswald-Kolle in forum Installation
    Replies: 25
    Last Post: 08-21-2007, 05:21 PM
  3. ZCS 3.2 Beta Available
    By KevinH in forum Announcements
    Replies: 31
    Last Post: 07-07-2006, 04:46 PM
  4. ZCS 3.0 Beta 3 Update 2 Released
    By KevinH in forum Announcements
    Replies: 2
    Last Post: 01-25-2006, 01:36 PM
  5. ZCS 3.0 Milestone 3(aka Beta 3) Released
    By KevinH in forum Announcements
    Replies: 26
    Last Post: 01-18-2006, 01:36 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •