Solved An unexpected database error occurred. Please try again later.

[dbdemon]

I've seen the message in the title a couple of times recently when visiting the forums. It's an all white page with the error message in the top left corner. It seems transient as I can usually get it to go away by trying again a bit later.

 

[Ogis]

Hello.
The forum works well for me. I don't see such a message.

 

[Emrion]

I saw this message these last days, but it's rare. Exactly what you describe dbdemon.

 

[SirDice]

Do you know the specific date and time? Can't find anything in the Xenforo logs, may need to check the webserver logs.

 

[Don Y]

I saw this message these last days, but it's rare. Exactly what you describe dbdemon.

+1

 

[dbdemon]

Do you know the specific date and time? Can't find anything in the Xenforo logs, may need to check the webserver logs.

I don't remember exactly but it was a few minutes before I started this thread (maybe max. 20 - 30 minutes).

 

[SirDice]

I don't remember exactly but it was a few minutes before I started this thread (maybe max. 20 - 30 minutes).

That's probably good enough, or else it's like trying to find a needle in a haystack.

 

[cracauer@]

Seen it too, but not in the last hours.

 

[danger@]

Do you guys still experience it? AFAIK DutchDaemon did some tweaks to the db config later on Friday so it should be fixed.

 

[dbdemon]

I haven't seen it again, so hopefully that did the trick.

 

[Don Y]

I've only seen it once or twice (in a week). So, it's pretty intermittent.

And, of course, one doesn't think about what they DID immediately prior to seeing it so there are few "clues" that could be offered.

IMnsHO, the IDEAL use for "Google Glass" would be for developers to be able to replay actions THAT THEY MAY HAVE OBSERVED (but weren't prepared to document BEFORE they happened). Imagine being able to answer the question: "What were you doing when this happened?"

[Can you even BUY Google Glass, anymore? Or, does it rely on something server side (as most Google products do -- so they can have their fingers in your pie) that may have been "turned off"?]

 

[Emrion]

It just happened right now.

 

[meaw229a]

For me too. Right now - Time UTC 8:12 am +13

 

[DutchDaemon]

That tracks with a spike in db connections I see in the monitoring we have set up in the meantime. I will increase the amount of allowed parallel connections from the default.

 

[DutchDaemon]

The error was related to a database dump locking tables for about two minutes, pushing the maximum allowed connections (caused by visitors waiting for their pages) to over the set limit, causing the aforementioned error. The table locking has been removed from the database dump, and the overall connection limit has been increased. This should not happen again (under these circumstances, at least).