Results 1 to 10 of 10

Thread: Mac OSX install: Java errors & LDAP CA error

  1. #1
    jefbear is offline Starter Member
    Join Date
    Mar 2006
    Posts
    2
    Rep Power
    9

    Default Mac OSX install: Java errors & LDAP CA error

    Hello,
    I have tried a couple times to install Zimbra 301 GA a couple times and I am getting the same error over and over.

    1. I know that the DNS entries are ok for webgrinder.com because I can "ping webgrinder.com" and get responses:
    nothing:/ zimbra$ ping webgrinder.com
    PING webgrinder.com (150.101.89.81): 56 data bytes
    64 bytes from 150.101.89.81: icmp_seq=0 ttl=64 time=0.068 ms
    64 bytes from 150.101.89.81: icmp_seq=1 ttl=64 time=0.069 ms
    64 bytes from 150.101.89.81: icmp_seq=2 ttl=64 time=0.073 ms

    2. I DO have an MX record for webgrinder.com

    3. I'm not sure what the java errors I am getting mean...


    System:
    Mac Mini Core Duo Intel 1.66Mhz
    1GB RAM
    100 Gb HD

    ==========================================
    Last login: Thu Mar 16 15:05:26 on console
    Welcome to Darwin!
    nothing:~ jeff$ java -version
    java version "1.4.2_09"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-239)
    Java HotSpot(TM) Client VM (build 1.4.2-66, mixed mode)

    *****************
    FIXED JAVA VERSION
    *****************

    nothing:~ jeff$ su root
    Password:
    nothing:/Users/jeff root# cd /System/Library/Frameworks/JavaVM.framework/Versions/
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# ls
    1.3 1.4 1.5 A CurrentJDK
    1.3.1 1.4.2 1.5.0 Current
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# rm CurrentJDK
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# ls
    1.3 1.3.1 1.4 1.4.2 1.5 1.5.0 A Current
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# ln -s 1.5 CurrentJDK
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# ls
    1.3 1.4 1.5 A CurrentJDK
    1.3.1 1.4.2 1.5.0 Current
    nothing:/System/Library/Frameworks/JavaVM.framework/Versions root# exit
    exit
    nothing:~ jeff$ java -version
    java version "1.5.0_05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-84)
    Java HotSpot(TM) Client VM (build 1.5.0_05-51, mixed mode, sharing)

    *********
    SCRIPT
    *********

    nothing:/Users/jeff root# /opt/zimbra/libexec/zmsetup.pl
    Operations logged to /tmp/zmsetup.log.713
    Setting defaults...hostname: illegal option -- -
    usage: hostname [-s] [name-of-host]
    No results returned for A lookup of
    Checked nameservers:
    192.231.203.132
    192.231.203.3


    DNS ERROR resolving
    It is suggested that the hostname be resolveable via DNS
    Change hostname [Yes] Yes
    Please enter the logical hostname for this host webgrinder.com
    No results returned for MX lookup of webgrinder.com
    Checked nameservers:
    192.231.203.132
    192.231.203.3


    DNS ERROR resolving MX for webgrinder.com
    It is suggested that the domain name have an MX record configured in DNS
    Change domain name? [Yes] No
    Create Domain: [webgrinder.com]
    No results returned for MX lookup of webgrinder.com
    Checked nameservers:
    192.231.203.132
    192.231.203.3


    DNS ERROR resolving MX for webgrinder.com
    It is suggested that the domain name have an MX record configured in DNS
    Re-Enter domain name? [Yes] No
    Done
    Checking for port conflicts
    Checking ldap on :389...FAILED ( ldap_bind: Can't contact LDAP server (-1) )

    Main menu

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

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

    Please enter the ldap server hostname webgrinder.com

    Main menu

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

    Address unconfigured (**) items (? - help) 4

    Password for ldap server (min 6 characters): blah-blah

    Main menu

    1) Hostname: webgrinder.com
    2) Ldap master host: webgrinder.com
    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] Yes
    Save config in file: [/opt/zimbra/config.713]
    Saving config in /opt/zimbra/config.713...Done
    The system will be modified - continue? [No] Yes
    Operations logged to /tmp/zmsetup.log.713
    Setting local config values...Done
    Fetching CA from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException webgrinder.com:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException webgrinder.com:389)
    Done
    Creating server entry for webgrinder.com...Done
    Setting services on webgrinder.com...Done
    Setting up zimbra crontab...crontab: no crontab for zimbra
    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 (3.0.1_GA_160_UNKNOWN)
    The ADMIN EMAIL ADDRESS created (admin@webgrinder.com)

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


    Operations logged to /tmp/zmsetup.log.713


    Configuration complete - press return to exit


    nothing:/Users/jeff root# su - zimbra
    nothing:~ zimbra$ zmcontrol status
    Cannot determine services - exitingnothing:~ zimbra$
    nothing:~ zimbra$
    ================================

    The errors I see are:

    Checking ldap on :389...FAILED ( ldap_bind: Can't contact LDAP server (-1) )

    and

    Fetching CA from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException webgrinder.com:389)
    ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException webgrinder.com:389)



    Does anyone have any suggestions?
    Last edited by jefbear; 03-15-2006 at 10:42 PM.

  2. #2
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default

    Your new macbook pro isn't supported yet.

    Quote Originally Posted by jefbear
    Hello,
    I have tried a couple times to install Zimbra 301 GA a couple times and I am getting the same error over and over.

    1. I know that the DNS entries are ok for webgrinder.com because I can "ping webgrinder.com" and get responses:
    nothing:/ zimbra$ ping webgrinder.com
    PING webgrinder.com (150.101.89.81): 56 data bytes
    64 bytes from 150.101.89.81: icmp_seq=0 ttl=64 time=0.068 ms
    64 bytes from 150.101.89.81: icmp_seq=1 ttl=64 time=0.069 ms
    64 bytes from 150.101.89.81: icmp_seq=2 ttl=64 time=0.073 ms
    no, you don't know that - ping doesn't necessarily use DNS to resolve the host. Use the "host" command, or nslookup, to check your DNS entry.

    nothing:~ jeff$ java -version
    java version "1.5.0_05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-84)
    Java HotSpot(TM) Client VM (build 1.5.0_05-51, mixed mode, sharing)

    *********
    SCRIPT
    *********

    nothing:/Users/jeff root# /opt/zimbra/libexec/zmsetup.pl
    Operations logged to /tmp/zmsetup.log.713
    Setting defaults...hostname: illegal option -- -
    usage: hostname [-s] [name-of-host]
    That error makes me think you're installing on either
    A - a wacky version of OS X
    B - an intel box

    If A, which version? If B, then you can stop where you are, since the powerpc build won't run on intel.
    Checking ldap on :389...FAILED ( ldap_bind: Can't contact LDAP server (-1) )

    Main menu

    1) Hostname: webgrinder.com
    ** 2) Ldap master host: UNSET
    3) Ldap port: 389
    ** 4) Ldap password: UNSET
    r) Start servers after configuration yes
    s) Save config to file
    x) Expand menu
    q) Quit
    Again, I'm thinking unsupported platform - if it can't see that you've got the ldap package installed, it's probably checking in the wrong fashion, because it can't figure out the platform.

    Does anyone have any suggestions?
    Wait a week - intel build coming soon.

  3. #3
    jefbear is offline Starter Member
    Join Date
    Mar 2006
    Posts
    2
    Rep Power
    9

    Default

    Hi Marcmac,

    Well.. it's on a brand new Mac Mini Intel Core Duo.
    This IS the problem...

    Thanks for the (very) quick response mate.

    I will wait for the "intel" version next week (?)


    BTW: DNS info
    nothing:~ zimbra$ host webgrinder.com
    webgrinder.com has address 150.101.89.81



    Jeff

  4. #4
    FastEddy760 is offline Intermediate Member
    Join Date
    Feb 2006
    Location
    Southern Cal
    Posts
    22
    Rep Power
    9

    Default Its been a week! ;)

    Hello,

    I ran out an bought a Mini INTEL just for Zimbra. After running it on other servers for clients, its working great.

    Now I want it for myself, hence the new mini.

    Will it be any day now for the intel version?

  5. #5
    marcmac is offline Expert Member
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    13

    Default

    The next release will include an intel build.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  6. #6
    ScottH is offline Junior Member
    Join Date
    Aug 2006
    Posts
    8
    Rep Power
    9

    Default

    Quote Originally Posted by marcmac
    The next release will include an intel build.
    Is this Intel Core Duo compatibility thing now fixed?

    BTW, how are things working out on the Mac Mini Intel??? I'm considering the same.

    Scott

  7. #7
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    18

    Default

    Yes we have Intel builds, and got a few Mac Mini's for our build/test machines. They work fine just make sure you get at least 1GB of ram.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  8. #8
    ScottH is offline Junior Member
    Join Date
    Aug 2006
    Posts
    8
    Rep Power
    9

    Default

    Thanks Kevin.

  9. #9
    bunam is offline Intermediate Member
    Join Date
    Oct 2006
    Posts
    21
    Rep Power
    8

    Default

    i'v got the same trouble on a imac core2duo and with zcs-4.0.4_GA_457.MACOSXx86.dmg
    on a new install on 10.4.8

    i'v got a full qualified domain (with good MX too)

  10. #10
    bunam is offline Intermediate Member
    Join Date
    Oct 2006
    Posts
    21
    Rep Power
    8

    Default

    my fault !!

    i have used the migration assistant so i have some stuff in /opt/zimbra from previous mac (with a different domain)

    so i have removed /opt/zimbra + receip for simbra in /Library/receip/

    sorry for previous post

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  2. Postfix problem
    By jimbo in forum Administrators
    Replies: 46
    Last Post: 07-23-2007, 05:24 AM
  3. 3 testing: LDAP: 389 Failed when restore zimbra
    By victorLeong in forum Administrators
    Replies: 15
    Last Post: 05-24-2007, 06:45 AM
  4. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 10:30 PM
  5. M3 problem with shares
    By titangears in forum Users
    Replies: 4
    Last Post: 01-12-2006, 01:01 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
  •