-
-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest next version of Woodpecker server fails to start #2370
Comments
I tried the next version again without success but I did get a additional log that I think could help.
|
Given that nobody else reported issues and all tests passed, it's likely a config issue. Did you try starting it without custom DNS mappings? If those are important, can you explain them? Also which other env vars are set? |
Yes I have tried starting it without the custom DNS mappings. Same result. ENV vars set
|
Having looked a bit further I personally think the issue is as follows: I run Docker in Swarm mode. As I mentioned every next version after This message is from this file: https://github.com/woodpecker-ci/woodpecker/blob/main/cmd/server/health.go Now I don't know much about golang code but I think it checks if the status is 200 and if not it will give an error and return this message. In addition to the above I have tried running Woodpecker on a different server with the following command:
Now the container doesn't get killed but still gets the unhealthy status & returns the same message I posted before from |
We could check to use a status check like: |
@rubenelshof Thanks for the deep dive! This makes a lot of sense. I wonder:
|
@qwerty287 FYI since you added #2366 |
Hmm yes, indeed, I changed it to 204, didn't know I would have to change this as well. Fixing should be easy though by applying @anbraten's solution in #2370 (comment) to https://github.com/woodpecker-ci/woodpecker/blob/main/cmd/server/health.go#L59 |
Component
server
Describe the bug
Woodpecker server fails to successfully start with the latest next version.
It will start up but the container remains unhealthy and eventually fails.
I have switched back to an earlier version
next-3bee51dc7a
which does work.System Info
Latest next version.
Because it won't start up I can't get the exact version.
Compose:
Additional context
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: