Search found 36 matches
- Thu Mar 08, 2007 2:59 am
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
Isnt it caused by an authentication problem in LDAP? Is it possible that after the upgrade it cant understand the ldap user account used by Zimbra? Possible Encryption issue? I dont know. I'm just trying my luck. Anyone?
- Thu Mar 08, 2007 2:55 am
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
Does zimbra ldap save logs?
- Thu Mar 08, 2007 2:46 am
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[quote user="jholder"]Try this as root: iptables -t nat -F[/QUOTE] I did this. I tried opening another console while running the installation script, it seems that when the installer shuts down the zimbra mail, the ldap service was also stopped because i cant telnet to port 389 anymore. I ...
- Wed Mar 07, 2007 9:44 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
Does the installation script stop the ldap service during installation?
- Wed Mar 07, 2007 12:59 am
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[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....
- Tue Mar 06, 2007 11:51 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[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 iptab...
- Tue Mar 06, 2007 11:23 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[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?
- Tue Mar 06, 2007 10:57 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
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.Namin...
- Tue Mar 06, 2007 9:59 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[quote user="jholder"]We think that perhaps you may not have enough buffer space. This causes an error in creation of foreign constants. Take a look at /opt/zimbra/conf/my.cnf and set the innodb_buffer_pool_size = 1992294400[/QUOTE] Ok. I'll try. Thanks. I'll post whatever the results here
- Tue Mar 06, 2007 9:30 pm
- Forum: Installation and Upgrade
- Topic: 3.0 to 4.5.3 Upgrade failed (mysql error)
- Replies: 35
- Views: 5381
3.0 to 4.5.3 Upgrade failed (mysql error)
[quote user="jholder"]Hi Delt, I think it's important for you to understand that you are attempting to treat the symptoms, and not address the problem. I think your proposal may work, but the problem you should be concerned about is why the heck is your script failing. Can you post your /o...