<?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>question nifi-env.sh file is empty in 2.4.0. Upgrade issue in EKS in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/nifi-env-sh-file-is-empty-in-2-4-0-Upgrade-issue-in-EKS/m-p/411510#M253069</link>
    <description>&lt;P&gt;We are upgrading from 2.0.0 M4 to 2.4.0 in EKS via helm charts.&lt;BR /&gt;But encountering issue while running nifi.sh file. Nifi.sh file references nifi-env.sh which is empty. We are suspecting issue is with docker image of nifi.&lt;BR /&gt;&lt;BR /&gt;When we opened binary of nifi 2.4.0 which is downloaded locally from internet, I can see content inside nifi-env.sh.&amp;nbsp;&lt;BR /&gt;Same is not present inside EKS when we deploy nifi 2.4.0 docker image into EKS&lt;BR /&gt;&lt;BR /&gt;This is crashing our main container. Basically its not setting PID path.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 11:21:51 GMT</pubDate>
    <dc:creator>Chetan_mn</dc:creator>
    <dc:date>2025-07-15T11:21:51Z</dc:date>
    <item>
      <title>nifi-env.sh file is empty in 2.4.0. Upgrade issue in EKS</title>
      <link>https://community.cloudera.com/t5/Support-Questions/nifi-env-sh-file-is-empty-in-2-4-0-Upgrade-issue-in-EKS/m-p/411510#M253069</link>
      <description>&lt;P&gt;We are upgrading from 2.0.0 M4 to 2.4.0 in EKS via helm charts.&lt;BR /&gt;But encountering issue while running nifi.sh file. Nifi.sh file references nifi-env.sh which is empty. We are suspecting issue is with docker image of nifi.&lt;BR /&gt;&lt;BR /&gt;When we opened binary of nifi 2.4.0 which is downloaded locally from internet, I can see content inside nifi-env.sh.&amp;nbsp;&lt;BR /&gt;Same is not present inside EKS when we deploy nifi 2.4.0 docker image into EKS&lt;BR /&gt;&lt;BR /&gt;This is crashing our main container. Basically its not setting PID path.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 11:21:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/nifi-env-sh-file-is-empty-in-2-4-0-Upgrade-issue-in-EKS/m-p/411510#M253069</guid>
      <dc:creator>Chetan_mn</dc:creator>
      <dc:date>2025-07-15T11:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: nifi-env.sh file is empty in 2.4.0. Upgrade issue in EKS</title>
      <link>https://community.cloudera.com/t5/Support-Questions/nifi-env-sh-file-is-empty-in-2-4-0-Upgrade-issue-in-EKS/m-p/413543#M254122</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/109475"&gt;@Chetan_mn&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was checking and the entrypoint for this kind of scenarios should be start.sh, that should call everything you need to start it.&amp;nbsp;&lt;BR /&gt;&lt;A href="https://hub.docker.com/layers/apache/nifi/2.4.0/images/sha256-e8ca069f1533e6ee52d706fa3395ea16fe6f29468c7c6234a3f1c6232b912704" target="_blank"&gt;https://hub.docker.com/layers/apache/nifi/2.4.0/images/sha256-e8ca069f1533e6ee52d706fa3395ea16fe6f29468c7c6234a3f1c6232b912704&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Do you have any error log that can give us more clues here?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Feb 2026 22:38:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/nifi-env-sh-file-is-empty-in-2-4-0-Upgrade-issue-in-EKS/m-p/413543#M254122</guid>
      <dc:creator>vafs</dc:creator>
      <dc:date>2026-02-12T22:38:43Z</dc:date>
    </item>
  </channel>
</rss>

