Uncle Al wrote: ↑Wed Feb 26, 2025 2:45 amAt this point, indications are that the problem is at the host site.
All available evidence points to that, and it's entirely likely system resource exhaustion, and we're seeing the result of that.
I was able to get into a command-line prompt this morning, and into the database, and reset everybody's login-attempt-counters that had essentially locked them out. I do not know whether the situation is corrected or will reoccur. I was able to grab a copy of the database image from yesterday and pull it into my lab. That won't give me the root cause, but it will allow me to try and develop evasion tactics so there's less damage done by this mess.
Ultimately, I think the answer is going to be the painful option of, "waiting it out".
If this keeps up, I'll contact the Barista Emeritus and seek guidance and leverage. I remain in close contact with the other US-based staff (but lack an international plan on my mobile, so haven't been in touch with Denimini).