-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
No data and no alerts if site goes down #1219
Comments
Again i see error, after restart |
Are there any logs in the server output? |
Here is logs from docker container, maybe you can tell me where to find some other debug logs? https://pb0.superhub.xyz/?fdff20a2a4ba2348#KNj9yiwtEjvqlqkkBtTBBJIqUpFOwLQok1xJvYnRCjw= |
also error.log inside container:
|
Hey, guys, any news please? |
Relevant previous discussion in #218. Unfortunately it's a generic database connection error and there isn't much to go on. |
But im using native sqlite database inside docker container, how it may be error with connecting to database? |
It may causes by a busy database. The monitor should be restarted if there is any error in general. |
A lot of performance improvements (using aggregated vs non-aggregated tables to store heartbeats, enabling users to choose mariadb as a db-backend, pagination of important events) have been made in You can subscribe to our releases and get notified when a new release (such as Meanwhile (the issue is with SQLite not reading data fast enough to keep up):
|
🛡️ Security Policy
Description
At some point in time, my monitoring stops checking the availability of the site. This is expressed in the fact that it "freezes" and displays the latest data for a certain period of time, the same thing happens when I use the prometheus exporter.
👟 Reproduction steps
This also happened on version 1.1 (before switching to the new one), I even put monitoring on a separate server, but the problem still repeats. I have about 15-20 HTTP checks, and they all don't work
👀 Expected behavior
Operational monitoring and display of correct data
😓 Actual Behavior
At some point in time, monitoring "freezes" and it's not clear to me how to fix it. This happens until I stop/enable monitoring or restart the server with monitoring.
Here is some screenshots:
how it looks like from uptime-kuma:
![](https://camo.githubusercontent.com/a5b84d966caba2afa7ffd25bfcc482b993e2f31c5f4a471a06348283182e440e/68747470733a2f2f696d672e73686172652e73757065726875622e78797a2f7636787776612e706e67)
if 24h:
![](https://camo.githubusercontent.com/9630068bbba5f9455e2f996d0219fbf4eff0ee72ac47001a6c57b904fc99aeaf/68747470733a2f2f696d672e73686172652e73757065726875622e78797a2f71657564667a2e706e67)
grafana:
![](https://camo.githubusercontent.com/7d75d1e5a2bb2316a9148248973d8d39667251349014f57e48ebff7694ba12ee/68747470733a2f2f696d672e73686172652e73757065726875622e78797a2f6568396f686b2e706e67)
So as you can see it stopped posting status after 00:00 24.01.22
How to fix this? My monitoring VM have about 100Gb NVMe space free
🐻 Uptime-Kuma Version
1.11.3
💻 Operating System and Arch
Ubuntu 18.04
🌐 Browser
Safari
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: