Search the VMware Knowledge Base (KB)
View by Article ID

/storage/log directory is full in vCenter Server Appliance 6.0 (2143565)

  • 82 Ratings
Language Editions


You see that the /storage/log directory is highly utilized in an Embedded vCenter Server Appliance or Platform Controller Server Appliance 6.0.

Note: For additional symptoms and log entries, see the Additional Information section.


To work around the /storage/log directory full issue in vCenter Server Appliance, decrease the maximum backup size and the maximum backup index in the file.


This issue occurs due to an decrease in the SSO log files in the /storage/log directory. During the log rotation, the old log file is not compressed resulting in multiple large files in the  /storage/log directory.


This issue is resolved in VMware vCenter Server 6.0 Update 3, available at VMware Downloads

    To work around this issue, decrease the maximum backup size and the maximum backup index in the file.

    Note: In external Platform Service Controller (PSC) environments, log in to the Platform Service Controller instead.

    1. Log in to the vCenter Server Appliance or PSC console as root user. 
    2. Run this command to enable access the Bash shell:

      shell.set --enabled true

    3. Type shell and press Enter.
    4. Navigate to this directory:

      cd /usr/lib/vmware-sso/vmware-sts/webapps/sts/WEB-INF/classes/

    5. Run this command to back up the file:


    6. Open the file using a text editor.

    7. Locate the  log4j.appender.LOGFILE.MaxFileSize and  log4j.appender.LOGFILE.MaxBackupIndex parameters after this entry: 


    8. Change the value of parameters to 50 and 5 respectively:

      For example:


      Note: The default values are MaxFileSize=100MB and MaxBackupIndex=10.

    9. Locate the log4j.appender.PERFLOG.MaxBackupIndex parameter after this entry: 


    10. Change the value of parameter to 3.

      For example:


      Note: The default value is MaxBackupIndex=10.

    11. Run this command to restart the STS service:

      service vmware-stsd restart

    12. Navigate to:

      cd /storage/log/vmware/sso/ 

    13. Remove the old localhost_access_log,vmware-identity-sts and  vmware-identity-sts-perf log files by running these commands:

      rm localhost_access_log.*
      rm vmware-identity-sts.*
      rm vmware-identity-sts-perf.*

      Note: Restart the STS service again for new log files to be created in the  /storage/log directory.

    Additional Information

    You experience these additional symptoms:

    • When you run the  du -sh command in the /storage/log/vmware/sso directory, you see that several GB of space is utilized.
    • In the vSphere Web Client, you see the Alerts:

      • Available storage for logs /storage/log reached warning threshold - less then 30 % available space
      • Available storage for logs/storage/log reached critical threshold - less then 15 % available space
    To be alerted when this article is updated, click Subscribe to Document in the Actions box.


    /storage/partition, /storage/log/vmware/sso size is growing up very fast, available storage for logs, available storage for logs /storage/log reached warning

    See Also

    Update History

    2/24/2017 – Updated resolution with vCenter 6.0 U3 fix

    Request a Product Feature

    To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


    • 82 Ratings

    Did this article help you?
    This article resolved my issue.
    This article did not resolve my issue.
    This article helped but additional information was required to resolve my issue.

    What can we do to improve this information? (4000 or fewer characters)

    Please enter the Captcha code before clicking Submit.
    • 82 Ratings