Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Installation zimbra Initializing ldap...failed. (28416)

  1. #1
    farrukh.nadeem is offline Starter Member
    Join Date
    Aug 2008
    Posts
    1
    Rep Power
    6

    Angry Installation zimbra Initializing ldap...failed. (28416)

    [root@mail1 libexec]# ./zmsetup.pl
    Operations logged to /tmp/zmsetup.01001900-0000153517324.log
    ERROR: service.FAILURE (system failure: unable to lookup server by name: mail1.solex.com.pk message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: mail1.solex.com.pk message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    Setting defaults...ERROR: service.FAILURE (system failure: unable to lookup server by name: mail1.solex.com.pk message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    done.
    Setting defaults from existing config...done.
    Checking for port conflicts
    Port conflict detected: 7306 (zimbra-store)
    Port conflict detected: 7307 (zimbra-store)
    Port conflicts detected! - Any key to continue
    ERROR: service.FAILURE (system failure: unable to lookup server by name: mail1.solex.com.pk message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    Saving config in /opt/zimbra/config.25532...done.
    Operations logged to /tmp/zmsetup.01001900-0000153517324.log
    Adding mail1.solex.com.pk to zimbraMailHostPool in default COS...ERROR: service.FAILURE (system failure: unable to lookup server by name: mail1.solex.com.pk message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    ERROR: service.FAILURE (system failure: unable to lookup COS by name: default message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    done.
    Setting Keyboard Shortcut Preferences...done.
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    prov> Setting up syslog.conf...ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    syslogd: no process killed
    Failed

    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 (5.0.8_GA_2462_UNKNOWN)
    The ADMIN EMAIL ADDRESS created (admin@mail1.solex.com.pk)

    Notify Zimbra of your installation? [Yes] no
    Notification skipped
    Starting servers...Unable to determine enabled services from ldap.
    done.
    Initializing Documents...ERROR: service.FAILURE (system failure: unable to lookup COS by name: default message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    failed to initialize documents...see logfile for details.
    ERROR: service.FAILURE (system failure: unable to list all domains) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    Restarting mailboxd...done.
    Setting up zimbra crontab...done.


    Moving /tmp/zmsetup.01001900-0000153517324.log to /opt/zimbra/log


    Configuration complete - press return to exit

  2. #2
    adeelarifbhatti is offline Advanced Member
    Join Date
    Feb 2009
    Posts
    188
    Rep Power
    6

    Lightbulb

    Hi,
    Can you ping mail1.solex.com.pk. I mean I hope your DNS has no issue.
    Had you changed the named of your system i.e. hostname after installing the zimbra?
    Regards
    Adeel
    Last edited by adeelarifbhatti; 07-03-2009 at 01:11 AM.

  3. #3
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Code:
    cat /etc/hosts
    cat /etc/resolv.conf
    dig solex.com.pk mx
    dig solex.com.pk any
    host `hostname` <- note backticks and not single quotes (type exactly as is)

  4. #4
    jor-el is offline Junior Member
    Join Date
    Jul 2009
    Posts
    5
    Rep Power
    6

    Question Same problem...

    Hi, I'm new to Zimbra(we still are in testing phases), and I have the same issue described above.

    During the installation it returns an error:
    Initializing ldap...failed. (28416)

    The Log has this "relevant"(just the failed status...wild guess) info:
    ** Retrieving CA private key from ldap...failed.
    ** Retrieving CA cert from ldap...failed.
    ** Retrieving server config key zimbraSSLCertificate...failed.
    ** Retrieving server config key zimbraSSLPrivateKey...failed.
    ** Saving server config key zimbraSSLPrivateKey...failed.
    ** Saving server config key zimbraSSLCertificate...failed.
    ** Saving server config key zimbraSSLPrivateKey...failed.
    Tue Jul 21 09:03:34 2009 failed. (28416)
    Configuration failed

    I've read a couple of threads and this info is a must, so here it is:

    # cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.

    127.0.0.1 localhost.localdomain localhost
    172.18.200.30 mail2.transactel.net mail2
    ::1 localhost6.localdomain6 localhost6

    ]# cat /etc/resolv.conf <-- we still are in testing phases so I have a local bind set up
    search transactel.netread
    #nameserver 172.18.200.79
    #nameserver 172.18.200.12
    nameserver 127.0.0.1

    # dig transactel.net mx

    ; <<>> DiG 9.3.4-P1 <<>> transactel.net mx
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45771
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;transactel.net. IN MX

    ;; ANSWER SECTION:
    transactel.net. 1500 IN MX 10 mail2.transactel.net.

    ;; AUTHORITY SECTION:
    transactel.net. 1500 IN NS mail2.transactel.net.

    ;; ADDITIONAL SECTION:
    mail2.transactel.net. 1500 IN A 172.18.200.130

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Jul 21 09:07:51 2009
    ;; MSG SIZE rcvd: 84

    ]# dig transactel.net any

    ; <<>> DiG 9.3.4-P1 <<>> transactel.net any
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18861
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

    ;; QUESTION SECTION:
    ;transactel.net. IN ANY

    ;; ANSWER SECTION:
    transactel.net. 1500 IN SOA transactel.net. admin.transactel.net. 10118 43200 3600 3600000 2592000
    transactel.net. 1500 IN NS mail2.transactel.net.
    transactel.net. 1500 IN MX 10 mail2.transactel.net.

    ;; ADDITIONAL SECTION:
    mail2.transactel.net. 1500 IN A 172.18.200.130

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Jul 21 09:08:11 2009
    ;; MSG SIZE rcvd: 126

    # host `hostname`
    mail2.transactel.net has address 172.18.200.130
    mail2.transactel.net mail is handled by 10 mail2.transactel.net.

    I guess it could be something boring for you but I appreciate any help.

    Regards,

    Jor-El.

  5. #5
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,499
    Rep Power
    56

    Default

    Either the IP address is wrong in your hosts file or the IP address is wrong in your A record, which is it?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  6. #6
    jor-el is offline Junior Member
    Join Date
    Jul 2009
    Posts
    5
    Rep Power
    6

    Talking Thanks!

    The IP in my hosts file(Feeling sooooo dumb right now!)......

    Thank you very much!, I swear I checked the IP addresses like 10 times and didn't notice!

    Anyway, thank you very much for your help, I'll start right away!.

    Best Regards.

    Jor-El.

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,499
    Rep Power
    56

    Default

    You're welcome, it's an easy one to miss.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    am_af is offline Starter Member
    Join Date
    Jul 2009
    Posts
    1
    Rep Power
    6

    Default

    i got same problem too..

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,499
    Rep Power
    56

    Default

    Quote Originally Posted by am_af View Post
    i got same problem too..
    Then post the information that was posted by jor-el (look at what's needed from pots #3) or at least give some hint as to what the problem might be, it's difficult to diagnose anything from a 'me too' comment.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    phillsky is offline New Member
    Join Date
    Aug 2009
    Posts
    3
    Rep Power
    5

    Default

    OK now it's my turn. I get the same error doing a clean install of 5.0.18_GA_3011.RHEL4
    Funny thing is that I get exactly the same errors with 5.0.11, 5.0.13 and 5.0.14. I have had Zimbra 5.0.14 up and running on this server a while ago. Something must have changed on the server, but I can't figure out what the change may be.

    -------------------------------------------------------------------------------------------------
    Setting local config values...done.
    Setting up CA...done.
    Deploying CA to /opt/zimbra/conf/ca ...done.
    Creating SSL certificate...done.
    Installing mailboxd SSL certificates...done.
    Initializing ldap...done.
    Setting replication password...done.
    Setting Postfix password...done.
    Setting amavis password...done.
    Setting nginx password...done.
    Saving CA in ldap ...done.
    Creating server entry for server.domain.com...done.
    Saving SSL Certificate in ldap ...done.
    Setting spell check URL...done.
    Setting service ports on server.domain.com...done.
    Adding redstone.home.unx.nu to zimbraMailHostPool in default COS...ERROR: service.FAILURE (system failure: unable to lookup server by name: server.domain.com message: [LDAP
    : error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
    ERROR: service.FAILURE (system failure: unable to lookup COS by name: default message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationExceptio
    n [LDAP: error code 49 - Invalid Credentials])

    -----------------------------------------------------------------------------------------

    And then a bit later.

    -----------------------------------------------------------------------------------------
    Initializing store sql database...done.
    Setting zimbraSmtpHostname for server.domain.com...done.
    Initializing logger sql database...done.
    Initializing mta config...done.
    Configuring SNMP...done.
    Setting services on server.domain.com...done.
    Setting up syslog.conf...ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials]
    )

    --------------------------------------------------------------------------------------------

    And at the end.

    ----------------------------------------------------------------------------------------------
    Installing common zimlets...
    com_zimbra_phone...failed. This may impact system functionality.
    com_zimbra_ymemoticons...failed. This may impact system functionality.
    com_zimbra_bulkprovision...failed. This may impact system functionality.
    com_zimbra_email...failed. This may impact system functionality.
    com_zimbra_url...failed. This may impact system functionality.
    com_zimbra_cert_manager...failed. This may impact system functionality.
    com_zimbra_local...failed. This may impact system functionality.
    com_zimbra_date...failed. This may impact system functionality.
    Finished installing common zimlets.
    ERROR: service.FAILURE (system failure: unable to lookup COS by name: default message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationExceptio n [LDAP: error code 49 - Invalid Credentials])
    Initializing Documents...failed to initialize documents...see logfile for details.
    ---------------------------------------------------------------------------------------------

    /etc/hosts contains the correct hostname and ip address.
    /etc/resolv.conf is correct
    dig server.domain.com mx returns the correct MX
    dig server.domain.com any returns the correct information.
    host `hostname` returns the correct information.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [SOLVED] Zimbra logwatch.
    By nishith in forum Administrators
    Replies: 5
    Last Post: 06-10-2009, 04:42 PM
  2. Major Issue - 5.0RC2 NE to 5.0GA NE failed
    By DougWare in forum Installation
    Replies: 7
    Last Post: 01-06-2008, 09:56 PM
  3. Unable to start tomcat
    By chanck in forum Administrators
    Replies: 11
    Last Post: 06-11-2006, 12:58 AM
  4. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 AM
  5. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 01:00 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
  •