3.0 to 4.5.3 Upgrade failed (mysql error)

Ask questions about your setup or get help installing ZCS server (ZD section below).
dealt
Posts: 36
Joined: Fri Sep 12, 2014 9:56 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby dealt » Tue Mar 06, 2007 10:57 pm

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):

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:
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

 cat /etc/redhat-release

Fedora Core release 4 (Stentz)

cat /etc/resolv.conf

search stii.dost.gov.ph

nameserver 202.90.141.137

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


jholder
Zimbra Employee
Zimbra Employee
Posts: 4693
Joined: Fri Sep 12, 2014 10:00 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby jholder » Tue Mar 06, 2007 11:09 pm

try this

su -zimbra

ldap start

telnet
stiimail.stii.dost.gov.ph 389
Does it work?

jholder
Zimbra Employee
Zimbra Employee
Posts: 4693
Joined: Fri Sep 12, 2014 10:00 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby jholder » Tue Mar 06, 2007 11:13 pm

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
dealt
Posts: 36
Joined: Fri Sep 12, 2014 9:56 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby dealt » Tue Mar 06, 2007 11:23 pm

[quote user="jholder"]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[/QUOTE]
Do I have to restore my backup first, then stop zmiptables, then do the upgrade? Or just re-run install.sh?
jholder
Zimbra Employee
Zimbra Employee
Posts: 4693
Joined: Fri Sep 12, 2014 10:00 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby jholder » Tue Mar 06, 2007 11:27 pm

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
dealt
Posts: 36
Joined: Fri Sep 12, 2014 9:56 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby dealt » Tue Mar 06, 2007 11:51 pm

[quote user="jholder"]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[/QUOTE]
Hi! I did the following:
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.
jholder
Zimbra Employee
Zimbra Employee
Posts: 4693
Joined: Fri Sep 12, 2014 10:00 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby jholder » Tue Mar 06, 2007 11:54 pm

Sorry,

By script, I meant the zmiptables -u script.
Go ahead and run that.
dealt
Posts: 36
Joined: Fri Sep 12, 2014 9:56 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby dealt » Wed Mar 07, 2007 12:59 am

[quote user="jholder"]Sorry,

By script, I meant the zmiptables -u script.
Go ahead and run that.[/QUOTE]
Er.. i dont seem to have zmiptables script
[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:
[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?:confused:
dealt
Posts: 36
Joined: Fri Sep 12, 2014 9:56 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby dealt » Wed Mar 07, 2007 9:44 pm

Does the installation script stop the ldap service during installation?
jholder
Zimbra Employee
Zimbra Employee
Posts: 4693
Joined: Fri Sep 12, 2014 10:00 pm

3.0 to 4.5.3 Upgrade failed (mysql error)

Postby jholder » Wed Mar 07, 2007 10:09 pm

Try this as root:

iptables -t nat -F

Return to “Installation and Upgrade”

Who is online

Users browsing this forum: No registered users and 2 guests