<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: vsphere appliance log size in vCenter™ Server Discussions</title>
    <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377342#M43917</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;They are dump files from the Java processes crashing and restarting.&amp;nbsp; They're not needed for anything.&amp;nbsp; Ideally they should only be left enabled for troubleshooting/debugging, but VMware has no documentation for disabling them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 May 2017 16:37:07 GMT</pubDate>
    <dc:creator>Bleeder</dc:creator>
    <dc:date>2017-05-22T16:37:07Z</dc:date>
    <item>
      <title>vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377334#M43909</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I limit specific logging in vsphere server appliance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For instance i have the default /storage/log 10G partition with almost 1G in /storage/log/vmware/vsphere-client/logs/access/.&lt;/P&gt;&lt;P&gt;Those are uncompressed .txt files dating back from almost a year ago.&lt;/P&gt;&lt;P&gt;Shouldn't there be logrotate and compression in place??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already followed the KB#2143565 and loosened the sso logs. Is there a similar config for vsphere-client logging?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are also other massive logs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# du -h -d1 /storage/log/vmware/&lt;/P&gt;&lt;P&gt;1.2G&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/sso&lt;/P&gt;&lt;P&gt;15M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vsan-health&lt;/P&gt;&lt;P&gt;31M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmware-sps&lt;/P&gt;&lt;P&gt;4.0K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/netdumper&lt;/P&gt;&lt;P&gt;28K&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/rbd&lt;/P&gt;&lt;P&gt;3.9M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/applmgmt&lt;/P&gt;&lt;P&gt;93M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/invsvc&lt;/P&gt;&lt;P&gt;4.0K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vapi-endpoint&lt;/P&gt;&lt;P&gt;69M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmcad&lt;/P&gt;&lt;P&gt;520M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/sca&lt;/P&gt;&lt;P&gt;8.0K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmafd&lt;/P&gt;&lt;P&gt;698M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vsphere-client&lt;/P&gt;&lt;P&gt;1.3M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/rhttpproxy&lt;/P&gt;&lt;P&gt;72M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/cm&lt;/P&gt;&lt;P&gt;1008M&amp;nbsp;&amp;nbsp; /storage/log/vmware/vpxd&lt;/P&gt;&lt;P&gt;10M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/syslog&lt;/P&gt;&lt;P&gt;11M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vsm&lt;/P&gt;&lt;P&gt;519M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmafdd&lt;/P&gt;&lt;P&gt;32M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/iiad&lt;/P&gt;&lt;P&gt;12K&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vws&lt;/P&gt;&lt;P&gt;113M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/eam&lt;/P&gt;&lt;P&gt;4.0K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vctop&lt;/P&gt;&lt;P&gt;4.0K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/mbcs&lt;/P&gt;&lt;P&gt;60M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmdird&lt;/P&gt;&lt;P&gt;68K&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/rsyslogd&lt;/P&gt;&lt;P&gt;29M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vapi&lt;/P&gt;&lt;P&gt;818M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/cloudvm&lt;/P&gt;&lt;P&gt;2.0M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/psc-client&lt;/P&gt;&lt;P&gt;45M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/workflow&lt;/P&gt;&lt;P&gt;1.4G&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vdcs&lt;/P&gt;&lt;P&gt;79M&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/perfcharts&lt;/P&gt;&lt;P&gt;764K&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vpostgres&lt;/P&gt;&lt;P&gt;16K&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/vmdir&lt;/P&gt;&lt;P&gt;110M&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/cis-license&lt;/P&gt;&lt;P&gt;6.8G&amp;nbsp;&amp;nbsp;&amp;nbsp; /storage/log/vmware/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Aug 2016 15:04:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377334#M43909</guid>
      <dc:creator>vobelic</dc:creator>
      <dc:date>2016-08-09T15:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377335#M43910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Bump!&lt;/P&gt;&lt;P&gt;Sorry vobelic for not providing an answer, but i second that question.&lt;/P&gt;&lt;P&gt;Log rotation in vCSA 6.0 is just horribly broken.&lt;/P&gt;&lt;P&gt;Can someone from VMware shed some light on this issue? Will there be a fix for this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2016 11:44:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377335#M43910</guid>
      <dc:creator>softconsult</dc:creator>
      <dc:date>2016-08-26T11:44:09Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377336#M43911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any update on this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2016 18:06:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377336#M43911</guid>
      <dc:creator>vobelic</dc:creator>
      <dc:date>2016-09-14T18:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377337#M43912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to know too.&amp;nbsp; Every solution seems to involve increasing disk size, rather than addressing log file retention.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Brian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Oct 2016 14:52:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377337#M43912</guid>
      <dc:creator>OSUBrian</dc:creator>
      <dc:date>2016-10-12T14:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377338#M43913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, in addition to &lt;A href="https://kb.vmware.com/kb/2143565" title="https://kb.vmware.com/kb/2143565"&gt;/storage/log directory is full in vCenter Server Appliance 6.0 (2143565)&lt;/A&gt; mentioned by the OP for adjusting SSO logs rotation, there's also &lt;A href="https://kb.vmware.com/kb/2147261" title="https://kb.vmware.com/kb/2147261"&gt;Log rotation of the cloudvm-ram-size.log file is not working (2147261)&lt;/A&gt; for helping manage the cloudvm logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I really hope the logs rotation defaults are improved in vCSA 6.5. This is an &lt;EM&gt;appliance&lt;/EM&gt;, and an appliance ought not require this type of maintenance for the majority its users.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Feb 2017 16:11:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377338#M43913</guid>
      <dc:creator>jsprinkleISG</dc:creator>
      <dc:date>2017-02-09T16:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377339#M43914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would similarly like an answer to this question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The biggest consumer of space on mine are in /storage/log/vmware/perfcharts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;-rw-------&amp;nbsp; 1 perfcharts users&amp;nbsp; 39M May 13 13:35 java_pid45593.hprof&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;-rw-------&amp;nbsp; 1 perfcharts users 392M May 11 23:23 java_pid22560.hprof&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;-rw-------&amp;nbsp; 1 perfcharts users 742M May 10 01:10 java_pid757.hprof&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;-rw-------&amp;nbsp; 1 perfcharts users 742M May 11 01:33 java_pid58499.hprof&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;-rw-------&amp;nbsp; 1 perfcharts users 742M May&amp;nbsp; 3 02:09 java_pid56961.hprof&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea what these are, or if I can delete old ones manually so I can get the web clients to start?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 15:08:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377339#M43914</guid>
      <dc:creator>secureguy</dc:creator>
      <dc:date>2017-05-22T15:08:47Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377340#M43915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Java dump files..&amp;nbsp; I'll never understand why VMware leaves those enabled by default.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 15:12:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377340#M43915</guid>
      <dc:creator>Bleeder</dc:creator>
      <dc:date>2017-05-22T15:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377341#M43916</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You happen to know what they are for, or how I can turn them off?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 16:00:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377341#M43916</guid>
      <dc:creator>secureguy</dc:creator>
      <dc:date>2017-05-22T16:00:41Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377342#M43917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;They are dump files from the Java processes crashing and restarting.&amp;nbsp; They're not needed for anything.&amp;nbsp; Ideally they should only be left enabled for troubleshooting/debugging, but VMware has no documentation for disabling them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 16:37:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377342#M43917</guid>
      <dc:creator>Bleeder</dc:creator>
      <dc:date>2017-05-22T16:37:07Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377343#M43918</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok.&amp;nbsp; Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2017 16:51:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377343#M43918</guid>
      <dc:creator>secureguy</dc:creator>
      <dc:date>2017-05-22T16:51:27Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377344#M43919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2151394" title="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2151394"&gt;Large Java dump files created in the location /storage/log/vmware/perfcharts (2151394) | VMware KB&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Sep 2017 15:42:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377344#M43919</guid>
      <dc:creator>Gastbie</dc:creator>
      <dc:date>2017-09-15T15:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: vsphere appliance log size</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377345#M43920</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is, check this link: &lt;A href="https://kb.vmware.com/s/article/2147261"&gt;https://kb.vmware.com/s/article/2147261&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It might help - we were struggling with the same issue.&lt;/P&gt;&lt;P&gt;Also check the vCenter community.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;oliver g&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Aug 2018 23:11:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vsphere-appliance-log-size/m-p/1377345#M43920</guid>
      <dc:creator>oliver_g</dc:creator>
      <dc:date>2018-08-17T23:11:31Z</dc:date>
    </item>
  </channel>
</rss>

