Log Files Not Shrinking Even After Being Archived Resulting in High Disk Space/Partition Usage

(Doc ID 1265513.1)

Last updated on OCTOBER 21, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 24-Feb-2013***

Symptoms

Log files on the Oracle Communications Network Charging and Control continue to grow despite the smsLogCleaner/acsLogCleaner archiving logs hourly.

Correlating the number of lines vs size of the log files does not match up:

smf_oper@SMS01:/IN/service_packages/SMS/tmp/archive> for LOG in `ls -rt *smsCdrBFTArchiver*` ; do
> echo "Lines: `wc -l $LOG | sed 's/^ *//g' | cut -d" " -f1` and Size: `ls -lh $LOG | awk '{print $5}'` for $LOG"
> done
Lines: 202 and Size: 60M for 201010272230smsCdrBFTArchiver.log.txt
Lines: 260 and Size: 60M for 201010272330smsCdrBFTArchiver.log.txt
Lines: 305 and Size: 60M for 201010280030smsCdrBFTArchiver.log.txt
...
Lines: 177 and Size: 63M for 201010291830smsCdrBFTArchiver.log.txt
Lines: 166 and Size: 63M for 201010291930smsCdrBFTArchiver.log.txt
Lines: 168 and Size: 63M for 201010292030smsCdrBFTArchiver.log.txt
...
Lines: 187 and Size: 65M for 201010312230smsCdrBFTArchiver.log.txt
Lines: 248 and Size: 65M for 201010312330smsCdrBFTArchiver.log.txt
Lines: 296 and Size: 65M for 201011010030smsCdrBFTArchiver.log.txt
...
Lines: 184 and Size: 67M for 201011021830smsCdrBFTArchiver.log.txt
Lines: 171 and Size: 67M for 201011021930smsCdrBFTArchiver.log.txt
Lines: 163 and Size: 67M for 201011022030smsCdrBFTArchiver.log.txt


So here it can be seen that irrespective of the number of lines in each log, it continues to grow in size over time.

When viewing the logs, we can see that the beginning of the large log files are full of non-readable characters:

smf_oper@SMS01:/IN/service_packages/SMS/tmp> less smsCdrBFTArchiver.log
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
...

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms