Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 36

Thread: 3.0 to 4.5.3 Upgrade failed (mysql error)

  1. #11
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    10

    Default mysql error fixed. ldap problem occurs.

    Hi! The migration script worked after adjusting the innodb buffer pool size but the LDAP problem occured again (same issues i had before when upgrading to 4.5.1):
    Code:
    Wed Mar  7 04:30:05 2007: Updating from 3.0.1_GA
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    Wed Mar  7 04:30:18 2007: Checking 3.1.0_GA
    Wed Mar  7 04:30:18 2007: Updating from 3.1.0_GA
    Wed Mar  7 04:32:10 2007: Checking 3.1.1_GA
    Wed Mar  7 04:32:10 2007: Updating from 3.1.1_GA
    Wed Mar  7 04:32:10 2007: Checking 3.1.2_GA
    Wed Mar  7 04:32:10 2007: Updating from 3.1.2_GA
    Wed Mar  7 04:32:10 2007: Checking 3.1.3_GA
    Wed Mar  7 04:32:10 2007: Updating from 3.1.3_GA
    Wed Mar  7 04:32:10 2007: Checking 3.1.4_GA
    Wed Mar  7 04:32:10 2007: Updating from 3.1.4_GA
    Wed Mar  7 04:32:15 2007: Checking 3.2.0_M1
    Wed Mar  7 04:32:15 2007: Updating from 3.2.0_M1
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.na                                                                             ming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    Wed Mar  7 04:33:22 2007: Checking 3.2.0_M2
    Wed Mar  7 04:33:22 2007: Updating from 3.2.0_M2
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to get config) (cause: javax.nami                                                                             ng.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.na                                                                             ming.NamingException [LDAP: error code 80 - internal error])
    Wed Mar  7 04:33:32 2007: Checking 4.0.0_RC1
    Wed Mar  7 04:33:32 2007: Updating from 4.0.0_RC1
    Wed Mar  7 04:33:45 2007: Checking 4.0.0_GA
    Wed Mar  7 04:33:45 2007: Updating from 4.0.0_GA
    Wed Mar  7 04:33:45 2007: Checking 4.0.1_GA
    Wed Mar  7 04:33:45 2007: Updating from 4.0.1_GA
    Wed Mar  7 04:33:48 2007: Checking 4.0.2_GA
    Wed Mar  7 04:33:48 2007: Updating from 4.0.2_GA
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.na                                                                             ming.NamingException [LDAP: error code 80 - internal error])
    Wed Mar  7 04:33:54 2007: Checking 4.0.3_GA
    Wed Mar  7 04:33:54 2007: Updating from 4.0.3_GA
    Wed Mar  7 04:34:20 2007: Checking 4.0.4_GA
    Wed Mar  7 04:34:20 2007: Updating from 4.0.4_GA
    Wed Mar  7 04:34:20 2007: Checking 4.0.5_GA
    Wed Mar  7 04:34:20 2007: Updating from 4.0.5_GA
    Wed Mar  7 04:34:20 2007: Checking 4.1.0_BETA1
    Wed Mar  7 04:34:20 2007: Updating from 4.1.0_BETA1
    Wed Mar  7 04:34:20 2007: Migrating amavisd-new to version 2.4.3
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.4.1/db
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.4.1/.spamassassin
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.3.3/db
    Wed Mar  7 04:34:20 2007: Migrating amavis-new db from version 2.3.3 to 2.4.3
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.3.3/.spamassassin
    Wed Mar  7 04:34:20 2007: Migrating amavis-new .spamassassin from version 2.3.3                                                                              to 2.4.3
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.3.1/db
    Wed Mar  7 04:34:20 2007: Checking /opt/zimbra/amavisd-new-2.3.1/.spamassassin
    Wed Mar  7 04:34:20 2007: Checking 4.5.0_BETA1
    Wed Mar  7 04:34:20 2007: Updating from 4.5.0_BETA1
    Wed Mar  7 04:34:23 2007: Checking 4.5.0_BETA2
    Wed Mar  7 04:34:23 2007: Updating from 4.5.0_BETA2
    Wed Mar  7 04:34:23 2007: Checking 4.5.0_RC1
    Wed Mar  7 04:34:23 2007: Updating from 4.5.0_RC1
    ERROR: service.FAILURE (system failure: unable to list all COS) (cause: javax.na                                                                             ming.NamingException [LDAP: error code 80 - internal error])
    Wed Mar  7 04:34:30 2007: Failed to delete cn=timezones,cn=config,cn=zimbra: int                                                                             ernal error
    Wed Mar  7 04:34:30 2007: Checking 4.5.0_RC2
    Wed Mar  7 04:34:30 2007: Updating from 4.5.0_RC2
    Wed Mar  7 04:34:35 2007: Checking 4.5.0_GA
    Wed Mar  7 04:34:35 2007: Updating from 4.5.0_GA
    Wed Mar  7 04:34:35 2007: Checking 4.5.1_GA
    Wed Mar  7 04:34:35 2007: Updating from 4.5.1_GA
    Wed Mar  7 04:34:38 2007: Checking 4.5.2_GA
    Wed Mar  7 04:34:38 2007: Updating from 4.5.2_GA
    Wed Mar  7 04:34:38 2007: Checking 4.5.3_GA
    Wed Mar  7 04:34:38 2007: Updating from 4.5.3_GA
    Wed Mar  7 04:34:47 2007: Stopping ldap
    Upgrade complete
    Checking for port conflicts
    Starting ldap...Done
    Setting defaults from ldap...ERROR: service.FAILURE (system failure: unable to l                                                                             ookup server by name: stiimail.stii.dost.gov.ph message: [LDAP: error code 80 -                                                                              internal error]) (cause: javax.naming.NamingException [LDAP: error code 80 - int                                                                             ernal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup COS by name: default me                                                                             ssage: [LDAP: error code 80 - internal error]) (cause: javax.naming.NamingExcept                                                                             ion [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    ERROR: service.FAILURE (system failure: unable to lookup server by name: stiimai                                                                             l.stii.dost.gov.ph message: [LDAP: error code 80 - internal error]) (cause: java                                                                             x.naming.NamingException [LDAP: error code 80 - internal error])
    Done
    
    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
       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@stiimail.stii.dost.gov.ph
            +SMTP host:                            stiimail.stii.dost.gov.ph
    ******* +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
    
    Address unconfigured (**) items  (? - help)
    Here are my os configurations that I think are helpful in solving this issue:

    Code:
    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
    202.90.141.143          stiimail.stii.dost.gov.ph stiimail
    Code:
     cat /etc/redhat-release
    Fedora Core release 4 (Stentz)
    Code:
    cat /etc/resolv.conf
    search stii.dost.gov.ph
    nameserver 202.90.141.137
    Code:
    nslookup
    > stiimail.stii.dost.gov.ph
    Server:         202.90.141.137
    Address:        202.90.141.137#53
    
    Name:   stiimail.stii.dost.gov.ph
    Address: 202.90.141.143
    >
    How can I fix this? THanks

  2. #12
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    try this
    su -zimbra
    ldap start
    telnet

    stiimail.stii.dost.gov.ph 389

    Does it work?

  3. #13
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    I'm stupid. I bet the problem is iptables.
    I forgot that we were using them back then.

    Make sure that you have iptables stopped

    su -zimbra
    zmiptables -u

  4. #14
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    10

    Default

    Quote Originally Posted by jholder View Post
    I'm stupid. I bet the problem is iptables.
    I forgot that we were using them back then.

    Make sure that you have iptables stopped

    su -zimbra
    zmiptables -u
    Do I have to restore my backup first, then stop zmiptables, then do the upgrade? Or just re-run install.sh?

  5. #15
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Good question. I don't know. You're only the second user that I've seen upgrade from a 3.1 release

    I'd guess that zmiptables is probably stopped, and the script already exists, so I'd say just run the script.

    If it fails, or doesn't run, do a forums search on iptables.

    john

  6. #16
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    10

    Default

    Quote Originally Posted by jholder View Post
    Good question. I don't know. You're only the second user that I've seen upgrade from a 3.1 release

    I'd guess that zmiptables is probably stopped, and the script already exists, so I'd say just run the script.

    If it fails, or doesn't run, do a forums search on iptables.

    john
    Hi! I did the following:

    Code:
    su - zimbra
    [zimbra@stiimail ~]$ telnet stiimail.stii.dost.gov.ph:389
    stiimail.stii.dost.gov.ph:389/telnet: Name or service not known
    [zimbra@stiimail ~]$ telnet stiimail.stii.dost.gov.ph 389
    Trying 202.90.141.143...
    Connected to stiimail.stii.dost.gov.ph (202.90.141.143).
    Escape character is '^]'.
    ..then re-run install.sh script, im still having the same problems. I'll try to restore my backup then do the same process.

  7. #17
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default Confusion

    Sorry,
    By script, I meant the zmiptables -u script.

    Go ahead and run that.

  8. #18
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    10

    Default

    Quote Originally Posted by jholder View Post
    Sorry,
    By script, I meant the zmiptables -u script.

    Go ahead and run that.
    Er.. i dont seem to have zmiptables script

    Code:
    [root@stiimail store]# find / -name zmiptables
    find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver.  Automatically turning on find's -noleaf option.  Earlier results may have failed to include directories that should have been searched.
    Right now, I have a working zimbra 3.0 (restored from backup) and I can connect to ldap via telnet:

    Code:
    [root@stiimail store]# su - zimbra
    [zimbra@stiimail ~]$ telnet stiimail.stii.dost.gov.ph 389
    Trying 202.90.141.143...
    Connected to stiimail.stii.dost.gov.ph (202.90.141.143).
    Escape character is '^]'.
    What went wrong?

  9. #19
    Join Date
    Sep 2005
    Posts
    36
    Rep Power
    10

    Default

    Does the installation script stop the ldap service during installation?

  10. #20
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Try this as root:
    iptables -t nat -F

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. Replies: 18
    Last Post: 03-20-2006, 01:22 PM
  3. M3 problem with shares
    By titangears in forum Users
    Replies: 4
    Last Post: 01-12-2006, 12:01 PM
  4. Building native libraries on MacOS X
    By ajmas in forum Developers
    Replies: 3
    Last Post: 10-14-2005, 11:00 PM
  5. Insallation failed (Debian server)
    By popui007 in forum Installation
    Replies: 5
    Last Post: 09-29-2005, 02:27 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
  •