Thank you for the suggestion. We are not noticing issues wit Rocket.chat, so the issue might be with Uptime Kuma or its database.
Posts made by martinv
RE: Very slow after restart
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.
Very slow after restart
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?
we are running in an issue where our Rocket.Chat instance is unable to properly send messages after about 20 hours of uptime. Whenever I try to send a message to somebody the message appears gray, indicating that it was not yet sent. The user does actually get the message though, but it impossible to chat like that.
I wanted to check some log files, but I only found that Rocket.Chat logs errors to stdout here: https://github.com/RocketChat/Docker.Official.Image/issues/16 So I tried to run the command, but it have me the error:
# docker logs e5648bb067fe Error response from daemon: configured logging driver does not support reading
I tried to attach to the docket stdout, but nothing would ever appear:
docker attach e5648bb067fe
I tried to inspect the files on docker too by logging in:
docker exec -it -u root e5648bb067fe /bin/bash
I tried to check the Mongo containers as well:
# docker exec -it -u root 48f5e963462c /bin/bash
Once there I was able to connect to the database:
But then even basic command like list of tables failed:
rs0:PRIMARY> use rocketchat switched to db rocketchat rs0:PRIMARY> show tables; Warning: unable to run listCollections, attempting to approximate collection names by parsing connectionStatus
Could you please provide any insight?