Very slow after restart

[martinv]

I tried to modify some of the core Uptime Kuma files in its /app/code/ folder. It was in the Rocket.chat notifications file.

The change did not make any effect, so I tried restarting it.

I was shocked to see the empty list of monitors. It's as if the whole database has disappeared.

However then, couple of minutes later, the list got populated.

I thought it could be a damage done by some of my modifications. So I just restored the backup from yesterday.

But I'm still running into the issue and currently the monitors are not loading at all.

Did anybody experience issues with Uptime Kuma after restart?

[martinv]

I restarted it again and now it works and it's fast again.

It's weird, did anyone experience anything similar with Cloudron and/or Uptime Kuma?

[martinv]

Unfortunately the issue is still present. It was only fast for a while.

I tried to restart the whole server, but it did not fix the issue. The server is not overloaded and there is plenty of free memory.

The app logs show no errors or warnings. It reports memory usage of 110 MB.

[nebulon]

are other apps and Cloudron itself snappy and feel fast enough? If you don't run out of memory and the CPU is doing fine (you can check this via ssh using htop or top) then this is likely an upstream app issue.

Our instance is doing quite fine though.

[martinv]

Thank you for the suggestion. We are not noticing issues wit Rocket.chat, so the issue might be with Uptime Kuma or its database.