<?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 Re: HDF 3.1.1 not starting in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215090#M81661</link>
    <description>&lt;P&gt;Thanks that helped. There was a deamon process which was running under root when I ran this command ,  I did get the information that something was running, I had to run this command as root and that it gave me the name of the daemon which was running. I had to uninstall it and it worked fine. &lt;/P&gt;</description>
    <pubDate>Tue, 07 Aug 2018 05:31:25 GMT</pubDate>
    <dc:creator>hdeci</dc:creator>
    <dc:date>2018-08-07T05:31:25Z</dc:date>
    <item>
      <title>HDF 3.1.1 not starting</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215088#M81659</link>
      <description>&lt;P&gt;	I'm trying to start HDF on  Linux, when I start I get this error&lt;/P&gt;
&lt;PRE&gt;	+ docker run --privileged --name sandbox-hdf -h --network=cda --network-alias= -d hortonworks/sandbox-hdf:3.1.1 6abf2ecd29d8a806be8bf2174a4d3d15c64b17e6eee86c6b52d531d1295d53b9 docker: Error response from daemon: network-scoped alias is supported only for containers in user defined networks. + echo Remove existing postgres run files. Please wait... Remove existing postgres run files. Please wait... + sleep 2 + docker exec -t sandbox-hdf sh -c rm -rf /var/run/postgresql/*; systemctl restart postgresql; Error response from daemon: Container 6abf2ecd29d8a806be8bf2174a4d3d15c64b17e6eee86c6b52d531d1295d53b9 is not running + sed s/sandbox-hdf-standalone-cda-ready/sandbox-hdf/g assets/generate-proxy-deploy-script.sh + mv -f assets/generate-proxy-deploy-script.sh.new assets/generate-proxy-deploy-script.sh + chmod +x assets/generate-proxy-deploy-script.sh + assets/generate-proxy-deploy-script.sh + uname + grep MINGW + chmod +x sandbox/proxy/proxy-deploy.sh + sandbox/proxy/proxy-deploy.sh e9f254500068cd78b2dda88ce63f42779ccb958e859d570ad76999763dfba1be docker: Error response from daemon: driver failed programming external connectivity on endpoint sandbox-proxy (dbc6108bda8a76afc46d5a0d02c64934429428074307ee9d77bc256c0834528d): Error starting userland proxy: listen tcp 0.0.0.0:7777: bind: address already in use. 	&lt;/PRE&gt;
	&lt;P&gt;there is no other process which is running. I have restarted docker so many times. Can't figure out why I would get this error.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 12:15:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215088#M81659</guid>
      <dc:creator>hdeci</dc:creator>
      <dc:date>2026-04-21T12:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: HDF 3.1.1 not starting</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215089#M81660</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/89302/singhharjit.html" nodeid="89302"&gt;@Harjit Singh&lt;/A&gt;! &lt;BR /&gt;Could you confirm if you already have something running on 7777 port?&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;netstat -tulpn | grep -i 7777&lt;/PRE&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;</description>
      <pubDate>Tue, 07 Aug 2018 04:47:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215089#M81660</guid>
      <dc:creator>vmurakami</dc:creator>
      <dc:date>2018-08-07T04:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: HDF 3.1.1 not starting</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215090#M81661</link>
      <description>&lt;P&gt;Thanks that helped. There was a deamon process which was running under root when I ran this command ,  I did get the information that something was running, I had to run this command as root and that it gave me the name of the daemon which was running. I had to uninstall it and it worked fine. &lt;/P&gt;</description>
      <pubDate>Tue, 07 Aug 2018 05:31:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215090#M81661</guid>
      <dc:creator>hdeci</dc:creator>
      <dc:date>2018-08-07T05:31:25Z</dc:date>
    </item>
    <item>
      <title>Re: HDF 3.1.1 not starting</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215091#M81662</link>
      <description>&lt;P&gt;I'm glad to know &lt;A rel="user" href="https://community.cloudera.com/users/89302/singhharjit.html" nodeid="89302"&gt;@Harjit Singh&lt;/A&gt;! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;Please, if the issue got solved, I'd kindly ask you to accept this as an answer. This will engage other HCC users to keep doing a good job. &lt;BR /&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Aug 2018 05:33:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HDF-3-1-1-not-starting/m-p/215091#M81662</guid>
      <dc:creator>vmurakami</dc:creator>
      <dc:date>2018-08-07T05:33:45Z</dc:date>
    </item>
  </channel>
</rss>

