Upgrade to 8.5 from 8.07 resulted in 150GB logfile

dragon2611 · Post by **dragon2611** » Thu Aug 28, 2014 3:08 am

Upgraded my small zimbra opensource edtion server from 8.07 to 8.5 last night.
It's a KVM VM running Centos 6.
Woke up this morning to find something had fallen over as I couldn't access the webUI, logged into the box to restart services and found one of the log files (I think it was zmswatch.out) had grown to over 150GB and eaten all the space on the VM's HDD
Since I had to leave to goto work and was in a hurry I deleted the log file which is less than ideal I know.
Before deleting the file I tailed it and got the following output
Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 549, <> line 444826599.

Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 559, <> line 444826599.

Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 566, <> line 444826599.

Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 589, <> line 444826599.

Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 549, <> line 444826600.

Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 559, <> line 444826600.

Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 566, <> line 444826600.

Use of uninitialized value $app in string eq at /opt/zimbra/libexec/zmlogger line 589, <> line 444826600.

Use of uninitialized value $msg in pattern match (m//) at /opt/zimbra/libexec/zmlogger line 549, <> line 444826601.

Use of uninitialized value
If the file starts growing exponentially again I'll try and capture the output/copy it off so I can provide more detail.

jorgedelacruz.es · Post by **jorgedelacruz.es** » Thu Aug 28, 2014 6:42 am

Hi dragon2611,

Tell us more about the upgrade process, did you check the integrity of the database? It looks so stragne, but maybe some of Zimbra employees can clarify more about the tail that you paste.
What do you have now in the log file? Is everything ok?
Best regards

15337Raunaq · Post by **15337Raunaq** » Thu Aug 28, 2014 7:42 am

Check https://bugzilla.zimbra.com/show_bug.cgi?id=95221

dragon2611 · Post by **dragon2611** » Thu Aug 28, 2014 9:27 am

I let it verify the database integrity during upgrade and it passed.
Since removing the log file and restarting the zimbra services I've yet to see a re-occurrence
du -hs /opt/zimbra/log

428M /opt/zimbra/log