Forum Discussion

LeeF99's avatar
LeeF99
Icon for Nimbostratus rankNimbostratus
Mar 16, 2016

What is logging to /var/log/sa6 on BIG-IP DNS and filling up /var/log partition?

I recently installed 4 x BIG-IP DNS virtual appliances and 3 months later all 4 of them starting alerting as the /var/log partition had completely filled up;

 

/dev/mapper/vg--db--sda-dat.log.1 485M 485M 0 100% /var/log

 

I tracked the main culprit down to files presents in the /var/log/sa6 directory;

 

-rw-r--r--. 1 root root 10200 2016-03-16 09:20 sa

 

-rw-r--r--. 1 root root 80961288 2016-01-18 15:05 sa.1

 

-rw-r--r--. 1 root root 0 2016-03-16 09:21 sa.1.gz

 

-rw-r--r--. 1 root root 129657856 2016-01-18 15:08 saxml

 

-rw-r--r--. 1 root root 5710091 2015-12-19 03:20 saxml.1

 

-rw-r--r--. 1 root root 0 2016-03-16 09:21 saxml.1.gz

 

I have tried to track down the process creating these files to no avail and the Internet or DevCentral doesn't appear to offer any information.

 

The saxml file just seems to contain virtual hardware details about the appliance (over and over again) and the sa file is a binary file but using the string command, I was able to see that it just seems to log details of the network adapters (over and over again).

 

Does anyone know what is creating these log files and more importantly is it safe to delete some or all of them to free up space. I appreciate that they will probably be recreated, so is there some way or stopping or slowing down their creation?

 

Thanks,

 

Lee.

 

2 Replies

  • These files are produced by the linux sar utility (system activity report) process. They're not big-ip specific, and contain historical data about system activity - cpu utilisation, memory usage, disk activity, etc.

     

    I'm not sure why you're seeing such large files, as that's not typical.

     

    You can delete them, as nothing uses them (yet). I recommend you open a support case to investigate this more thoroughly, as we'll need a qkview to start figuring it out.

     

  • Could you confirm if this was happening with the version 12.x?