search

Study-Together-Org / time_counter

12 stars 5 forks source link

A lot of hours/streaks got dropped for a lot of people after the bot went unresponsive for 10 minutes. #61

Closed Totti56 closed 3 years ago

Totti56 commented 3 years ago

Descriptions The counter bot went unresponsive at around 14:17 - 14:27 UTC+2 where the bot did not respond to any commands. image https://discord.com/channels/595999872222756885/695434541233602621/841287862803628092 (link to when it started)

After the bot was responsive again, some people noticed their stats were off. image image

Example user: Stats of a user (759047159990845501) before the bot went unresponsive at 13:52: image Stats of that user after the bot went responsive again 14:29: image As you can see that the user's stats before the bot went unresponsive had a lot more hours than after. So, I am thinking that the fact that the counter bot went unresponsive during those two time frames might have a relation with that the hours of lots of people got dropped.

This also caused a drop of streaks for all(?) users.

Gugu7264 commented 3 years ago

Within the timeframe @Totskoz provided, I can see this: https://ptb.discord.com/channels/595999872222756885/738091719073202327/841289208576212992

Bot restarted, might be the issue here

Gugu7264 commented 3 years ago

Checked redis logs, server disconnected, might be the same issue as last time per Nadir

Zackhardtoname commented 3 years ago

An issue with not having enough memory. It should be fixed as I added a swapfile.