<?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: Unable to apply log4j vulnerability workaround on LCM in VMware Aria Suite Lifecycle Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882979#M229</link>
    <description>&lt;P&gt;Check if you have more than one .jar file in that folder.&lt;/P&gt;&lt;P&gt;Move the older Jar file in other folder and run. it works.&lt;/P&gt;&lt;P&gt;But remember if your version 8.4.x, then the jar file older than 8.4.x should&amp;nbsp; be removed.&lt;/P&gt;&lt;P&gt;in my case, the older jar file was 8.1.1 (e.g.&lt;SPAN&gt;vmlcm-service-8.1.1-SNAPSHOT.jar&lt;/SPAN&gt;)&lt;/P&gt;</description>
    <pubDate>Mon, 13 Dec 2021 15:55:34 GMT</pubDate>
    <dc:creator>Techstarts</dc:creator>
    <dc:date>2021-12-13T15:55:34Z</dc:date>
    <item>
      <title>Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882896#M226</link>
      <description>&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/87097" target="_blank"&gt;https://kb.vmware.com/s/article/87097&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I followed the instructions per the KB.&amp;nbsp; I get the following error when I attempt to run the script:&lt;/P&gt;&lt;P&gt;vmlcm-service-8.1.1-SNAPSHOT.jar: binary operator expected&lt;BR /&gt;vRSLCM services jar does not exist&lt;/P&gt;&lt;P&gt;Currently running&amp;nbsp;&amp;nbsp;vRSLCM 8.6.0.20&lt;/P&gt;</description>
      <pubDate>Sun, 12 Dec 2021 19:51:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882896#M226</guid>
      <dc:creator>BrianCoA</dc:creator>
      <dc:date>2021-12-12T19:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882945#M227</link>
      <description>&lt;P&gt;Having exactly the same issue.&lt;/P&gt;&lt;P&gt;Script immediately fails with the following;&lt;/P&gt;&lt;P&gt;./log4jfix.sh: line 4: [: vmlcm-service-8.1.1-SNAPSHOT.jar: binary operator expected&lt;BR /&gt;-bash: ./log4jfix.sh:: No such file or directory&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 06:01:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882945#M227</guid>
      <dc:creator>jlonsdale</dc:creator>
      <dc:date>2021-12-13T06:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882970#M228</link>
      <description>&lt;P&gt;Same here. Not working for me as well&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 09:44:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882970#M228</guid>
      <dc:creator>Techstarts</dc:creator>
      <dc:date>2021-12-13T09:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882979#M229</link>
      <description>&lt;P&gt;Check if you have more than one .jar file in that folder.&lt;/P&gt;&lt;P&gt;Move the older Jar file in other folder and run. it works.&lt;/P&gt;&lt;P&gt;But remember if your version 8.4.x, then the jar file older than 8.4.x should&amp;nbsp; be removed.&lt;/P&gt;&lt;P&gt;in my case, the older jar file was 8.1.1 (e.g.&lt;SPAN&gt;vmlcm-service-8.1.1-SNAPSHOT.jar&lt;/SPAN&gt;)&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 15:55:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882979#M229</guid>
      <dc:creator>Techstarts</dc:creator>
      <dc:date>2021-12-13T15:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882986#M230</link>
      <description>&lt;P&gt;Thank you, this worked for me, I also had two .jar files in /var/lib/vrlcm&lt;BR /&gt;&lt;BR /&gt;Relocated vmlcm-service-8.1.1-SNAPSHOT.jar to another folder and the script has run&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 10:52:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2882986#M230</guid>
      <dc:creator>LanceV1</dc:creator>
      <dc:date>2021-12-13T10:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2883046#M231</link>
      <description>&lt;P&gt;Removed the old .jar file and now getting this,,,,&lt;/P&gt;&lt;P&gt;zip warning: Local Entry CRC does not match CD: BOOT-INF/classes/log4j2.xml&lt;BR /&gt;(deflated 60%)&lt;BR /&gt;test of vmlcm-service-8.4.1-SNAPSHOT.jar OK&lt;BR /&gt;Zip action: 0&lt;BR /&gt;Waiting for vRLCM services to start.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 14:00:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2883046#M231</guid>
      <dc:creator>Steven1973</dc:creator>
      <dc:date>2021-12-13T14:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to apply log4j vulnerability workaround on LCM</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2883088#M232</link>
      <description>&lt;P&gt;The original KB has been updated to address this error.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;if you encounter the below error while executing the script rename the old version of vRSLCM SNAPSHOT.jar file and rerun the script./log4jfix.sh: line 4: [: vmlcm-service-8.1.1-SNAPSHOT.jar: binary operator expected&lt;BR /&gt;vRSLCM services jar does not exist&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Steps to rename&lt;/STRONG&gt;:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.change directory to /var/lib/vrlcm&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;cd /var/lib/vrlcm&lt;BR /&gt;2. Run the below command to rename the file&lt;BR /&gt;mv vmlcm-service-8.1.1-SNAPSHOT.jar vmlcm-service-8.1.1-SNAPSHOT_old.jar&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 15:52:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Suite-Lifecycle/Unable-to-apply-log4j-vulnerability-workaround-on-LCM/m-p/2883088#M232</guid>
      <dc:creator>BrianCoA</dc:creator>
      <dc:date>2021-12-13T15:52:55Z</dc:date>
    </item>
  </channel>
</rss>

