vsphere appliance log size

[vobelic]

Hi,

How can I limit specific logging in vsphere server appliance?

For instance i have the default /storage/log 10G partition with almost 1G in /storage/log/vmware/vsphere-client/logs/access/.

Those are uncompressed .txt files dating back from almost a year ago.

Shouldn't there be logrotate and compression in place??

I already followed the KB#2143565 and loosened the sso logs. Is there a similar config for vsphere-client logging?

There are also other massive logs:

# du -h -d1 /storage/log/vmware/

1.2G    /storage/log/vmware/sso

15M     /storage/log/vmware/vsan-health

31M     /storage/log/vmware/vmware-sps

4.0K    /storage/log/vmware/netdumper

28K     /storage/log/vmware/rbd

3.9M    /storage/log/vmware/applmgmt

93M     /storage/log/vmware/invsvc

4.0K    /storage/log/vmware/vapi-endpoint

69M     /storage/log/vmware/vmcad

520M    /storage/log/vmware/sca

8.0K    /storage/log/vmware/vmafd

698M    /storage/log/vmware/vsphere-client

1.3M    /storage/log/vmware/rhttpproxy

72M     /storage/log/vmware/cm

1008M   /storage/log/vmware/vpxd

10M     /storage/log/vmware/syslog

11M     /storage/log/vmware/vsm

519M    /storage/log/vmware/vmafdd

32M     /storage/log/vmware/iiad

12K     /storage/log/vmware/vws

113M    /storage/log/vmware/eam

4.0K    /storage/log/vmware/vctop

4.0K    /storage/log/vmware/mbcs

60M     /storage/log/vmware/vmdird

68K     /storage/log/vmware/rsyslogd

29M     /storage/log/vmware/vapi

818M    /storage/log/vmware/cloudvm

2.0M    /storage/log/vmware/psc-client

45M     /storage/log/vmware/workflow

1.4G    /storage/log/vmware/vdcs

79M     /storage/log/vmware/perfcharts

764K    /storage/log/vmware/vpostgres

16K     /storage/log/vmware/vmdir

110M    /storage/log/vmware/cis-license

6.8G    /storage/log/vmware/

Thanks.

[softconsult]

Bump!

Sorry vobelic for not providing an answer, but i second that question.

Log rotation in vCSA 6.0 is just horribly broken.

Can someone from VMware shed some light on this issue? Will there be a fix for this?

[vobelic]

Any update on this?

[OSUBrian]

I would like to know too.  Every solution seems to involve increasing disk size, rather than addressing log file retention.

-Brian

[jsprinkleISG]

So, in addition to /storage/log directory is full in vCenter Server Appliance 6.0 (2143565) mentioned by the OP for adjusting SSO logs rotation, there's also Log rotation of the cloudvm-ram-size.log file is not working (2147261) for helping manage the cloudvm logs.

I really hope the logs rotation defaults are improved in vCSA 6.5. This is an appliance, and an appliance ought not require this type of maintenance for the majority its users.

[secureguy]

I would similarly like an answer to this question.

When the /storage/log directory fills, it brings down everything, and I haven't seen any alert or notification when it gets close to full.

The biggest consumer of space on mine are in /storage/log/vmware/perfcharts:

-rw-------  1 perfcharts users  39M May 13 13:35 java_pid45593.hprof

-rw-------  1 perfcharts users 392M May 11 23:23 java_pid22560.hprof

-rw-------  1 perfcharts users 742M May 10 01:10 java_pid757.hprof

-rw-------  1 perfcharts users 742M May 11 01:33 java_pid58499.hprof

-rw-------  1 perfcharts users 742M May  3 02:09 java_pid56961.hprof

Any idea what these are, or if I can delete old ones manually so I can get the web clients to start?

[Bleeder]

Java dump files..  I'll never understand why VMware leaves those enabled by default.

[secureguy]

You happen to know what they are for, or how I can turn them off?

[Bleeder]

They are dump files from the Java processes crashing and restarting.  They're not needed for anything.  Ideally they should only be left enabled for troubleshooting/debugging, but VMware has no documentation for disabling them.

[secureguy]

Ok.  Thanks.

[Gastbie]

I'm sure you've found this answer already but for others who are still looking - this link was the answer to this error for me.

Large Java dump files created in the location /storage/log/vmware/perfcharts (2151394) | VMware KB

[oliver_g]

There is, check this link: https://kb.vmware.com/s/article/2147261

It might help - we were struggling with the same issue.

Also check the vCenter community.

best,

oliver g