DATABASE - Is phpMyAdmin.co down? - mysql

I'm working on a project with a DB and whe are using phpMyAdmin.co for administration and I'm not able to connect with my DB administration (phpMyadmin) anymore (yesterday was the last time it worked).
I have tried to reach my host sql7 and phpMyadmin.co and they both didn't work. They where offline.
I've already looked here for the error "Too many connection" and they say I need to adjust something in my administration. But since I can't reach phpMyadmin It's not possible the do that.
Error: Authentication to host 'sql7.freemysqlhosting.net' for user 'sql7269519' using method 'mysql_native_password' failed with message: Too many connections'
Does anyone know if there are some issues with phpMyadmin.co or is there a problem with my code.

Related

Heroku. MariaDB. Access denied for user

I'm creating new app on Heroku. Installed add-on "JawsDB Maria" successfully - I can open it's dashboard
In PHP on connection to DB I receive error:
SQLSTATE[HY000] [1044] Access denied for user 'vcgu1h273742rn5l'#'%' to database 'jeyx2j66ipgtqe11'
I'm sure that problem is not in PHP, because the same error I receive even on MariaDB dashboard trying to Create New Databite - https://prnt.sc/rj4dr4 .
Looks like solution is to GRANT ALL PRIVILEGES to user. But using dashboard I can't execute even SHOW GRANTS.
Questions:
Can somebody help how to solve this problem?
Or, at least, which way I can GRANT ALL PRIVILEGES?
I've tried:
read Heroku docs: JawsDB MySQL, PHP + DB
searching for similar problems in Heroku support, Google, SO:
the best match I found is here. But heroku pg:psql - it's tool only for PostgreSQL.
tried to find useful command for my case in Heroku CLI Commands
Additional info - I'm sure it is not important, but just in case it is:
project is based on Yii2
for easy deployment on Heroku installed "purrweb/yii2-heroku"
You probably know how to read your error message. At any rate, my superpower is explaining the obvious. So, ... here goes.
SQLSTATE[HY000] [1044] Access denied for user 'vcgu1h273742rn5l'#'%' to database 'jeyx2j66ipgtqe11'
Tells you your php program couldn't get to the MySQL server. That operation goes in these steps.
Make a TCP/IP network connection to the server. SUCCESS.
Present a user name and password to the server. SUCCESS.
But the server rejected those credentials. FAILURE
Access the database schema mentioned in the connect request. Not attempted yet. So we have no information about whether the named database actually exists.
The success of step 1 means there are no firewall or network-routing issues. That's good.
The success of step 2 gives us even more confidence about firewall issues.
The failure of step 3 tells us that we're not using a username and password that the MySQL server knows about.
Step 4 is incomplete. So, even if we fix the username and password issues, we still might get another issue before this mess is behind us.
Heroku assigns those usernames to their customers. So, check on the appropriate Heroku control panel to see whether you're using the right username / password credentials. Your error message says you've got wrong credentials.
Next step? Ask your vendor for help. Is Bruce Schneier is reading this? Maybe he can fix this for you from his earbuds while he's riding on the subway. But none of the rest of us here on SO can fix it.
I've waited for 8 hours, hoping there is some trigger, that will complete all necessary settings. But it didn't helped.
Then I reinstalled this add-on. And now all works fine!
So, that was some kind of "JawsDB Maria" bug.

Amazon EC2, mysql aborting even after adding swap space

I have set up a micro instance server on amazon EC2.
mysql server fails frequently and due to which I get 'error establishing a database connection' whenever I access my website. To make my website work again, I have to restart mysqld. Here is the error log. Please click the link as i just opened the account on stackoverflow.
I read through other threads here for the same kind of error and accordingly I added a swapfile of 3G but I am still getting the same memory allocation error. Here is my swapfile.
I am not a technical person so please help me figure out how to solve this problem.

Google Cloud SQL ER_HOST_IS_BLOCKED

i'm getting some issues connecting to Cloud SQL from Container engine...
I followed https://cloud.google.com/sql/docs/container-engine-connect tutorial and it all seems to work, though I had to tweak a few things with the password/user stuff being sent.
However after several failed attempts of the container trying connect using Cloud SQL Proxy I am now seeing this error ER_HOST_IS_BLOCKED: Host '104.197.135.204' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'
FLUSH HOSTS; doesn't seem to fix it.
and I'm unable to change the max_connect_errors value since root doesn't have the super privilege & it's not part of the MySQL flags customizable https://cloud.google.com/sql/docs/mysql-flags
any thoughts?
Got some answers through Google Cloud SQL Slack channel. It was actually related to a different database
However, I did learn that the ER_HOST_IS_BLOCKED is reset whenever a successful connection is made so this should never be an issue

MYSQL error, cannot start service and mysql.sock not found

Yesterday, my website crashed. Or, what appears to be a crash.
My host (JustHost) have disclosed that it was a SAN problem and have been rebuilding it. It's hard to get anymore information out of them because they are playing their cards very close to their chest for some reason.
I have suffered almost 24 hours downtime in 2 days and I'm getting fed up.
The error I am receiving on the frontend of the website is:
Database connection error (2): Could not connect to MySQL.Database connection error (2): Could not connect to MySQL.
Trying to access my phpMyadmin from cPanel gives me the following error:
Accessing SSH and trying to start the mysql service via putty I get:
Starting MySQL. ERROR! The server quit without updating PID file (/var/lib/mysql /mysqld.pid).
Can anyone please help me resolve this issue as my host is rather useless!
Thanks!
Yep, mysqld is down. Did you try running "mysqld_safe&"?
For anyone who wishes to know the conclusion of this issue.
I have been left with 2 choices:
1) Be patient and wait for Just Host to fix the issue and potentially lose my Google search rankings and a lot more future revenue
2) Set up a new hosting account, transfer my data over and wait for the domain to propagate.
I have chosen the latter of the two. My confidence in Just Host as a customer service hub and web hosting provider has thoroughly diminished to the point where all of my hosting accounts will now be switched over to another provider.
They have let me down by not fixing the issue in good time and have passed me from pillar to post in live chat, email support and phone support. The final nail in the coffin was my request for them to backup my databases and send them to me via email being met with the resoundingly passive "sorry, we do not provide that service" response.
I would do it myself if only I had access to phpMyadmin, which I do not have because of a server error that they have been incapable of fixing for the past 72 hours.
Goodbye Just Host.

CakePHP, NearlyFreeSpeech.net, and MySQL

In the last ~week, my CakePHP site has been unable to connect to a MySQL database. Everything is hosted by NearlyFreeSpeech.net and I don't see any problems with the financial aspects of my account.
Does anyone know what's going on?
I'm able to connect to the database with phpMyAdmin and my automated mysqldump calls have worked fine, so I didn't find out right away.
I tried putting up a new CakePHP site using a fresh download from CakePHP but I get the same error message:
Warning (2): PDO::__construct() [pdo.--construct]: [2002] Operation timed out (trying to connect via tcp://cakeht.db:3306) [CORE/Cake/Model/Datasource/Database/Mysql.php, line 177]
Cake is NOT able to connect to the database.
Database connection "Mysql" is missing, or could not be created.
SQLSTATE[HY000] [2002] Operation timed out
Does anyone have any advice?
The problem was magically fixed with the passage of time.
The solution then, is to simply wait an unknown number of days.