Yes, submit a case.
Yes, submit a case.
BLAME YOUR BOSS THEN!!!I did a copy but it freezed copying on /opt/zimbra/postfix/spool/
After an hour I stopped the copy process with ctrl/c. Because my boss wanted the mail system running.
So I have an partial copy. but not the whole thing. I know its stupid.
you could install a fresh working copy and then restore from your daily backup? i've never tried this before but assume it must work?I have a daily backup. But that is just the mails I think.
in the future, when you do an upgrade, always take a snapshot of /opt/zimbra. The easiest way is to stop zimbra, and do:
cd /opt; tar cf zimbra.tar zimbra
If you search the forums and the wiki there are alternatives using scripts and rsync, but nothing beats a simple tar.
This is probably related to:
Bug 26281 - Check Logger DB integrity and Connection Prior to Installing
Looks like you had a pre-existing logger condition that you probably didn't know about. This caused the upgrade to fail.
If you're on RHEL, just uninstall it:
rpm -qa | grep logger
Then rpm -e (package)
Then rerun the installer. That will get it working.
I am on UBUNTU 6
A submitted a case on zimbra...
It was sunday and 5 min. later I got a phonecall from the guys at zimbra to solve the problem.
That is what we call "EXCELLENT SERVICE".
He reinstalled the 5.0.2 version and restored a backup from 2 days ago.
He also said i'd better upgrade my RAM on my server (old server) 500 MB, now I've upgraded to 2 GB RAM and it runs smoothly..
Can I upgrade now to 5.0.4 or should I wait.
PS Thanks to everyone and to the zimbra team for the excellent service
i have NE 5.0.11, Centos 5.2, with logger stopped with the infamous gui error.
I follow this link
now, what can i do to avoid to rpm -e logger rpm packageCode:[01:01:04 zimbra@zimbra ~ ]$ logmysqladmin status Uptime: 181 Threads: 11 Questions: 1674 Slow queries: 0 Opens: 19 Flush tables: 1 Open tables: 13 Queries per second avg: 9.249 01:02:48 zimbra@zimbra ~ ]$ logmysql zimbra_logger ERROR 1040 (08004): Too many connections
and then reinstaling (./install.sh u mean, correct?)
i wonder why a so small number and I would know if i could increase it, changing it in my.logger.cnf, zmcontrol stop/start, then issueCode:[01:14:21 zimbra@zimbra ~ ]$ grep connections /opt/zimbra/conf/my.logger.cnf max_connections = 10
to investigare tables to be repaired.Code:logmysql zimbra_logger
what do u suggest?
Last edited by maumar; 12-05-2008 at 05:19 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)