Service stopped working, Dashboard works fine

[Ingo-Knito]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

I have installed uptime-kuma a couple of months ago and it worked perfekt.
Now, a couple of weeks later, two active monitors are not working anymore.

According to the dashboard, both are active and the url is also accessible.
But the statistics are not updated anymore and the last check was 14 days ago.
The dashboard looks ok.

📝 Error Message(s) or Log

🐻 Uptime-Kuma Version

1.23.3

💻 Operating System and Arch

RASPI, Debian Bookworm

🌐 Browser

Chrome

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors: 2

[CommanderStorm]

What does the log say?
What is your Deployment Environment?

[chakflying]

Please update the application to the latest version. Older versions of 1.23.X had issues were HTTP monitors could get stuck due to incorrect handling of timeouts. (see #3952) This should be fixed in the latest version.

[CommanderStorm]

Good catch.
I am going to close this issue as resolved.
@Ingo-Knito if this issue persists on newer versions, we can reopen this issue ^^

[Ingo-Knito]

Ok, thanks for your help!

I will try (again) to update. Actual the update fails.
I'm running it as a service. It looks like the "mv" during the installation causes this problem. But this is an other issue...

[Ingo-Knito]

Just to let you know: I've found the problem.

The time of the system was not set correct. After setting up NTP everything is fine.
It was never an issue on uptime-kuma.

Thanks for your support!

[chakflying]

That's very interesting. We never found the root cause of the original issue. I wonder if the system time jumping backwards / getting too out of sync would somehow break node.js's timers.