You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2020. It is now read-only.
Creating sensu-server ... done
* Waiting for the Platform to become available - this can take a few minutes
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
* Loading the Platform
Generating client certificates for TLS-enabled Engine
/root/docker_certs/cert.pem was generated successfully...
/root/docker_certs/ca.pem was generated successfully...
/root/docker_certs/key.pem was generated successfully...
Uploading certificates to Jenkins Slave at: //root/.docker/
* Waiting for Nginx to become available
Nginx was unavailable, so slept for: 5 secs
Nginx was unavailable, so slept for: 5 secs
Nginx was unavailable, so slept for: 5 secs
Nginx was unavailable, so slept for: 5 secs
Nginx was unavailable, so slept for: 5 secs
Nginx was unavailable, so slept for: 5 secs
--see complete log in the attachment.
Stopped this and connected to the machine:
and found that all the services are up and running except the registry container is restarting forever: d3c255fb6e44 registry:2.5.1 "/entrypoint.sh /etc…" 14 minutes ago Restarting (1) 29 seconds ago registry Not sure if this could be an issue but this worked only once when upgraded the image version to 2.6 in compose.yml.
docker logs for jenkins, gerrit etc did not work with the below error:
root@adop:~# docker logs jenkins
Error response from daemon: configured logging driver does not support reading
root@adop:~# docker logs jenkins-slave
Error response from daemon: configured logging driver does not support reading
root@adop:~# docker logs registry
Error response from daemon: configured logging driver does not support reading
Tried to restart with more options: root@ip-172-31-5-91:~/adop-docker-compose# ./adop compose -m adop init --with-stdout
Found out the similar issues reported in unable to start the platform #285
--tail of the log:
Recreating sensu-uchiwa ... done
Recreating sonar ... done
* Waiting for the Platform to become available - this can take a few minutes
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
Jenkins was unavailable, so slept for: 30 secs
Error response from daemon: Container 70a70033eb1ddb93f1e6a5f8e4d4bff6145107cfc3aa99f319977e49e0da036f is restarting, wait until the container is running
Jenkins was unavailable, so slept for: 30 secs
Error response from daemon: Container 70a70033eb1ddb93f1e6a5f8e4d4bff6145107cfc3aa99f319977e49e0da036f is restarting, wait until the container is running
Jenkins was unavailable, so slept for: 30 secs
Error response from daemon: Container 70a70033eb1ddb93f1e6a5f8e4d4bff6145107cfc3aa99f319977e49e0da036f is restarting, wait until the container is running
Jenkins was unavailable, so slept for: 30 secs
performed the logs check of Jenkins and found this extract:
root@adop:~# docker logs 70a70033eb1ddb93f1e6a5f8e4d4bff6145107cfc3aa99f319977e49e0da036f
Genarate JENKINS SSH KEY and add it to gerrit
Setting up your default SCM provider - Gerrit...
Generate Sonar authentication token
Generating Sonar Authentication Token
* Waiting for the Sonar user token api to become available - this can take a few minutes
Generating Jenkins Key Pair
Sonar was unavailable, so slept for: 30 secs
Sonar was unavailable, so slept for: 30 secs
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 90 100 90 0 0 2425 0 --:--:-- --:--:-- --:--:-- 2432
Traceback (most recent call last):
File "<string>", line 1, in <module>
KeyError: 'token'
Able to reproduce this after finding the same behavior atleast 3-4times now:
Followed the instructions in the quickstart and performed the steps as follows:
Quikcstart Script:
./quickstart.sh -t aws -m adop -c vpc-xxxx -r eu-west-1 -z c -a AAA -s SSS -u prd -p xxxx
tail of the log:
--see complete log in the attachment.
and found that all the services are up and running except the registry container is restarting forever:
d3c255fb6e44 registry:2.5.1 "/entrypoint.sh /etc…" 14 minutes ago Restarting (1) 29 seconds ago registry
Not sure if this could be an issue but this worked only once when upgraded the image version to 2.6 in compose.yml.
root@ip-172-31-5-91:~/adop-docker-compose# ./adop compose -m adop init --with-stdout
Found out the similar issues reported in unable to start the platform #285
--tail of the log:
Detailed logs: github_adop.log
The text was updated successfully, but these errors were encountered: