Yeah, I believe it is happening for almost everyone but people aren't bothered to post about it. You got the time right and the behavior is exactly the same. Not sure how but one of those maint. actions or perhaps multiple are causing the issue so its safer to just have it disabled.

I see but the 24.3.3 won't help you either. You should completely disable maintenance plan / actions. Based on the size of your instance it won't be a problem.

The other option is to tweak the maintenance actions and remove actions 1 by 1 until you find the offending action which causes the issue.

Sorry for kinda ignoring you here. I hope the issues stopped for you. Or are they still happening? I plan to upgrade to 24.2.10 with our MSSQL setup and see how it goes. We hadn't had any crashes or issues for quite a while now, version 24.1.9 still. Moving from sqlite3db to mssql definitely made our life peaceful.

I was wondering because we noticed the same issue, it started a few months ago. What issue did you have yesterday that you needed to restart services? If the database didn't corrupt this time, what made you restart the services?

Slightly off-topic but we moved to MSSQL rather than SQlite3.

Would you share on which version are you currently?

Simply create an access session group with following filter and delete the machines which end up there when it makes sense.

(GuestConnectedCount = '0') AND (GuestInfoUpdateTIme < $180DAYSAGO)

This is most likely due to huge db size and crappy SQLite 3 engine.Session.db and Security.db are the main files in use. There's also .db-wal and .db-shm for those 2 that need to be saved. You can attempt using MSSQL Express 2019 to reach better performance.

We have the same problem and just moved to MSSQL so will see if it helps with the webapp freezes.