Skip to content
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

Uptime Kuma intermittently unresponsive. #5667

Open
2 tasks done
nckrwlmn opened this issue Feb 28, 2025 · 0 comments
Open
2 tasks done

Uptime Kuma intermittently unresponsive. #5667

nckrwlmn opened this issue Feb 28, 2025 · 0 comments
Labels

Comments

@nckrwlmn
Copy link

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

So here is what happened from the beginning. I started uptime Kuma a year ago and it’s been running flawlessly. I deployed it on a VM that is a little bit low on space, so a week ago I noticed that everything was froze up on the dashboard. Everything was at 100% of time which seemed a little bit sketchy. upon further inspection, I noticed that my VM was completely full, and the logs for Uptime Kuma Manager complained that SQL database was low on space or something like that. So I increased the storage on my VM and re-deployed it and things are mostly working as expected. however, I have uptime robot.com visiting my Uptime Kuma status page and it is complaining intermittently that it is down. When I go to check, it’s not down. Approximately five minutes later, it will tell me that it’s back up again, but be aware that uptime robot is only checking every five minutes, so the problem is usually very short-lived. I think.

But I do notice that when I try to clear the heartbeat for a monitor that the bar graph won’t instantly clear out. And I believe that it used to be very instant. Things are just a little bit unresponsive. And shortly there after when I refresh the page only half of the dashboard comes up. So something is not going right with this container, but I find nothing in the logs that shows any issue. Is there some way that I can increase the log level to see more details about what is going on?

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

Brave

🖥️ Deployment Environment

  • Runtime: docker
  • Database: built in to docker cont
  • Filesystem used to store the database on:
  • number of monitors: 20
@nckrwlmn nckrwlmn added the help label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant