Results 1 to 8 of 8

Thread: Upgrade: 4.5.5 -> 4.5.6 failed, LDAP/slapd issues

  1. #1
    Join Date
    Jul 2007
    Posts
    14
    Rep Power
    8

    Default Upgrade: 4.5.5 -> 4.5.6 failed, LDAP/slapd issues

    Hi,

    I attempted to upgrade to Zimbra 4.5.6 this morning. All went well until the install.sh script attempted to initialize the LDAP service, at which point things went haywire. We're running on RHEL 4 x64. Relevant output from the install script is copied below (long):

    --------------------------------------------------------------
    The system will be modified. Continue? [N] y

    Shutting down zimbra mail

    Backing up ldap


    Removing existing packages

    zimbra-ldap...done
    zimbra-logger...done
    zimbra-mta...done
    zimbra-snmp...done
    zimbra-store...done
    zimbra-spell...done
    zimbra-apache...done
    zimbra-core...done

    Removing deployed webapp directories
    Installing packages

    zimbra-core......zimbra-core-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-ldap......zimbra-ldap-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-logger......zimbra-logger-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-mta......zimbra-mta-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-snmp......zimbra-snmp-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-store......zimbra-store-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-apache......zimbra-apache-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done
    zimbra-spell......zimbra-spell-4.5.6_GA_1023.RHEL4_64-20070627170359.x86_64.rpm...done

    Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
    HOSTNAME=*****
    LDAPHOST=*****
    LDAPPORT=389
    SNMPTRAPHOST=*****
    SMTPSOURCE=*****
    SMTPDEST=*****
    SNMPNOTIFY=yes
    SMTPNOTIFY=yes
    LDAPROOTPW=*****
    LDAPZIMBRAPW=*****
    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...Restoring backup schedule...done
    Operations logged to /tmp/zmsetup.log.411
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd
    Setting defaults...Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd
    Done
    Setting defaults from existing config...Upgrading from 4.5.5_GA_838 to 4.5.6_GA_1023
    Stopping zimbra services
    Stop failed - exiting
    UPGRADE FAILED - exiting
    ------------------------------------------------------------------

    An additional log file, /tmp/zmsetup.log, is mentioned during the install. I've copied the relevant bits of that file below for reference:

    ------------------------------------------------------------------
    Getting installed packages
    checking isEnabled zimbra-core
    zimbra-core not in enabled cache
    enabled packages
    Getting local config zimbra_server_hostname
    Getting local config ldap_url
    zimbra_server_hostname contained in ldap_url checking ldap status
    Checking ldap status
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    Starting ldap
    *** Running as zimbra user: /opt/zimbra/openldap/sbin/slapindex -q -f /opt/zimbra/conf/slapd.conf
    could not stat config file "/opt/zimbra/conf/slapd.conf": No such file or directory (2)
    slapindex: bad configuration file!
    *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
    TLS: error:02001002:system library:fopen:No such file or directory bss_file.c:259
    TLS: error:20074002:BIO routines:FILE_CTRL:system lib bss_file.c:261
    TLS: error:140B0002:SSL routines:SSL_CTX_use_PrivateKey_file:system lib ssl_rsa.c:691
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd

    ldap_bind: Can't contact LDAP server (-1)
    ldap_bind: Can't contact LDAP server (-1)
    ldap_bind: Can't contact LDAP server (-1)
    ldap_bind: Can't contact LDAP server (-1)
    ldap_bind: Can't contact LDAP server (-1)
    ldap_bind: Can't contact LDAP server (-1)
    *** Running as zimbra user: /opt/zimbra/bin/ldap status
    *** Running as zimbra user: /opt/zimbra/bin/ldap start
    TLS: error:02001002:system library:fopen:No such file or directory bss_file.c:259
    TLS: error:20074002:BIO routines:FILE_CTRL:system lib bss_file.c:261
    TLS: error:140B0002:SSL routines:SSL_CTX_use_PrivateKey_file:system lib ssl_rsa.c:691
    main: TLS init def ctx failed: -1
    ERROR - failed to start slapd

    ldap startup failed with exit code 256
    ------------------------------------------------------------------

    This repeats several times. Are there other log files that I should be looking at? What additional information can I provide to help debug the issue?

    Thanks in advance.

  2. #2
    Join Date
    May 2007
    Location
    Zimbra
    Posts
    1,285
    Rep Power
    10

    Default More debugging

    What does:

    ls -l /opt/zimbra/conf/slapd.conf

    show?

    and

    ls -l /opt/zimbra/conf/slapd.crt
    ls -l /opt/zimbra/conf/slapd.key

    Thanks!

    --Quanah
    Quanah Gibson-Mount
    Server Architect
    Zimbra, Inc
    --------------------
    Zimbra :: the leader in open source messaging and collaboration

  3. #3
    Join Date
    Jul 2007
    Posts
    14
    Rep Power
    8

    Default

    In consultation with Zimbra support, the issue has been resolved. Thanks for your help.

  4. #4
    Join Date
    Jul 2007
    Location
    Ottumwa, IA
    Posts
    1
    Rep Power
    8

    Default Solution

    What was the solution to get 4.5.6 running?

  5. #5
    Join Date
    Jun 2007
    Location
    Philippines
    Posts
    193
    Rep Power
    8

    Default

    Quote Originally Posted by Daimyo View Post
    In consultation with Zimbra support, the issue has been resolved. Thanks for your help.
    Probably it would be better if you can share to the community how your problem was resolved.

    What do you think?

    Thank you in advance for your kindnes...

  6. #6
    Join Date
    Jul 2007
    Posts
    14
    Rep Power
    8

    Default

    Probably it would be better if you can share to the community how your problem was resolved.
    I would be more than happy to share, but the truth is that I don't know exactly what was broken or exactly what was done to fix it. Our Zimbra architecture is clustered across two hosts, and the upgrade was performed while the cluster was inactive (i.e. all Zimbra services were running on just one host, where the upgrade was performed). My understanding is that there were some issues with the slapd.crt and slapd.key files, but the repair work was done remotely by Zimbra support. I still don't know exactly what was done to remedy the problem.

  7. #7
    Join Date
    Jul 2007
    Posts
    8
    Rep Power
    8

    Unhappy ldap startup failed with exit code 256

    Hi! Again here because now I have this error message and the installation cannot continue because this error don't stop.

    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
    chown: cannot access `/opt/zimbra/tomcat/conf/keystore': No such file or directory
    chown: cannot access `/opt/zimbra/conf/smtpd.key': No such file or directory
    chown: cannot access `/opt/zimbra/conf/smtpd.crt': No such file or directory
    chown: cannot access `/opt/zimbra/conf/slapd.crt': No such file or directory
    chown: cannot access `/opt/zimbra/conf/perdition.pem': No such file or directory
    chown: cannot access `/opt/zimbra/conf/perdition.key': No such file or directory
    Operations logged to /tmp/zmsetup.log.27145
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Setting defaults...Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Done
    Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking for port conflicts
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256


    Thx

  8. #8
    Join Date
    Jul 2006
    Location
    Australia, ACT
    Posts
    197
    Rep Power
    9

    Talking Solution for RH5 - works for me :)

    Had the same problem on a Zimbra 4.55 to 4.56 upgrade on a Red Hat 5 server today. The solution was simply to:
    vi /etc/sudoers
    comment out: #Default requiretty

    Run the install.sh again or if the install is still running just wait till the LDAP start command is called again and it should all just start working.

    Checking the /tmp/install.log.2309 (Zimbra install / upgrade log) provided the vital information to work out what to do.

    (Might be useful if the Zimbra installer did a check for this requirement).


    Quote Originally Posted by gbajczman View Post
    Hi! Again here because now I have this error message and the installation cannot continue because this error don't stop.

    Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
    chown: cannot access `/opt/zimbra/tomcat/conf/keystore': No such file or directory
    chown: cannot access `/opt/zimbra/conf/smtpd.key': No such file or directory
    chown: cannot access `/opt/zimbra/conf/smtpd.crt': No such file or directory
    chown: cannot access `/opt/zimbra/conf/slapd.crt': No such file or directory
    chown: cannot access `/opt/zimbra/conf/perdition.pem': No such file or directory
    chown: cannot access `/opt/zimbra/conf/perdition.key': No such file or directory
    Operations logged to /tmp/zmsetup.log.27145
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Setting defaults...Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Done
    Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking for port conflicts
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256
    Checking ldap status
    Starting ldap
    ldap startup failed with exit code 256


    Thx
    Last edited by greenrenault; 08-04-2007 at 10:26 PM.

Similar Threads

  1. 4.5.4 -> 4.5.5 (Networkd Edition) Upgrade problems
    By spector@zeitgeist.com in forum Administrators
    Replies: 3
    Last Post: 10-18-2007, 06:06 AM
  2. 4.5.6 -> 5.0 Upgrade Problem :(
    By uxbod in forum Installation
    Replies: 3
    Last Post: 07-21-2007, 09:02 PM
  3. upgrade to 4.5.6 failed
    By dmore73 in forum Installation
    Replies: 1
    Last Post: 07-03-2007, 02:26 AM
  4. Lotus migration
    By babou in forum Migration
    Replies: 15
    Last Post: 03-05-2007, 10:33 PM
  5. Replies: 0
    Last Post: 01-13-2007, 03:10 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
  •