Hello, I know there are several posts about this problem, but I could not figure out what is the best post to solve my problem. Here is what I have. I after running: start_sandbox-hdp.sh I get: "Ambari server 'start' completed successfully" I believe my docker has been updated. I see some posts saying to modifying the sandbox startup script, but I am not sure what to change. I have Hortonworks HDP 2.6.1 installed. Any help would be much appreciated. Here is other information about my environment OS: Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial Could it be because of low disk space? 96% used up space on the file system /dev/sdc1 and /devf/sda1. Would this cause the sandbox to not start? Filesystem 1K-blocks Used Available Use% Mounted on
overlay 64989928 61996332 2977212 96% /
tmpfs 65536 0 65536 0% /dev
tmpfs 16459536 0 16459536 0% /sys/fs/cgroup
/dev/sdc1 67075056 1651732 65423324 3% /data
/dev/sda1 64989928 61996332 2977212 96% /etc/resolv.conf
/dev/sda1 64989928 61996332 2977212 96% /etc/hostname
/dev/sda1 64989928 61996332 2977212 96% /etc/hosts
shm 65536 0 65536 0% /dev/shm The sandbox start HDP sh file: #!/bin/bash
echo "Waiting for docker daemon to start up:"
until docker ps 2>&1| grep STATUS>/dev/null; do sleep 1; done; >/dev/null
docker ps -a | grep sandbox-hdp
if [ $? -eq 0 ]; then
docker start sandbox-hdp
else
docker run --name sandbox-hdp --hostname "sandbox.hortonworks.com" --privileged -v /data:/data -d \
-p 1111:111 \
-p 1000:1000 \
-p 1100:1100 \
-p 1220:1220 \
-p 1988:1988 \
-p 2049:2049 \
-p 2100:2100 \
-p 2181:2181 \
-p 3000:3000 \
-p 4040-4050:4040-4050 \
-p 9999:9999 \
-p 4200:4200 \
-p 4242:4242 \
-p 5007:5007 \
-p 5011:5011 \
-p 6001:6001 \
-p 6003:6003 \
-p 6008:6008 \
-p 6080:6080 \
-p 6188:6188 \
-p 8000:8000 \
-p 8005:8005 \
-p 8020:8020 \
-p 8032:8032 \
-p 8040:8040 \
-p 8042:8042 \
-p 8080:8080 \
-p 8082:8082 \
-p 8086:8086 \
-p 8088:8088 \
-p 8090:8090 \
-p 8091:8091 \
-p 8188:8188 \
-p 8443:8443 \
-p 8744:8744 \
-p 8765:8765 \
-p 8886:8886 \
-p 8888:8888 \
-p 8889:8889 \
-p 8983:8983 \
-p 8993:8993 \
-p 9000:9000 \
-p 9995:9995 \
-p 9996:9996 \
-p 10000:10000 \
-p 10001:10001 \
-p 10015:10015 \
-p 10016:10016 \
bash
echo "Waiting for docker daemon to start up:" In an ambari-agent.out file, this is repeated: WARNING: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
javax.jdo.option.ConnectionPassword has been successfully created.
org.apache.hadoop.security.alias.JavaKeyStoreProvider has been updated.
2018-04-14 02:07:31,850 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Apr 14, 2018 2:08:44 AM org.apache.hadoop.util.NativeCodeLoader <clinit>
WARNING: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
oozie.service.JPAService.jdbc.password has been successfully created.
org.apache.hadoop.security.alias.JavaKeyStoreProvider has been updated.
2018-04-14 02:09:33,283 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
2018-04-14 02:10:34,443 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
2018-04-14 02:11:35,382 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
2018-04-14 02:12:35,604 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
2018-04-14 02:13:35,659 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
2018-04-14 02:14:35,635 - Testing the JVM's JCE policy to see it if supports an unlimited key length.
"ambari-agent.out" 112L, 10714C
... View more
