Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Smart Protection Server log file takes up too much disk space

    • Updated:
    • 20 Jun 2014
    • Product/Version:
    • Smart Protection Server 3.0
    • Trend Micro Smart Protection Server 2.5
    • Trend Micro Smart Protection Server 2.6
    • Platform:
    • Linux - Red Hat RHEL 4 64-bit
    • Linux - Red Hat RHEL 5 64-bit
Summary

The Smart Protection Server (TMSPS) log files are taking up large disk space.

Details
Public
To resolve this issue:
Log in to the Smart Protection Server console and run this command:
- find / -size +103400k | xargs ls -laAh
It will list all the files that are using more than 100MB of disk space. If you found the following files using too much disk space, it is safe to manually delete them:
  • /var/log/lighttpd/access.log
  • /var/log/messages
  • /var/log/lighttpd/lwcs_access.log
  • /var/tmcss/tmp/*.blob
Access.log is using a lot of space
In case you notice that access.log is growing beyond 1GB in terms of disk usage, perform the following steps to ensure the log is rotated periodically:
  1. Check the /etc/logrotate.d/ folder. It must contain only the following files:
    • jetty
    • lighttpd
    • notifydbg
    • rpm
    • snmpd
    • syslog
    • yum
  2. Delete any files that are not supposed to be under this directory.
  3. Run the logrotate command and check if it decreased the size of the access.log file:
    - logrotate -vf /etc/logrotate.conf  
Blob files take too much disk space.
Blob files are generated by the Smart Feedback system and according to SEG, it's a known bug in TMSPS. The Blob file is mainly used for debugging purposes, consumes high bandwidth or traffic, and causes the TMSPS web console to be unresponsive. All other TMSPS services (reputation and update) can be compromised as well.
  1. Check the /var/tmcss/tmp/*.blob. If there are a lot of blob files, it is a known defect in Smart Protection Server and will be fixed in the future versions.
  2. Run this command to delete all the .blob files:
    - rm *.blob
  3. Turn off Smart Feedback in the Smart Protection Server web console. Go to Smart Protection > Smart Feedback.
    Note: If SPS is running on version 2.0, make sure to apply the critical patch tmsps-os-service-patch-2.0-1100.x86-64.tar. This patch contains the fix for the Blob issue. If this patch is applied, there's no need to turn off the Smart Feedback.
Premium
Internal
Rating:
Category:
Configure
Solution Id:
1057649
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.