Results 1 to 5 of 5

Thread: Installation on debian

  1. #1
    jordg is offline Junior Member
    Join Date
    Feb 2006
    Posts
    6
    Rep Power
    9

    Default Installation on debian

    Hi,

    I am trying to install Zimbra on Debian/Testing however it seems that the ldap installation isn't taking.

    I had to make a couple of modifications to the installation to get it to install however were trivial.

    In bin/get_plat_tag.sh
    grep "testing/unstable" /etc/debian_version > /dev/null 2>&1
    if [ $? = 0 ]; then
    echo "DEBIAN3.1"
    exit 0
    fi

    util/packages/packeges.sh:
    $PACKAGEINST --ignore-depends=libgmp3 $file >> $LOGFILE 2>&1
    Debian/testing has a later library libgmpxx3

    Any help appreciated.

    Thanks

    Grahame Jordan

    Here are the final stages of the install

    Password for ldap server (min 6 characters): zimbra

    Main menu

    1) Hostname: ob1.theforce.com.au
    2) Ldap master host: ob1.theforce.com.au
    3) Ldap port: 389
    4) Ldap password: set
    r) Start servers after configuration yes
    s) Save config to file
    x) Expand menu
    q) Quit

    *** CONFIGURATION COMPLETE - press 'a' to apply
    Select from menu, or press 'a' to apply config (? - help) a
    Save configuration data to a file? [Yes]
    Save config in file: [/opt/zimbra/config.7989]
    Saving config in /opt/zimbra/config.7989...Done
    The system will be modified - continue? [No] Yes
    Operations logged to /tmp/zmsetup.log.7989
    Setting local config values...Done
    Setting up CA...Done
    Fetching CA from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    Done
    Creating server entry for ob1.theforce.com.au...Done
    Setting services on ob1.theforce.com.au...Done
    Setting up zimbra crontab...Done
    Setting up syslog.conf...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    Done

    You have the option of notifying Zimbra of your installation.
    This helps us to track the uptake of the Zimbra Collaboration Suite.
    The only information that will be transmitted is:
    The VERSION of zcs installed (4.0.0_RC1_272_UNKNOWN)
    The ADMIN EMAIL ADDRESS created (admin@theforce.com.au)

    Notify Zimbra of your installation? [Yes] no
    Notification skipped
    Starting servers...Done.


    Operations logged to /tmp/zmsetup.log.7989


    Configuration complete - press return to exit

  2. #2
    dijichi2 is offline OpenSource Builder & Moderator
    Join Date
    Oct 2005
    Posts
    1,176
    Rep Power
    11

    Default

    hi, i suspect this is because openldap that comes with zimbra is linked against openssl0.9.7, whereas unstable/testing has 0.9.8. thus slapd tls fails and the rest of the install cant talk to slapd. one fix is to do this, but you gotta be quick, or hope you have a slow box!:

    install, wait until it starts installing the packages. keep an eye out on /opt/zimbra/openldap/etc/openldap, as soon as it exists edit this file: /opt/zimbra/openldap/etc/openldap/slapd.conf and comment out the TLS lines at the bottom. if you do this in time, the install should then go smoothly!

  3. #3
    jordg is offline Junior Member
    Join Date
    Feb 2006
    Posts
    6
    Rep Power
    9

    Default

    Tried that with a script.
    while true; do if [ -e /opt/zimbra/openldap/etc/openldap/slapd.conf ]; then cd /opt/zimbra/openldap/etc/openldap/; mv slapd.conf slapd.conf.tmp; sed -e 's/^TLS/#TLS/g' slapd.conf.tmp > slapd.conf; echo "DONE"; break; fi; done

    Still the same:
    *** CONFIGURATION COMPLETE - press 'a' to apply
    Select from menu, or press 'a' to apply config (? - help) a
    Saving config in /opt/zimbra/config.27980...Done
    Operations logged to /tmp/zmsetup.log.27980
    Setting local config values...Done
    Fetching CA from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    Done
    Creating server entry for ob1.theforce.com.au...Done
    Setting services on ob1.theforce.com.au...Done
    Setting up zimbra crontab...Done
    Setting up syslog.conf...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException ob1.theforce.com.au:389)
    Done

  4. #4
    dijichi2 is offline OpenSource Builder & Moderator
    Join Date
    Oct 2005
    Posts
    1,176
    Rep Power
    11

    Default

    so if you look at /opt/zimbra/conf/slapd.conf.in and /opt/zimbra/conf/slapd.conf, have these lines been commented out?

  5. #5
    jordg is offline Junior Member
    Join Date
    Feb 2006
    Posts
    6
    Rep Power
    9

    Default

    Yes.
    This must happen fairly early after the file becomes available because the script is in a tight loop.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Reliable Zimbra installation on Debian Etch?
    By holunde in forum Installation
    Replies: 7
    Last Post: 06-21-2007, 12:01 AM
  2. OSE on Debian - installation troubleshooting
    By William in forum Installation
    Replies: 4
    Last Post: 01-24-2007, 11:51 PM
  3. Zimbra installation fails (Debian)
    By info in forum Installation
    Replies: 5
    Last Post: 01-01-2007, 04:12 AM
  4. Debian Installation Issue
    By Neil P in forum Installation
    Replies: 1
    Last Post: 11-10-2006, 02:51 PM
  5. Replies: 1
    Last Post: 02-17-2006, 07:59 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
  •