Problem error healthcheck. on k8s #1910

Closed
opened 2026-02-28 02:36:52 -05:00 by deekerman · 8 comments
Owner

Originally created by @PrasinMike on GitHub (Feb 20, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I found error healthcheck on k8s
livenessProbe: exec: command: - node - extra/healthcheck
this error
image

🐻 Uptime-Kuma Version

louislam/uptime-kuma:1.20.0

💻 Operating System and Arch

🌐 Browser

🐋 Docker Version

K8S

🟩 NodeJS Version

No response

Originally created by @PrasinMike on GitHub (Feb 20, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I found error healthcheck on k8s ` livenessProbe: exec: command: - node - extra/healthcheck` this error <img width="683" alt="image" src="https://user-images.githubusercontent.com/108521875/220087220-ef10e24c-4bdb-4720-8aac-63cdf6646da9.png"> ### 🐻 Uptime-Kuma Version louislam/uptime-kuma:1.20.0 ### 💻 Operating System and Arch - ### 🌐 Browser - ### 🐋 Docker Version K8S ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 02:36:52 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@louislam commented on GitHub (Feb 20, 2023):

extra/healthcheck is not a javascript file, it is an executable file.

@louislam commented on GitHub (Feb 20, 2023): `extra/healthcheck` is not a javascript file, it is an executable file.
Author
Owner

@PrasinMike commented on GitHub (Feb 20, 2023):

extra/healthcheck is not a javascript file, it is an executable file.

  1. I can use healthcheck or healthcheck.go ? on k8s
  2. What should I change? exec command

livenessProbe: exec: command: - node

@PrasinMike commented on GitHub (Feb 20, 2023): > `extra/healthcheck` is not a javascript file, it is an executable file. 1. I can use healthcheck or healthcheck.go ? on k8s 2. What should I change? exec command ` livenessProbe: exec: command: - node`
Author
Owner

@PrasinMike commented on GitHub (Feb 20, 2023):

I fix it command and use health check I found error this image
image

@PrasinMike commented on GitHub (Feb 20, 2023): I fix it command and use health check I found error this image <img width="703" alt="image" src="https://user-images.githubusercontent.com/108521875/220177578-4935906d-eeae-4f3b-acc3-68e4cf0757b6.png">
Author
Owner

@louislam commented on GitHub (Feb 20, 2023):

Are you using extra/healthcheck?

PS: extra/healthcheck.js is not working in k8s due to the collision of UPTIME_KUMA_PORT env vars

@louislam commented on GitHub (Feb 20, 2023): Are you using `extra/healthcheck`? PS: `extra/healthcheck.js` is not working in k8s due to the collision of `UPTIME_KUMA_PORT` env vars
Author
Owner

@PrasinMike commented on GitHub (Feb 21, 2023):

Are you using extra/healthcheck?

yes I use extra/healthcheck

@PrasinMike commented on GitHub (Feb 21, 2023): > Are you using `extra/healthcheck`? yes I use extra/healthcheck
Author
Owner

@louislam commented on GitHub (Feb 21, 2023):

Just realize that I forget to re-compile extra/healthcheck it in the latest docker image.

Workaround:
Try to set UPTIME_KUMA_PORT=3001

@louislam commented on GitHub (Feb 21, 2023): Just realize that I forget to re-compile `extra/healthcheck` it in the latest docker image. Workaround: Try to set `UPTIME_KUMA_PORT=3001`
Author
Owner

@PrasinMike commented on GitHub (Feb 22, 2023):

Just realize that I forget to re-compile extra/healthcheck it in the latest docker image.

Workaround: Try to set UPTIME_KUMA_PORT=3001

Thanks you this work

@PrasinMike commented on GitHub (Feb 22, 2023): > Just realize that I forget to re-compile `extra/healthcheck` it in the latest docker image. > > Workaround: Try to set `UPTIME_KUMA_PORT=3001` Thanks you this work
Author
Owner

@CommanderStorm commented on GitHub (Jul 27, 2023):

@PrasinMike
There don't seem to remain any open issues in this issue, am I correct?
If yes, don't forget to close it.

(Only you or Louis can do so. Otherwise, this will become a zombie that never dies)

@CommanderStorm commented on GitHub (Jul 27, 2023): @PrasinMike There don't seem to remain any open issues in this issue, am I correct? If yes, don't forget to close it. (Only you or Louis can do so. Otherwise, this will become a zombie that never dies)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1910
No description provided.