-
Notifications
You must be signed in to change notification settings - Fork 46
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
"Unhealthy Readiness probe failed: Get "http://xx.xx.xx.xx:8080/ping": dial tcp xx.xx.xx.xx:8080: connect: connection refused" #bug #280
Comments
@Puvendhan what's the version you are using? |
Here's the version 1.0.0-beta5 |
Hi, Any update on this? |
Seems like a compatibility problem of the gcp Cloudsql mysql, try using |
Hello I'm experiencing this issue as well, starting from |
@hayk96 You can try the latest version. |
Thanks for your response @d4x1 I've just tried the latest version: |
I've tried the
|
@hayk96 Please paste more logs so we can find which migration script failed with this error message. |
sure, in that time the pod was printing the following logs:
|
@hayk96 I've tried v1.0.1-beta1 with am empty database, there is no error. |
yes, all DevLeke versions work fine with an empty database. These errors have been raised during upgrades. Will check. |
tables that have
length of the columns
|
@hayk96 I cannot find which scipr fialed from you logs. You can change the log level and if something went wrong, we can find the script id from this line: https://github.com/apache/incubator-devlake/blob/main/backend/core/migration/migrator.go#L99 |
I have deleted the entire stack, so can not reproduce it. |
I am getting the below error in the devlake-lake pod, the UI is up , but after clicking on "Proceed Database Migration" , the devlake pod is going down and giving the below error.
Pod is having this event
"Unhealthy Readiness probe failed: Get "http://xx.xx.xx.xx:8080/ping": dial tcp xx.xx.xx.xx:8080: connect: connection refused"
I am using gcp Cloudsql mysql instance and used the below arguments to enable external mysql server
mysql: useExternal: true externalServer: xxxxxxxx externalPort: 3306 username: testuser password: xxxxxx database: devlake option: autoCreateSecret: true
The text was updated successfully, but these errors were encountered: