<?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: Issue with workaround for log4j for vRealize log insight in VMware Aria Operations for Logs Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893732#M2769</link>
    <description>&lt;P&gt;Thread reported so moderators know it should be moved to the area for vRealize Log Insight.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Feb 2022 17:15:01 GMT</pubDate>
    <dc:creator>scott28tt</dc:creator>
    <dc:date>2022-02-15T17:15:01Z</dc:date>
    <item>
      <title>Issue with workaround for log4j for vRealize log insight</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893523#M2767</link>
      <description>&lt;P&gt;Hi there, currently I'm using log insight&amp;nbsp;&lt;SPAN&gt;8.2.0-16957702. I'm trying the workaround found&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/87089" target="_self"&gt;here&lt;/A&gt;&amp;nbsp;for the issue regarding log4j. I'm having this issue with running the scripts. Every time&amp;nbsp;I try to run one of them I get the following error messages.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Searching for impacted .jar files. Please wait...&lt;BR /&gt;Found 1 impacted .jar files&lt;BR /&gt;Starting to patch impacted .jar files&lt;BR /&gt;patching -&amp;gt; /usr/lib/loginsight/application/3rd_party/apache-tomcat-8.5.57/log4j2/lib/log4j-core-2.13.3.jar&lt;BR /&gt;zip I/O error: No space left on device&lt;BR /&gt;zip error: Output file write failure (write error on zip file)&lt;BR /&gt;ERROR: Fail to Patch /usr/lib/loginsight/application/3rd_party/apache-tomcat-8.5.57/log4j2/lib/log4j-core-2.13.3.jar&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm not familiar with out log insight works. Is there a step I'm missing? If you need any more information, please let me know. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 18:46:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893523#M2767</guid>
      <dc:creator>rvazquez1</dc:creator>
      <dc:date>2022-02-14T18:46:17Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with workaround for log4j for vRealize log insight</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893713#M2768</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp; From your error message, you dont have free space on log insight.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Run df -h after logging into VRLI.&lt;/P&gt;&lt;P&gt;2) Figure out which file system is using 100% space.&lt;/P&gt;&lt;P&gt;3) cleanup the file system or add more space to appliance.&lt;/P&gt;&lt;P&gt;4) Retry the workaround for log4j.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 16:07:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893713#M2768</guid>
      <dc:creator>DeviVmware</dc:creator>
      <dc:date>2022-02-15T16:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with workaround for log4j for vRealize log insight</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893732#M2769</link>
      <description>&lt;P&gt;Thread reported so moderators know it should be moved to the area for vRealize Log Insight.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 17:15:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893732#M2769</guid>
      <dc:creator>scott28tt</dc:creator>
      <dc:date>2022-02-15T17:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with workaround for log4j for vRealize log insight</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893744#M2770</link>
      <description>&lt;P&gt;That was it. Thanks for the help!&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 18:04:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893744#M2770</guid>
      <dc:creator>rvazquez1</dc:creator>
      <dc:date>2022-02-15T18:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with workaround for log4j for vRealize log insight</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893927#M2771</link>
      <description>&lt;P&gt;Glad that worked. Please Mark my answer as Resolved to close this thread.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Feb 2022 17:00:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/Issue-with-workaround-for-log4j-for-vRealize-log-insight/m-p/2893927#M2771</guid>
      <dc:creator>DeviVmware</dc:creator>
      <dc:date>2022-02-16T17:00:30Z</dc:date>
    </item>
  </channel>
</rss>

