Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
All The Tropes Wiki Project, Part XXVII
RE: All The Tropes Wiki Project, Part XXVII
#25
(01-05-2023, 08:07 AM)o further translate that into plain EngliushBob Schroeck Wrote:
(01-05-2023, 01:36 AM)Umbire Wrote:
(01-04-2023, 12:43 PM)robkelk Wrote: It's unlocked. Still waiting to learn why.

Any update?

Yes.  According to the ticket,

Quote:This is fixed. This was due to mysql being restarted because of a OOM and the read_only mode forgotten to be set to 0 after start up.

So, not a symptom of something far more serious.

To further translate to English, that response is that MySQL (the database backend) ran out of memory during a script call, and when they rebooted it to flush the bugged up call (as MySQL can hang with a memory leak on rare occasion), they forgot to make sure the database flag was set to 0 for read-only mode (meaning off, on is set for when they are debugging by preventing changes to the tables to discover bad values, meaning it would be set to 1 then for "on")

In short, database backend snafu, nothing dire.


Messages In This Thread
RE: All The Tropes Wiki Project, Part XXVII - by GethN7 - 01-05-2023, 10:44 AM

Forum Jump:


Users browsing this thread: 5 Guest(s)