Forums

Cannot connect to Console. Stuck at "Loading Mysql Interpreter" Need help immediately. Once had a "max user connections" error but reloaded the site and now im again stuck at "Loading Mysql Interpreter"

Hi there -- sorry for the slow response! I think there may have been a short outage on the MySQL server associated with your account at the time you posted this -- has the problem cleared up now?

I'm not sure if this is related but I'm having a hard time SSHing in with mysql workbench. I'm able to connect but the schemas aren't loading.

Something isn't right. Trying to open a console through the browser is hanging as well.

Loading console... Preparing execution environment... OK Reversing the polarity of the neutron flow... OK Loading Mysql interpreter...

Interesting. Did it start the MySQL console eventually? I'm wondering if we have a load issue on one of our MySQL servers in the early morning our time.

The console eventually loaded but I have no idea how long it took. I ended up getting up and walking away. I looked at things this morning (United States Pacific Standard Time) and so far things seem to be a little snappier. I held off doing some updates last night because of the connection issue but I plan on trying out some updates this weekend.

OK, thanks for confirming it's faster again now. We're keeping an eye on the server.

Problem still persists for me. I had to just open up the console page and leave it while I went to dinner. When i came back it had opened so no idea how long it took but it wasnt as quick as it used to be.

Hi there, we are looking into it right now. Sorry about that!

Is it sorted now?

yes things are faster right now. Thanks!

A quick note that I've had some additional weirdness with my application not being able to connect to MySQL. No setting changes so it would seem (?) to be an availability issue?

"Can't connect to MySQL server on 'cppcorpdev.mysql.pythonanywhere-services.com' (111)"

Sorry about that -- I think we just had a short (<2 minute) glitch on one of our database servers -- it looks like it's recovered now.