Skip to content
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.

shipshape exits with "Error HTTP client did not become healthy: service did not respond before timeout:" #124

Open
Zemnmez opened this issue Feb 18, 2018 · 2 comments
Open

shipshape exits with "Error HTTP client did not become healthy: service did not respond before timeout:" #124

Zemnmez opened this issue Feb 18, 2018 · 2 comments

Comments

@Zemnmez
Copy link

Zemnmez commented Feb 18, 2018 

shipshape -v 10 -logtostderr .
Status: Image is up to date for beta.gcr.io/shipshape_releases/service:prod
I0218 21:58:59.220580    2355 shipshape_lib.go:346] Pulling complete
I0218 21:58:59.220644    2355 shipshape_lib.go:369] Pulling dockerized analyzers...
I0218 21:58:59.220686    2355 shipshape_lib.go:371] Analyzers pulled
I0218 21:58:59.220710    2355 shipshape_lib.go:270] Starting shipshape...
I0218 21:58:59.230821    2355 docker.go:203] Running 'docker [run -p=127.0.0.1:10007:10007 -v=/home/ubuntu:/shipshape-workspace -v=/tmp:/shipshape-output -e="START_SERVICE=true" -e="ANALYZERS=localhost:10005,localhost:10006,localhost:10008" --name=shipping_container -d beta.gcr.io/shipshape_releases/service:prod]'
I0218 21:58:59.521892    2355 shipshape_lib.go:414] stdout:
43d5b0713c917e3f541807b27e09181a4a5ad4a647bf6b692e6977760a5f7e6b
I0218 21:58:59.522146    2355 shipshape_lib.go:306] Image beta.gcr.io/shipshape_releases/service:prod running in service mode
Error: HTTP client did not become healthy: service did not respond before timeout: HTTP failure: Post http://localhost:10007/: read tcp 127.0.0.1:40904->127.0.0.1:10007: read: connection reset by peer
@Ramos-dev
Copy link

i met the same question too

@djtjwillia
Copy link

I am seeing the same thing as well.
I am trying to run shipshape on a jenkins agent that was spun up as an ubuntu ec2 instance.

setup steps:

sudo usermod -a -G docker $USER
wget https://storage.googleapis.com/shipshape-cli/shipshape
chmod 555 shipshape
sudo mv shipshape /usr/bin/
shipshape -v 10 -logtostderr $PWD

build output:

Digest: sha256:e89a931874a7677e91cba6dc94df67df7bd272d6087dfccf40f9e8c44d992ec9
Status: Downloaded newer image for beta.gcr.io/shipshape_releases/service:prod
I0206 14:01:05.860947    2262 shipshape_lib.go:346] Pulling complete
I0206 14:01:05.860964    2262 shipshape_lib.go:369] Pulling dockerized analyzers...
I0206 14:01:05.860969    2262 shipshape_lib.go:371] Analyzers pulled
I0206 14:01:05.860975    2262 shipshape_lib.go:270] Starting shipshape...
I0206 14:01:05.916506    2262 docker.go:203] Running 'docker [run -p=127.0.0.1:10007:10007 -v=/home/ubuntu/workspace/k-swa-jenkins-job-to-multibranch:/shipshape-workspace -v=/tmp:/shipshape-output -e="START_SERVICE=true" -e="ANALYZERS=localhost:10005,localhost:10006,localhost:10008" --name=shipping_container -d beta.gcr.io/shipshape_releases/service:prod]'
I0206 14:01:06.537299    2262 shipshape_lib.go:414] stdout:
4d1050d1c1241518b818371c6300c050df19b5ba28df86b64929d3e4abdf1e13
I0206 14:01:06.537341    2262 shipshape_lib.go:306] Image beta.gcr.io/shipshape_releases/service:prod running in service mode

Error: HTTP client did not become healthy: service did not respond before timeout: HTTP failure: Post http://localhost:10007/: read tcp 127.0.0.1:52534->127.0.0.1:10007: read: connection reset by peer

is there anyway we can get someone to assist? I see that this issue has been open for nearly a year with no response :/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Zemnmez @djtjwillia @Ramos-dev