SSO Logs filling up mount point

[hath91]

I'm looking for some clarification on information found in VMware KB 2143565. The instructions state to change the numeric values in the following lines:

log4j.appender.LOGFILE.MaxFileSize

log4j.appender.LOGFILE.MaxBackupIndex

log4j.appender.PERFLOG.MaxBackupIndex

However, these lines are not present in the 'log4j.properties' file on this VCSA, version 6.0.0.30100.

The mount point is 10 GB in size and 100% utilized

Filesystem                            Size  Used Avail Use% Mounted on

/dev/sda3                              11G  5.6G  4.6G  56% /

udev                                  4.0G  164K  4.0G   1% /dev

tmpfs                                 4.0G  112K  4.0G   1% /dev/shm

/dev/sda1                             128M   41M   81M  34% /boot

/dev/mapper/core_vg-core               25G  3.1G   21G  14% /storage/core

/dev/mapper/log_vg-log                9.9G  9.8G     0 100% /storage/log

/dev/mapper/db_vg-db                  9.9G  313M  9.1G   4% /storage/db

/dev/mapper/dblog_vg-dblog            5.0G  187M  4.5G   4% /storage/dblog

/dev/mapper/seat_vg-seat              9.9G  513M  8.9G   6% /storage/seat

/dev/mapper/netdump_vg-netdump       1001M   18M  932M   2% /storage/netdump

/dev/mapper/autodeploy_vg-autodeploy  9.9G  165M  9.2G   2% /storage/autodeploy

/dev/mapper/invsvc_vg-invsvc          5.0G  167M  4.6G   4% /storage/invsvc

I have attached a copy of the log4j.properties file along with drive utilization of the /storage/log/vmware directory.

Any assistance or suggestion are greatly appreciated.

Regards,

[Lalegre]

That could be because as the KB says:

"This issue is resolved in VMware vCenter Server 6.0 Update 3"

But what you can try to do in order to workaround is to delete some logs and try increasing your vmdk size a little bit.

, available at VMware Downloads

To work around this issue, decrease the maximum backup size and the maximum backup index in the log4j.properties 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 log4j.properties file:
   
   cp log4j.properties log4j.properties.bak
   
6. Open the log4j.properties file using a text editor.
   
7. Locate the log4j.appender.LOGFILE.MaxFileSize and log4j.appender.LOGFILE.MaxBackupIndex parameters after this entry:
   
   log4j.appender.LOGFILE.File=${catalina.base}/logs/vmware-identity-sts.log
   
8. Change the value of parameters to 50 and 5 respectively:
   
   For example:
   
   log4j.appender.LOGFILE.MaxFileSize=50MB
   log4j.appender.LOGFILE.MaxBackupIndex=5
   
   Note: The default values are MaxFileSize=100MB and MaxBackupIndex=10.
   
9. Locate the log4j.appender.PERFLOG.MaxBackupIndex parameter after this entry:
   
   log4j.appender.PERFLOG.File=${catalina.base}/logs/vmware-identity-sts-perf.log
   
10. Change the value of parameter to 3.
    
    For example:
    
    log4j.appender.PERFLOG.MaxBackupIndex=3
    
    Note: The default value is MaxBackupIndex=10.
    
11. Navigate to: cd /storage/log/vmware/sso/

12. 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.*​

13. Run this command to restart the STS service:
    
    service vmware-stsd restart
    
    

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

---

Related 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 document is updated, click the Subscribe to Article link in the Actions boxvCenter Server Appliance 6.0 中的 /storage/log 目录已满
vCenter Server Appliance 6.0 の /storage/log ディレクトリがいっぱいになる

---

Update History

---

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

---

Keywords

---

/storage/partition, Platform Service Controller, vCenter Server

---

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.

Feedback

*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)

Email ID

Submit

Actions

Bookmark Article

---

Print Article

---

Subscribe to Article

Article : 2143565

Updated : Jun 5, 2018

---

Total Views : 81887

---

Categories :

How to

---

Language:

EnglishChinese (Simplified)

---

Product(s):

VMware vCenter Server Appliance

---

Product Version(s):

VMware vCenter Server Appliance 6.0.x

---

Permalink to: /storage/log directory is full in vCenter Server Appliance 6.0

[Lalegre]

Sorry i cannot edit my comment i did not mean to copy all the KB

[Vijay2027 · Accepted solution]

So you will have to edit the below lines to:

From log4j.appender.LOGFILE.RollingPolicy.maxIndex=10 to log4j.appender.LOGFILE.RollingPolicy.maxIndex=5

From log4j.appender.LOGFILE.TriggeringPolicy.MaxFileSize=100000000 to log4j.appender.LOGFILE.TriggeringPolicy.MaxFileSize=50000000

Make sure you take a backup copy of the config file.

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered

[Vijay2027]

Also, please be aware of the know issue as per

https://kb.vmware.com/s/article/2149278

[hath91]

Thank you for your response and help. Your response along with info found HERE

“/storage/log filesystem is low on disk space or nodes” warning on platform service controller – vCl...

I was able to clean up some of the SSO log file space and got it down to 1.7 GB available or 83% free.

Thanks again.