<?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 Ni Fi Installed in VMWare CentOs and URL access error in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ni-Fi-Installed-in-VMWare-CentOs-and-URL-access-error/m-p/107733#M30108</link>
    <description>&lt;P&gt;Hi All &lt;/P&gt;&lt;P&gt;Perhaps an apache mailing list question but nevertheless asking here from experts. I have a standalone hadoop environment in CentOs. I have now untared NiFi in the same VM. I am able to start and Stop NiFi from CentOs. I am trying to access the Ni Fi application from my laptop (not from VM) using &lt;A href="http://192.168.191.128:9080/nifi" target="_blank"&gt;http://192.168.191.128:9080/nifi&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I have altered nifi.properties to change port to 9080. I am able to ping my server and other services on Vmware. Is there any setting I am missing. Any help appreciated!&lt;/P&gt;&lt;P&gt;On the other hand. If I have NiFi set up on windows and have my Hadoop cluster running on CentOs. How can I give the config path for core-site and hdfs-site to processors : Do I have to suffix IPaddress somewhere?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Srivi&lt;/P&gt;</description>
    <pubDate>Mon, 30 May 2016 21:36:54 GMT</pubDate>
    <dc:creator>srividhya_karth</dc:creator>
    <dc:date>2016-05-30T21:36:54Z</dc:date>
    <item>
      <title>Ni Fi Installed in VMWare CentOs and URL access error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ni-Fi-Installed-in-VMWare-CentOs-and-URL-access-error/m-p/107733#M30108</link>
      <description>&lt;P&gt;Hi All &lt;/P&gt;&lt;P&gt;Perhaps an apache mailing list question but nevertheless asking here from experts. I have a standalone hadoop environment in CentOs. I have now untared NiFi in the same VM. I am able to start and Stop NiFi from CentOs. I am trying to access the Ni Fi application from my laptop (not from VM) using &lt;A href="http://192.168.191.128:9080/nifi" target="_blank"&gt;http://192.168.191.128:9080/nifi&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I have altered nifi.properties to change port to 9080. I am able to ping my server and other services on Vmware. Is there any setting I am missing. Any help appreciated!&lt;/P&gt;&lt;P&gt;On the other hand. If I have NiFi set up on windows and have my Hadoop cluster running on CentOs. How can I give the config path for core-site and hdfs-site to processors : Do I have to suffix IPaddress somewhere?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Srivi&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2016 21:36:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ni-Fi-Installed-in-VMWare-CentOs-and-URL-access-error/m-p/107733#M30108</guid>
      <dc:creator>srividhya_karth</dc:creator>
      <dc:date>2016-05-30T21:36:54Z</dc:date>
    </item>
    <item>
      <title>Re: Ni Fi Installed in VMWare CentOs and URL access error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ni-Fi-Installed-in-VMWare-CentOs-and-URL-access-error/m-p/107734#M30109</link>
      <description>&lt;P&gt;I figured it out by following the instructions here : &lt;A href="https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices"&gt;https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices&lt;/A&gt; &lt;/P&gt;&lt;P&gt;my linux settings were to be fixed and done.&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2016 21:36:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ni-Fi-Installed-in-VMWare-CentOs-and-URL-access-error/m-p/107734#M30109</guid>
      <dc:creator>srividhya_karth</dc:creator>
      <dc:date>2016-05-30T21:36:55Z</dc:date>
    </item>
  </channel>
</rss>

