Disk Space being eaten up

[Paul_Pittsburgh]

I have been running Zimbra 5.0.11 for about a year and a half for an organization with about 150 users. I have noticed that my disk space is slowly getting used up. I don't think it is user mail. I was wondering if there are some log files or some other files that I should be cleaning up.

[phoenix]

Originally Posted by Paul_Pittsburgh

I have been running Zimbra 5.0.11 for about a year and a half for an organization with about 150 users. I have noticed that my disk space is slowly getting used up. I don't think it is user mail. I was wondering if there are some log files or some other files that I should be cleaning up.

Have you looked through you drives to see what's actually using the space?

[Paul_Pittsburgh]

No, unfortunately, I don’t have any historical data on the directories to see what has grown. When I took over this server, we were using about 17 percent of disk space and it has grown to 25. But I have never done much maintenance on the unix side, except for the ubuntu updates. So I guess my question is really if there are error log files, temp files, that kind of thing that I should be cleaning out, or other maintenance on the unix side that I should be doing.

[phoenix]

Originally Posted by Paul_Pittsburgh

No, unfortunately, I don’t have any historical data on the directories to see what has grown.

I was actually thinking more along the lines of checking your whole filesystem for large files (it may not be zimbra that's the problem), how about starting with the following:

df -h
find / -size +10000k -print0 | xargs -0 ls -l

The second command may take a while to run and you may want to change the size value that it lists (it's currently 10MB).

[raj]

in 5.x version some times logger eats up lots of space

du -sh /opt/zimbra/logger

following gives a rough estimate of your email store usage

du -sh /opt/zimbra/store

Raj

[Paul_Pittsburgh]

Thanks, I'll try those solutions and see what I find. Outside of the unix updates are there any other unix maintenance items that I should be performing on a monthly, weekly, daily basis to keep the box running?

[Paul_Pittsburgh]

These are some of the large files that I found, is it ok to remove these?

11G opt/zimbra/logger/db/data/zimbra_logger/amavis.MYD
1.7G opt/zimbra/logger/db/data/zimbra_logger/amavis.MYI
57G opt/zimbra/logger/db/data/zimbra_logger/mta.MYD
1.8G opt/zimbra/logger/db/data/zimbra_logger/raw_logs.MYD

[raj]

Hi..as suspected logger is the culprit here.
you cannnot just delete those files as is ..that will crash the logger service and will be hard to fix or reset.
please backup your system before doingg the following logger reset.
Open Source Edition Backup Procedure - Zimbra :: Wiki

RESET ZIMBRA LOGGER
when you do the following it may get stuck for long time on "rm -rf /opt/zimbra/logger/db/data/*" line coz you have huge filesizes.

su - zimbra
logmysql.server stop
logout
rm -rf /opt/zimbra/logger/db/data/*
chown zimbra:zimbra /opt/zimbra/logger/db/data
chmod 775 /opt/zimbra/logger/db/data
cd /opt/zimbra/libexec
./zmloggerinit
./zmfixperms --verbose
su - zimbra
zmlogswatchctl start
logout

Also once you have everything cleaned up in logger, its strongly suggested that you upgarde to new version.
soon you wont be able to upgarded from that old version and you will have to hunt down the downloads

Raj

[Paul_Pittsburgh]

Thanks, I will try this and let you know how it works. Also, I am planning to upgrade, that is what started me looking closely at getting all the mailboxes and data cleaned up for an upgrade.

[Paul_Pittsburgh]

Hi, I ran into some errors this morning when running this procedure and I am hoping you can help me with them. The Zimbra mail is running, it looks like the logger never came back.

Here is what I did and the errors I was encountering:

When I ran the ./zmloggerinit command I received the following output.

paul@mydomain.com:/opt/zimbra/libexec$ sudo ./zmloggerinit
* Creating required directories
* Creating database in /opt/zimbra/logger/db/data
* Starting logger_mysql server
* Loading schema /opt/zimbra/db/loggerdb.sql
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
* Setting random password for mysql root user in zimbra local config
* Setting random password for mysql zimbra user in zimbra local config
* Changing mysql root user password
/opt/zimbra/logger/mysql/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
* Changing mysql zimbra user password
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
**** PASSWORD CHANGE FAILED


I continued with the rest of the steps in the script.

After restarting Zimbra I got these messages

zmcontrol start
Host mydomain.com.
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...FAILED
Starting zmmtaconfig...zmmtaconfig is already running.
Starting amavisd...amavisd is already running.
Starting clamd...failed.


Starting snmp...Done.
Starting spell...Done.
Starting mta...Done.
Starting stats...Done.


I stopped Zimbra and started it again to the same set of errors.
I stopped Zimbra and rebooted my server hoping that would clean things up.

That fixed the clamd failed

When I ran a zmcontrol status I got this.

zmcontrol status
Host mydomain.com.
antispam Running
antivirus Stopped
zmclamdctl is not running
ldap Running
logger Stopped
logmysql.server is not running
zmlogswatchctl is not running
mailbox Running
mta Running
snmp Running
spell Running
stats Running


I logged into the admin console and received this error message box:

Zimbra Administration

Server error encountered.

And in the server status screen this error was showing:

Server status data is not available. To see the server status, logger service must be installed.

I checked around and mail did seam to be working.

I went back to the unix level and thinking that the logger did not start I ran the following command

logmysql.server start

and I got this response.

mysqld_safe already running with pid 6455

I looked to see what this was and got this:

paul@mydomain.com:~$ ps -ef | grep mysqld_safe
zimbra 6343 1 0 06:18 ? 00:00:00 /bin/sh /opt/zimbra/logger/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.logger.cnf --external-locking --log-error=/opt/zimbra/log/logger_mysql_error.log --ledir=/opt/zimbra/logger/mysql/libexec
zimbra 6486 1 0 06:18 ? 00:00:00 /bin/sh /opt/zimbra/mysql/bin/mysqld_safe --defaults-file=/opt/zimbra/conf/my.cnf --external-locking --log-error=/opt/zimbra/log/mysql_error.log --ledir=/opt/zimbra/mysql/libexec
paul 29699 28959 0 06:48 pts/1 00:00:00 grep mysqld_safe

Since the mail appears to be running I decided that I didn’t want to go any further without checking with some experts. Any thoughts on how to proceed?