 logger still not solved
ok it seems this is really not solved yet. Could be my fault or simply a bug in the logger.
This time I upgraded from Network Edition 5.0.12 to the latest 5.0.15.
In the beginning of the script it did an integrity check for the logger [I said Y]. It hung for almost 2 hours. So I stopped it and did what I did before:
"I stopped the script because it was stuck after waiting 2 hours I gave up. Then I went and killed all zimbra processes [yes stopping the script left a few things still doing something, (yes mainly logger stuff)].
Then I went to /var/log and renamed zimbra.log.
- then rpm -e zimbra-logger
I ran the installer again. This time it asked me if I wanted to install logger, so I said "Y"
The integrity check was good and the installer seemed to work fine this time."
My /var/log/zimbra.log was again really big and I renamed it. I am not sure if its not doing log rotation or if its logging everything.
Does anyone know where to get more info on the logger? it there a utility to review the logs [yes of course I can more or cat it but something more human would be nice] or where do we modify what is being logged?
Also how do I completely erase logger and start over. Because when I do a rpm -e on it it does remove it but the logs must still be somewhere because when I re-install my /var/log/zimbra.log [that I moved] again blots to around the same size as before. Except this time installations works fine [maybe its just skipping the integrity check...].
Someone on another posting suggested renaming the /opt/zimbra/logger directory, but I'm not sure if this is correct. I guess it would move the logger mysql tables forcing it to build new ones.
Anyways I am back in business till the next upgrade I guess. Just updating folks about possible logger problems.
Cheers  | 
Bugzilla
Wiki
Source
Linear Mode
