Chef Automate Pilot stuck on loading page


#1

Hi All,
I’m learning module scan-for-compliance which uses docker-compose to install Chef Automate Pilot.
docker-compose up -d comes up without error.

When I access localhost in my browser the loading screen comes up but never goes away so I can’t log in.

Bringing up Chef Automate Pilot environment…

When your instance is available please sign in with:

Username: admin
Password: password

Never advances from here.

Any advice to what is wrong or how I can figure out what is wrong?

Thanks,

Andrew


#2

I’m back to connection refused. I’ve been trying this for 3 days. The furthest I have gotten is a frozen loading screen. Do any of these containers have logfiles that I can inspect?

$ docker-compose up -d
Creating network “learninspec_default” with the default driver
Creating learninspec_postgresql-data_1 …
Creating learninspec_postgresql_1 …
Creating learninspec_workflow-server_1 … done
Creating learninspec_automate-nginx_1 … done
Creating learninspec_compliance_1 … done
Creating learninspec_rabbitmq_1 … done
Creating learninspec_notifications_1 … done
Creating learninspec_elasticsearch_1 … done
Creating learninspec_logstash_1 … done

Not sure why those first two don’t say done.

I’m guessing that the learninspec_automate-nginx_1 is the container that has the docker proxy. I’ve looked in the container but I don’t really know what to look for.
$ sudo lsof -i tcp:80
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
docker-pr 11538 root 4u IPv6 61725 0t0 TCP *:http (LISTEN)

That looks like its listening. but curl can’t attach:
curl -v (hostname)
* About to connect() to aboyd1 mylabserver com port 80 (#0)
* Trying 34.217.147.111…
* Connection refused
* Failed connect to aboyd1 mylabserver com:80; Connection refused
* Closing connection 0
curl: (7) Failed connect to aboyd1 mylabserver com:80; Connection refused

Any ideas how to debug? These containers are from: learn.chef.io modules try-chef-automate scan-for-compliance

Any advice would be greatly appreciated.
-Andrew


#3

Here is a link to a gist that shows the error messages that I am getting.

My Box:
OS platform: centos
OS family: redhat
OS release: 7.4.1708

sudo netstat -lnp | grep docker
tcp6 0 0 :::80 :::* LISTEN 11538/docker-proxy
tcp6 0 0 :::443 :::* LISTEN 11519/docker-proxy
unix 2 [ ACC ] STREAM LISTENING 62318 11654/docker-contai @/containerd-shim/moby/5a4205edff594c086ef7dc9416b288f146629db430f71ac84aae72bcbf6a1373/shim.sock
unix 2 [ ACC ] STREAM LISTENING 26932 1125/docker-contain /var/run/docker/containerd/docker-containerd-debug.sock
unix 2 [ ACC ] STREAM LISTENING 26934 1125/docker-contain /var/run/docker/containerd/docker-containerd.sock
unix 2 [ ACC ] STREAM LISTENING 27193 1106/dockerd /var/run/docker/metrics.sock
unix 2 [ ACC ] STREAM LISTENING 60265 11177/docker-contai @/containerd-shim/moby/475b6ffeb76ed52357462ec362ff48c88e08a1bd7ea057e81b2bc63022bab9ad/shim.sock
unix 2 [ ACC ] STREAM LISTENING 63429 11892/docker-contai @/containerd-shim/moby/b3c4c97e81105040d26ad20cf3f6a6496250010ccf2a1bcfb858c9e69d383ec1/shim.sock
unix 2 [ ACC ] STREAM LISTENING 61104 11412/docker-contai @/containerd-shim/moby/e8dbb95a8034d28b67e01b0fcfbb96e21734ec7ce36a83d3a46e9bfd1e815c0d/shim.sock
unix 2 [ ACC ] STREAM LISTENING 63903 11971/docker-contai @/containerd-shim/moby/a279121ce376c5b5e9b63bbba7647a2f1fbc17f857f47d181f845529f891760c/shim.sock
unix 2 [ ACC ] STREAM LISTENING 62973 11819/docker-contai @/containerd-shim/moby/d89a9b9937f19d985bea1dfceba3543c9b23e416870b8939464baeff59a8afa4/shim.sock
unix 2 [ ACC ] STREAM LISTENING 64384 12042/docker-contai @/containerd-shim/moby/40a487b863514e32f4474b1089d93bef0f62d7acdcd72bbe312c31e2dfbb5361/shim.sock
unix 2 [ ACC ] STREAM LISTENING 61749 11555/docker-contai @/containerd-shim/moby/e92123a75fabdc243b919c1b549c19fe693dfdd8ba9d114d05968e25b029ba57/shim.sock
unix 2 [ ACC ] STREAM LISTENING 28896 1106/dockerd /run/docker/libnetwork/bd9a021509e0b53afb8a530afd95de2fb8b8d4ab36d9c70bc4698819d5f63e5a.sock
unix 2 [ ACC ] STREAM LISTENING 26849 1106/dockerd /var/run/docker.sock

I’m not sure what changed, because all I’ve been doing is collecting data for the kind soul that will help me. I can connect now but I’m still stuck on the loading screen:
> curl -v $(hostname)

GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: aboyd1.mylabserver.com
Accept: /

< HTTP/1.1 302 Moved Temporarily
< Server: openresty
< Date: Sat, 10 Feb 2018 12:12:43 GMT
< Content-Type: text/html
< Content-Length: 154
< Connection: keep-alive
< Location: http://aboyd1.mylabserver.com:80/loading
<

302 Found

302 Found


nginx * Connection #0 to host aboyd1.mylabserver.com left intact