Support Questions
Find answers, ask questions, and share your expertise

HDF 3.1.1 not starting

Explorer

I'm trying to start HDF on Linux, when I start I get this error

	+ 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. 	

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.

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @Harjit Singh!
Could you confirm if you already have something running on 7777 port?

netstat -tulpn | grep -i 7777

Hope this helps!

View solution in original post

3 REPLIES 3

Hi @Harjit Singh!
Could you confirm if you already have something running on 7777 port?

netstat -tulpn | grep -i 7777

Hope this helps!

View solution in original post

Explorer

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.

I'm glad to know @Harjit Singh! 🙂
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.
Thanks.