Ajcody-Logger-Issues
![]() |
Logger Issues
You might want to cross review these other sections as well:
Actual Logger Issues Homepage
Please see Ajcody-Logger-Issues
Logger Not Working Or No Stats In Admin Console
Check the following log files first to gather some information:
- Make sure the /etc/hosts details make the actual hostname and the zmhostname output - if someone recently changed the hostname variables for this box, logger can be effected if done improperly and will not log the obvious issue.
- /tmp/logprocess.out
- /tmp/gengraphs.out
- /opt/zimbra/logger/db/data/<hostname>.err
- /var/log/zimbra/log (logswatch monitors this file)
- grep'ing for things such as:
egrep 'postfix|amavis|STATUS|DISK|QUEUE' /var/log/zimbra.log
- grep'ing for things such as:
- You might also want to look at the following directory:
- /opt/zimbra/logger/db/work/
- You should see data in here, gif and rrd files.
Then proceed with the following wiki pages, as ordered:
- Logger
- If you find that tables are in need of repair, also consult the following wiki:
- If all else fails, you can clear the old logger database and reinitalize it. Please see:
Large Logger Database Killing Performance Of ZCS
Review the following to see what might be best option for you:
- King0770-Notes#Logger_Issues_-_Improve_Disk_Utilization_for_the_logger_service
- Ajcody-Logger-Issues#Reinitializing_Logger_Database_From_Scratch
Reinitializing Logger Database From Scratch
This will effectively blow away your old logger database, allowing you to start over.
zmloggerctl stop cd /opt/zimbra/logger/db mv db db-old
- or remove it if your not worried about old directory being perserved
- rm -rf db
/opt/zimbra/libexec/zmloggerinit
- logger is probably running after this, but to make sure
zmloggerctl start
- Need to manually start this one though
zmlogswatchctl start
Turning Off Logger
To not have logger startup [ use `hostname` or type in hostname] :
zmprov ms `hostname` -zimbraServiceEnabled logger
To manually shutdown logger
zmloggerctl stop