Member since
05-18-2017
6
Posts
1
Kudos Received
0
Solutions
12-31-2018
11:30 PM
:~/HDP# sh
docker-deploy-hdp30.sh +
registry=hortonworks + name=sandbox-hdp + version=3.0.1 +
proxyName=sandbox-proxy + proxyVersion=1.0 + flavor=hdp + echo hdp + mkdir -p
sandbox/proxy/conf.d + mkdir -p
sandbox/proxy/conf.stream.d + docker pull
hortonworks/sandbox-hdp:3.0.1 3.0.1: Pulling from
hortonworks/sandbox-hdp 70799bbf2226:
Downloading [================================> ] 47.17MB/72.85MB 40963917cdad:
Pulling fs layer 70799bbf2226:
Downloading [===================================> ] 51.45MB/72.85MB ee3ec4e8cb3d:
Downloading [=======>
] 57.28MB/368.8MB ee3ec4e8cb3d:
Downloading [=======>
] 57.81MB/368.8MB ee3ec4e8cb3d:
Downloading [========>
] 64.24MB/368.8MB 7ea5917732c0:
Download complete 2d951411620c:
Download complete f4c5e354e7fd:
Downloading ca01ba34744d:
Waiting 83326dded077:
Waiting eb3d71b90b73:
Waiting bdd1cab41c81:
Waiting 500cc770c4bd:
Waiting 0cb1decd5474:
Waiting b9591f4b6855:
Waiting f28e56086127:
Waiting e7de4e7d0bca:
Waiting ec77967d2166:
Waiting 4fdcae170114:
Waiting 6347f5df8ffc:
Waiting 6a6ecc232709:
Waiting ea845898ff50:
Waiting 02135573b1bf:
Waiting cb0176867cd8:
Waiting 3c08321268fd:
Pulling fs layer 82e82a97c465:
Waiting 3c08321268fd:
Waiting 74b321ac2ac5:
Waiting 569da02c0a66:
Waiting af40820407ef:
Pulling fs layer af40820407ef:
Waiting unauthorized:
authentication required + docker pull
hortonworks/sandbox-proxy:1.0 1.0: Pulling from
hortonworks/sandbox-proxy Digest:
sha256:42e4cfbcbb76af07e5d8f47a183a0d4105e65a1e7ef39fe37ab746e8b2523e9e Status: Image is up
to date for hortonworks/sandbox-proxy:1.0 + [ hdp = hdf ] + [ hdp = hdp ] +
hostname=sandbox-hdp.hortonworks.com + docker images + grep
hortonworks/sandbox-hdp + awk {print $2} + version= + docker network
create cda + docker run
--privileged --name sandbox-hdp -h sandbox-hdp.hortonworks.com --network=cda
--network-alias=sandbox-hdp.hortonworks.com -d hortonworks/sandbox-hdp: docker: invalid
reference format. See 'docker run
--help'. + echo Remove existing postgres run files. Please
wait Remove existing postgres run files. Please
wait + sleep 2 + docker exec -t
sandbox-hdp sh -c rm -rf /var/run/postgresql/*; systemctl restart
postgresql-9.6.service; Error: No such
container: sandbox-hdp + sed
s/sandbox-hdp-security/sandbox-hdp/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 sandbox-proxy baed363d86a7a73e7712b838df09c2aeda99a6b15f0333e9f8e6f445902a383b docker: Error
response from daemon: driver failed programming external connectivity on
endpoint sandbox-proxy
(d53fe3e3eba2b296b2f6acaa6d8202732308d93cd987157130dfdddef1b82170): Error
starting userland proxy: listen tcp 0.0.0.0:8042: bind: address already in use. i have gone through the script,:- it means docker pull hortonworks/sandbox-hdp:3:0:1 cat docker-deploy-hdp30.sh # CAN EDIT THESE
VALUES registry="hortonworks" name="sandbox-hdp" version="3.0.1" proxyName="sandbox-proxy" proxyVersion="1.0" flavor="hdp" # NO EDITS BEYOND
THIS LINE # housekeeping echo $flavor >
sandbox-flavor # create necessary
folders for nginx and copy over our rule generation script there mkdir -p
sandbox/proxy/conf.d mkdir -p
sandbox/proxy/conf.stream.d # pull and tag the
sandbox and the proxy container docker pull
"$registry/$name:$version"........ ======== but it fails with the error "unauthorized: authentication required". even though if i executed docker pull hortonworks/sandbox-hdp:3:0:1 also i had logged into docker with docker login -u <userid> -p <password>
... View more
10-31-2018
12:02 PM
i have followed the steps but after changing restart zeppeline i am getting below error:- help me to resolve HTTP ERROR: 503 Problem accessing /. Reason: Service Unavailable
... View more
05-18-2017
09:17 AM
Thanks for reply.. i do also having same problem. but as you asvised i removed the file /var/run/cloudera-scm-server.pid then i start the cloudera service and again same issue but that removed file automatically regenarated again. [root@cdh1 ~]# service cloudera-scm-server start Starting cloudera-scm-server: [ OK ] [root@cdh1 ~]# service cloudera-scm-server status cloudera-scm-server dead but pid file exists [root@cdh1 ~]# rm /var/run/cloudera-scm-server.pid rm: remove regular file `/var/run/cloudera-scm-server.pid'? y [root@cdh1 ~]#
... View more