Why MySQL Server shutdown after getting some hits - mysql

My website attracts more than 40 thousands unique visitors daily. When it gets 50 visitors simultaneously, sometimes the mySQL server shutdown itself and it gives error: "mysql cannot connect to database server"
the website on vps: its ram is 2 gb.
Is this due to low ram or low ranking features of vps?
When I restart the mySQL server, the problem is resolved.
The website is using wordpress as cms.
If there are some like me facing this issue and not know how they restart the mysql server, here it is: first login your whm and search MySQL, youll see restart MySQl button, click on it. http://www.saderesim.com/SxueS30

Related

mysql lost data rows after reboot

I have an ubuntu server.
I checked the server and I notice that had only 700mb of free hdd space so I restarted. I lost a few days of data in mysql and also I was unable to run apache and I had to installed apache again.
The hard disk now have a lot of free space.
Any of you know what can happen?
Thanks

Unresponsive MySQL database

I've setup a MySQL server on Ubuntu machine.
When running a heavy query (the table has over 1M rows), the database becomes unresponsive.
Upon connection it returns:
Can't connect to MySQL server on 'ip address' (110)
To make it responsive again, I need to kill the process of the heavy query (visible under "show processlist").
Is there a way of preventing this? I used to host the same database on Rackspace MySQL server. Even though it had the same amount of memory, it was more efficient and it never became unresponsive even when running similar queries.

Amazon RDS (Mysql2::Error 110)

I've had a Rails application running in production for the past 6 months, with weekly deployments, without any issue.
Now, I've been having a recurring issue for about 3 weeks and it seems to get worst every week.
When my app boots and reaches the point where it's trying to connect to the DB, I get this error :
Can't connect to MySQL server on '***.amazonaws.com' (110) (Mysql2::Error)
AFAIK, this error tells me that I've reached MySQL's max connections limit.
From the configs, I should be able to open 296 connections. My app is set to run 7 instances with each a database connection pool of 5, so it can't really exceed 70 connections when deploying a new instance.
I've never seen the connection count go above 20 in either the AWS RDS Console or the SHOW PROCESSLIST command.
I don't think it has anything to do with either Rails or my application server (Puma), since I can't connect through the MySQL Command-Line Tool when the issue occurs.
Has anyone had a similar issue with MySQL on RDS or MySQL itself?
The database pool isn't per application, it's per process. If it's threading/multi process per instance it could be using more than that. Have you tried restarting mysql? It sounds like you have some hanging connections for whatever reason.
I've been getting these issues recently. Could it be related to the pending-restart change of parameter group on my RDS Instance? I sure hope not. As I understand a pending change should have no effect on the current performance.

AppHarbor MySql Yocto connection error

My AppHarbor Web Instance uses the free MySql Yocto 20 MB plan, off late I'm seeing "Unable to connect to any of the specified MySQL hosts". Is this because the database used up the free 20 MB or is MySql really down right now, I am not able to figure it out.
Is there any straight forward way of finding the curent database memory size that would be proportional to the plans published w.r.t MySql AddOn.
We've had problems with our MySQL service in connection with a big Amazon Web Services outage. The MySQL service should be restored now, at least to read-only mode. We're tracking the situation closely.
The error you're seeing is unlikely to be related to database size issues.

how can I repair a mysql connection?

I use XAMPP 1.7.3
If I try to open phpMyAdmin it will try to open but eventually I'll have only a blank page, no errors.
If I try to connect with Navicat, the same thing, it will not be able to establish a connection.
And usually this process takes between 30% and 60% of the processor for more than 20 min.
If I stop and then start again the mysql server from XAMPP Control Panel the message is 'Mysql server started'.
But If I go to http://localhost/xampp/ and then 'Status' everything is 'Activated' EXCEPT ' MySQL database', 'SMTP Service', 'FTP Service' which are 'Deactivated'.
I think I crashed the Mysql server after I tried to make a database backup BUT the laptop closed before the backup was finished (the battery was discharged).
How can I repair the connection to the Mysql server?
First, make sure to double check the obvious, most likely these are not the issues since it happened after you closed your laptop, but it doesn't hurt to double check:
Make sure the MySQL service is running...
Also make sure that a firewall is not blocking port 3306...
This guide covers both MyISAM and InnoDB: http://www.softwareprojects.com/resources/programming/t-how-to-fix-mysql-database-myisam-innodb-1634.html
Now, assuming that the tables are MyISAM, you can repair them by following this guide:
http://colekcolek.com/2011/11/02/repair-corrupted-mysql-myisam-table/
Here is a way to do it for InnoDB: http://code.google.com/p/innodb-tools/