Does this happens a lot, I saw this for the first time.

[twister]

I was just trying to find a thread I saw a few days back and I entered the keywords and then I was greeted by this:



Don't know if it's normal but this is the first time I have seen this, so I thought maybe I should inform admins.

[1714776283]

1714776283

[1714776283]

1714776283

[Madness]

I guess it's some kind of SQL Database error , After searching I found on reddit this answer from Theymos so I'am not sure if it's the same issue or it's just a default message for a lot of issues .

Code:

It was a technical issue while I was sleeping. It's fixed now.
How it happened was that Slickage was downloading a big chunk of the database for testing without turning off some SQL transaction stuff, so ~10 hours into their query, some configured limit was reached (probably the size of the InnoDB undo log), blocking all other queries. The disk wasn't actually full.
(You might be worried about the security of letting someone have access to the live database, but they are restricted via SQL permissions to only reading non-sensitive columns.)

[tarsua]

Never seen that one before but i've been getting alot of 503 errors in the last hours or two

[Nowi]

I di not see it ever too. Does not that post delete ? Or if it is, there is different error ? I think it can be this one.

[PipeCoin]

Have never encountered that error before. Could be a error where multiple users are trying to utilize the search engine at the same time and the request timesout.

[shorena]

I guess it's some kind of SQL Database error , After searching I found on reddit this answer from Theymos so I'am not sure if it's the same issue or it's just a default message for a lot of issues .

Code:

It was a technical issue while I was sleeping. It's fixed now.
How it happened was that Slickage was downloading a big chunk of the database for testing without turning off some SQL transaction stuff, so ~10 hours into their query, some configured limit was reached (probably the size of the InnoDB undo log), blocking all other queries. The disk wasn't actually full.
(You might be worried about the security of letting someone have access to the live database, but they are restricted via SQL permissions to only reading non-sensitive columns.)

Is that regarding the current situation or the last issue when the first assumption was that the server had a raid crash?

[twister]

I wonder if this had anything to do with forum getting hacked because I tried logging in hours later after reporting this and the forum was down and the search is disabled for now?

Also getting lots of 502 Bad Gateway errors.