MySQL down / password failure?

[relax]

As of a few moments ago I suddenly cannot access the MySQL database anymore. When using the link from ops, I suddenly asks for a password. And when entered it says
We are sorry, the password you entered does not match our system. Please verify your password and try again.
This happens on all my databases

[relax]

Update: seems to be working again.

[entrecon]

I haven't done early morning work in a while, but I had noticed in the past that somewhere between 5am and 7am eastern time I would see some outage on my sites. I figured it was some kind of system maintenance.

[pureconcepts]

This is still down. It has been over 24 hours for me. This isn't a temporary outage, something is wrong with the OPS page.

[Doc C]

Hopefully you've reported it to Support and aren't just waiting for it to fix itself.

[IanS]

Seems as if no-one else is exeriencing the problem it's not a case of the OPS/MySql systems aren't working but more of they've been disabled (either on purpose or accidentally) by someone/some program.

If there'd been a general outage, the forum members would be vociferous in their indication that they're unhappy. You're a lone voice, so it is likely that it's not a general outage and Doc's suggestion of contact with Support is, indeed, a good one.

[omatic]

I have the same problem today. It's insisting that my password is a non-match, which is nonsense. I even updated it via ops to make sure I wasn't making a typo.

Then I created a second account to replace the first, as none of my scripts were able to use the DB and of course, all my php/mysql content is dead in the water. Within MINUTES that account started complaining about password mismatches too. PhpMyAdmin booted me in midsession as well.

So I got on the horn (live chat) and (long story short) there was no resolution. I was told it would be escalated and it would be addressed in 24-48 hours. Bleah!! I hope they fix it faster than that. There's nothing wrong with the account IMHO. Sounds like the MySQL server needs to be bounced.

[omatic]

Incidentally, I tried to log into my other two databases. One works (for now) and the other, the other has the same problem. So this problem is not limited to just my main database.

[mpk]

If you are still seeing this issue send me a PM with your ticket number, domain name, and url where the db connection is required.

[omatic]

If you are still seeing this issue send me a PM with your ticket number, domain name, and url where the db connection is required.Thank you for your direct concern mpk.

However, I think the database was irretrievably corrupted. It was bad enough that I wasn't even able to even gingerly approach my two most-critical tables in phpMyAdmin. Any operation (even an attempt to view structure) caused deadlocks. CHECK TABLE, REPAIR TABLE, etc. had the same problem. I had to close my browser, re-log-into Ops, and kill the previous Processes upon reentering phpMyAdmin. If I didn't, it'd just freeze the phpMyAdmin session again.

So at last, I gave up, and started a new database. I had a very recent backup (thank you Ops) and restored my tables to that. I am underway with the new database, and plan to drop the old one in a day or two. Let's hope this mess doesn't repeat itself! That database was around over 5 years though, so God knows how much it's been through. Maybe it was just time for it to croak.

Good luck to all with a similar (or possibly the same) problem.

Thanks again.
Mike AKA omatic

PS. I will manually close the ticket myself to prevent unnecessary effort by your folks.