Fresh install: "Pulling the catalog library from the repo ..." for last 7 hours

Rancher 1.x
1

Hi,

been trying to try out rancher. Followed installation instructions.
Deployed on a Docker version 1.9.1, build a34a1d5 on AWS

Logfile entries:
time="2015-12-15T03:37:56Z" level=info msg="Pulling the catalog library from the repo to sync any new changes to ./DATA/library"

for the last 7 hours.

Hitting the rancher server ip:8080 results in
{"type":"collection","resourceType":"apiVersion","links":{"self":"http://localhost:8080/","latest":"http://localhost:8080/v1"},"createTypes":{},"actions":{},"data":[{"id":"v1","type":"apiVersion","links":{"self":"http://localhost:8080/v1"},"actions":{}}],"sortLinks":{},"pagination":null,"sort":null,"filters":{},"createDefaults":{}}

That seems unexpected.

Does anyone know what I could change to speed this up?

Thanks for any pointers!!

Dan

2

The "Pulling the catalog library from the repo to sync any new changes to ./DATA/library" is a periodic sync (albeit every 5 minutes) but it shouldn’t affect rancher-server starting.

What OS type are you using in AWS? Are your security groups set up correctly in AWS? For Rancher-server, you only need 8080 open.

3

Now. That makes me feel slightly silly… I indeed forgot about configuring the AWS security group with the required port.
Thanks so much!

To answer your question - the OS type is ubuntu 14.04

What did trip me up a little bit was that I looked in the log for the line containing .... Startup Succeeded, Listening on port 8080 which is mentioned in the quick start documentation.
That line never showed up.
What did show up though was .... Startup Succeeded, Listening on port 8081 …

4

Yeah that should be corrected… Java is listening on 8081 now and there’s a separate internal proxy on top for 8080->8081.