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

Thread: LDAP Problem. Upgrading from 3.0 to 4.5 FAILED

  1. #1
    dealt is offline Active Member
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    9

    Default LDAP Problem. Upgrading from 3.0 to 4.5 FAILED

    Hi! running install.sh seems to be ok at first, it smoothly upgraded my mysql tables but when it came to ldap installation part, in warns with the following errors:

    "Setting defaults from ldap...ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimail.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimail.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])"

    Although the installation process continued, in the end it showed an incomplete configuration:

    Main menu

    1) Hostname: mymailhost.mydomain.com
    2) Ldap master host: mymailhost.mydomain.com
    3) Ldap port: 389
    4) Ldap password: set
    5) zimbra-ldap: Enabled
    6) zimbra-store: Enabled
    +Create Admin User: no
    +Enable automated spam training: yes
    ******* +Spam training user: UNSET
    ******* +Non-spam(Ham) training user: UNSET
    +Global Documents Account: wiki@mymailhost.mydomain.com
    +SMTP host: mymailhost.mydomain.com
    ******* +Web server HTTP port: UNSET
    ******* +Web server HTTPS port: UNSET
    +Web server mode: mixed
    +Enable POP/IMAP proxy: no
    ******* +IMAP server port: UNSET
    ******* +IMAP server SSL port: UNSET
    ******* +POP server port: UNSET
    ******* +POP server SSL port: UNSET
    +Use spell check server: yes
    +Spell server URL: http://stiimail.stii.dost.gov.ph: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


    What should I do to fix my upgrade? Im restoring my backup now. I hope everything goes well. Thanks

  2. #2
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Go ahead and restore to a backup, and do incremental upgrades.

    In your case, upgrade to 3.1

  3. #3
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,581
    Rep Power
    57

    Default

    Quote Originally Posted by dealt View Post
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimail.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimail.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])"
    Make sure that your /etc/hosts file is correct and DNS A & MX records are set-up correctly and point to your Zimbra server.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #4
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Good catch Bill.
    I missed that. I was thinking that this was another upgrade from 3.x


    john

  5. #5
    dealt is offline Active Member
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    9

    Default

    Quote Originally Posted by phoenix View Post
    Make sure that your /etc/hosts file is correct and DNS A & MX records are set-up correctly and point to your Zimbra server.
    Hi! Thanks for the reply. But arent those files correctly configured already since the system (3.0) is up and runing without problems before the upgrade? Anyway, what are the things that I should look for? We have a separate DNS server and resolves our zimbra fqdn correctly. Hosts file is ok. What am I missing?

  6. #6
    dealt is offline Active Member
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    9

    Default

    Quote Originally Posted by wannabetenor View Post
    Go ahead and restore to a backup, and do incremental upgrades.

    In your case, upgrade to 3.1
    Hello! Do you mean I have to upgrade first to 3.1 then to 3.1.1->3.1.2->....->4.5.1?

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

    Default

    Well, they should be set correctly but you are getting an error saying it can't find the server and we use DNS.

    What does the following return (run on the Zimbra server):

    Code:
    host `hostname`
    dig yourdomain any
    dig yourdomain mx
    Also post the details of your /etc/hosts file. I assume that you have disabled any firewall or SELinux on this server?

    Maybe the problem is that it takes a long time to look-up your domain? Look at this report - that took 161 seconds (when I ran it) and that's far too long.
    Last edited by phoenix; 02-09-2007 at 01:02 AM.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    dealt is offline Active Member
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    9

    Default

    Hi! I discovered few things during my first installation:

    First, resolv.conf is pointing to my zimbra server not to our DNS server (I thought that could've cause the error) I already fixed it

    Second, i do a 'zmcontrol stop' as zimbra user before upgrading. (I was thinking too that since I stopped the zimbra-ldap service, that would've caused the error) I didnt stop zimbra services again on my next attempt(s) of upgrade.

    Here's my setting
    Code:
    [root@stiimail zcs]# hostname
    stiimail.stii.dost.gov.ph
    
    [root@stiimail zimbra3.0_02062007]# dig stii.dost.gov.ph any
    
    ; <<>> DiG 9.3.1 <<>> stii.dost.gov.ph any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58520
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 2
    
    ;; QUESTION SECTION:
    ;stii.dost.gov.ph.              IN      ANY
    
    ;; ANSWER SECTION:
    stii.dost.gov.ph.       38398   IN      SOA     stiidoor.stii.dost.gov.ph. root.stii.dost.gov.ph. 2006120401 10800 3600 604800 38400
    stii.dost.gov.ph.       38398   IN      NS      stiidoor.stii.dost.gov.ph.
    stii.dost.gov.ph.       38398   IN      MX      10 stiimail.stii.dost.gov.ph.
    
    ;; ADDITIONAL SECTION:
    stiidoor.stii.dost.gov.ph. 38398 IN     A       202.90.141.137
    stiimail.stii.dost.gov.ph. 38398 IN     A       202.90.141.143
    
    ;; Query time: 1 msec
    ;; SERVER: 202.90.141.137#53(202.90.141.137)
    ;; WHEN: Fri Feb  9 11:47:29 2007
    ;; MSG SIZE  rcvd: 155
    
    
    [root@stiimail zimbra3.0_02062007]# dig stii.dost.gov.ph mx
    
    ; <<>> DiG 9.3.1 <<>> stii.dost.gov.ph mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19689
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
    
    ;; QUESTION SECTION:
    ;stii.dost.gov.ph.              IN      MX
    
    ;; ANSWER SECTION:
    stii.dost.gov.ph.       38398   IN      MX      10 stiimail.stii.dost.gov.ph.
    
    ;; AUTHORITY SECTION:
    stii.dost.gov.ph.       38398   IN      NS      stiidoor.stii.dost.gov.ph.
    
    ;; ADDITIONAL SECTION:
    stiimail.stii.dost.gov.ph. 38398 IN     A       202.90.141.143
    stiidoor.stii.dost.gov.ph. 38398 IN     A       202.90.141.137
    
    ;; Query time: 1 msec
    ;; SERVER: 202.90.141.137#53(202.90.141.137)
    ;; WHEN: Fri Feb  9 11:48:11 2007
    ;; MSG SIZE  rcvd: 114
    Here's the error im encountering:
    Code:
    Fri Feb  9 11:24:41 2007: Running /opt/zimbra/libexec/scripts/migrateLogger5-qid.pl
    Fri Feb  9 11:24:43 2007: SELECT value FROM config WHERE name = 'db.version'
    Fri Feb  9 11:24:44 2007: Verified schema version 4.
    Fri Feb  9 11:24:44 2007: Adding loghostname
    Fri Feb  9 11:24:44 2007: alter table mta add INDEX i_qid (qid);
    
    Fri Feb  9 11:24:46 2007: SELECT value FROM config WHERE name = 'db.version'
    Fri Feb  9 11:24:47 2007: Verified schema version 4.
    Fri Feb  9 11:24:47 2007: Updating logger DB schema version from 4 to 5.
    Fri Feb  9 11:24:47 2007: UPDATE zimbra_logger.config SET value = '5' WHERE name = 'db.version';
    
    Fri Feb  9 11:24:50 2007: Stopping logger mysql
    Fri Feb  9 11:25:08 2007: Checking ldap status
    Fri Feb  9 11:25:10 2007: Starting ldap
    Fri Feb  9 11:25:17 2007: Checking 3.0.M1
    Fri Feb  9 11:25:17 2007: Checking 3.0.0_M2
    Fri Feb  9 11:25:17 2007: Checking 3.0.0_M3
    Fri Feb  9 11:25:17 2007: Checking 3.0.0_M4
    Fri Feb  9 11:25:17 2007: Checking 3.0.0_GA
    Fri Feb  9 11:25:17 2007: Checking 3.0.1_GA
    Fri Feb  9 11:25:17 2007: Updating from 3.0.1_GA
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    
    Fri Feb  9 11:25:30 2007: Checking 3.1.0_GA
    Fri Feb  9 11:25:30 2007: Updating from 3.1.0_GA
    Fri Feb  9 11:27:28 2007: Checking 3.1.1_GA
    Fri Feb  9 11:27:28 2007: Updating from 3.1.1_GA
    Fri Feb  9 11:27:28 2007: Checking 3.1.2_GA
    Fri Feb  9 11:27:28 2007: Updating from 3.1.2_GA
    Fri Feb  9 11:27:28 2007: Checking 3.1.3_GA
    Fri Feb  9 11:27:28 2007: Updating from 3.1.3_GA
    Fri Feb  9 11:27:28 2007: Checking 3.1.4_GA
    Fri Feb  9 11:27:28 2007: Updating from 3.1.4_GA
    Fri Feb  9 11:27:33 2007: Checking 3.2.0_M1
    Fri Feb  9 11:27:33 2007: Updating from 3.2.0_M1
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    Fri Feb  9 11:28:44 2007: Checking 3.2.0_M2
    Fri Feb  9 11:28:44 2007: Updating from 3.2.0_M2
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.naming.NamingException [LDAP: error code 80 - internal error])
    Fri Feb  9 11:28:54 2007: Checking 4.0.0_RC1
    Fri Feb  9 11:28:54 2007: Updating from 4.0.0_RC1
    and by the way, why is it the resulting configuration will always use user@hostname.domainname format on addresses? shouldnt it be user@domainname only?

    Code:
    Main menu
    
       1) Hostname:                                stiimail.stii.dost.gov.ph
       2) Ldap master host:                        stiimail.stii.dost.gov.ph
       3) Ldap port:                               389
       4) Ldap password:                           set
       5) zimbra-ldap:                             Enabled
            +Create Domain:                        no
    
       6) zimbra-store:                            Enabled
            +Create Admin User:                    no
            +Enable automated spam training:       yes
            +Spam training user:                   3o03lmhbfu@stiimail.stii.dost.gov.ph
    ******* +Non-spam(Ham) training user:          UNSET
            +Global Documents Account:             wiki@stiimail.stii.dost.gov.ph
            +SMTP host:                            stiimail.stii.dost.gov.ph
            +Web server HTTP port:                 80
            +Web server HTTPS port:                443
            +Web server mode:                      mixed
            +Enable POP/IMAP proxy:                no
    ******* +IMAP server port:                     UNSET
    ******* +IMAP server SSL port:                 UNSET
    ******* +POP server port:                      UNSET
    ******* +POP server SSL port:                  UNSET
            +Use spell check server:               yes
            +Spell server URL:                     http://stiimail.stii.dost.gov.ph:7780/aspell.php
    
       7) zimbra-mta:                              Enabled
            +MTA Auth host:                        stiimail.stii.dost.gov.ph
            +Enable Spamassassin:                  yes
            +Enable Clam AV:                       yes
            +Notification address for AV alerts:   admin@stiimail.stii.dost.gov.ph
    
       8) zimbra-snmp:                             Enabled
            +Enable SNMP notifications:            yes
            +SNMP Trap hostname:                   stiimail.stii.dost.gov.ph
            +Enable SMTP notifications:            yes
            +SMTP Source email address:            admin@stiimail.stii.dost.gov.ph
            +SMTP Destination email address:       admin@stiimail.stii.dost.gov.ph
    
       9) zimbra-logger:                           Enabled
      10) zimbra-spell:                            Enabled
    
       c) Collapse menu
       r) Start servers after configuration        yes
       s) Save config to file
       q) Quit
    Thanks again for the help and suggestions.

  9. #9
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    I don't think that its communicating with LDAP.

  10. #10
    dealt is offline Active Member
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    9

    Default

    Quote Originally Posted by wannabetenor View Post
    I don't think that its communicating with LDAP.
    Oh.. .then what am i missing?

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. Upgrade: 4.5.5 -> 4.5.6 failed, LDAP/slapd issues
    By Daimyo in forum Installation
    Replies: 7
    Last Post: 08-04-2007, 09:23 PM
  2. Zimbra Install Problem - getDirectContext
    By bsimzer in forum Installation
    Replies: 27
    Last Post: 07-19-2007, 10:12 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. Lotus migration
    By babou in forum Migration
    Replies: 15
    Last Post: 03-05-2007, 10:33 PM
  5. Replies: 4
    Last Post: 11-15-2006, 12:16 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
  •