KNOWNHOST WIKI

User Tools

Site Tools


developmental:troubleshooting-database-connection-errors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
developmental:troubleshooting-database-connection-errors [2019/09/06 18:33]
Karson N.
developmental:troubleshooting-database-connection-errors [2019/10/11 13:25] (current)
Karson N.
Line 50: Line 50:
 You may see output with errors similar to these: You may see output with errors similar to these:
  
-{{:​developmental:​ooms-killer.png?​direct&​1200|}}+{{:​developmental:​ooms-killer.png?​nolink&​1200|}}
  
 If this is the case, then you should immediately check your domlogs (domain access logs) for abuse, such as Wordpress login brute forcing, XMLRPC abuse, or DoS attacks. Please don't hesitate to ask KnownHost support for help with this if you are experiencing Out of Memory errors! ​ If this is the case, then you should immediately check your domlogs (domain access logs) for abuse, such as Wordpress login brute forcing, XMLRPC abuse, or DoS attacks. Please don't hesitate to ask KnownHost support for help with this if you are experiencing Out of Memory errors! ​
Line 75: Line 75:
 The last number listed is the count of OOMs. If no OOMs have occurred, then your output will look like this: The last number listed is the count of OOMs. If no OOMs have occurred, then your output will look like this:
  
-{{:​developmental:​beancounters.png?​direct&​1000|}}+{{:​developmental:​beancounters.png?​nolink&​1000|}}
  
 If OOMs have occurred, as in the case of the following server which has had 126K, you will see the number of OOMs that have occurred: If OOMs have occurred, as in the case of the following server which has had 126K, you will see the number of OOMs that have occurred:
  
-{{:​developmental:​129kooms.png?​direct&​1000|}}+{{:​developmental:​129kooms.png?​nolink&​1000|}}
  
 If OOMs are occurring too frequently to be logged via /​var/​log/​messages,​ then you will want to watch this number. This does sometimes occur where OOMs are happening but are not being logged on the server, though the fail count is logged to /​proc/​user_beancounters. ​ If OOMs are occurring too frequently to be logged via /​var/​log/​messages,​ then you will want to watch this number. This does sometimes occur where OOMs are happening but are not being logged on the server, though the fail count is logged to /​proc/​user_beancounters. ​
Line 99: Line 99:
 You will see something similar to this showing that you have reached 100% disk space utilization,​ or are within MB of doing so: You will see something similar to this showing that you have reached 100% disk space utilization,​ or are within MB of doing so:
  
-{{:​developmental:​df-h_.png?​direct&800|}}+{{:​developmental:​df-h_.png?​nolink&800|}}
  
 Or try to log into WHM. The following error is typically shown when you have exceeded your disk space and try to access WHM: Or try to log into WHM. The following error is typically shown when you have exceeded your disk space and try to access WHM:
  
-{{:​developmental:​diskfull.png?​direct&​1200|}}+{{:​developmental:​diskfull.png?​nolink&​1200|}}
  
 When your disk space is exceeded, you can only correct it by accessing via SSH. If you are uncomfortable with SSH, open a support request with KH support setting the priority Critical, and we will work quickly to find what is consuming space and get you back online. When your disk space is exceeded, you can only correct it by accessing via SSH. If you are uncomfortable with SSH, open a support request with KH support setting the priority Critical, and we will work quickly to find what is consuming space and get you back online.
Line 113: Line 113:
 You will get output similar to this: You will get output similar to this:
  
-{{:​developmental:​du.png?​direct&​1000|}}+{{:​developmental:​du.png?​nolink&​1000|}}
  
 For this particular server, you can see that 22G is in /backup, and 11G in /home. If you wanted to look further into what is in /home, you can do so as follows: For this particular server, you can see that 22G is in /backup, and 11G in /home. If you wanted to look further into what is in /home, you can do so as follows:
Line 142: Line 142:
 You'll see output similar to the following: You'll see output similar to the following:
  
-{{:​developmental:​max_con.png?​direct&800|}}+{{:​developmental:​max_con.png?​nolink&800|}}
  
 If the value of Max_used_connections ​ from the first command is the value of max_connections + 1 or more, then the max_connections for MySQL have been exceeded. ​ For example, if the Max_used_connections is 51 but the max_connections is 50, then you did exceed your max_connections. As long as traffic looks legitimate and you have sufficient RAM to support the increase, you can increase this setting in the MySQL configuration file by doing the following: If the value of Max_used_connections ​ from the first command is the value of max_connections + 1 or more, then the max_connections for MySQL have been exceeded. ​ For example, if the Max_used_connections is 51 but the max_connections is 50, then you did exceed your max_connections. As long as traffic looks legitimate and you have sufficient RAM to support the increase, you can increase this setting in the MySQL configuration file by doing the following:
Line 312: Line 312:
 Here is what this type of repair looks like: Here is what this type of repair looks like:
  
-{{:​developmental:​repairing_crashed_myisam_table_.png?​direct&800|}}+{{:​developmental:​repairing_crashed_myisam_table_.png?​nolink&800|}}
  
 Occasionally,​ this repair will fail due to a temporary table. The error will read something similar to this: Occasionally,​ this repair will fail due to a temporary table. The error will read something similar to this:
Line 320: Line 320:
 Here is what this error looks like when you encounter it after attempting to repair a table via the MySQL CLI: Here is what this error looks like when you encounter it after attempting to repair a table via the MySQL CLI:
  
-{{:​developmental:​temp-table_error_.png?​direct&​1000|}}+{{:​developmental:​temp-table_error_.png?​nolink&​1000|}}
  
  
developmental/troubleshooting-database-connection-errors.txt · Last modified: 2019/10/11 13:25 by Karson N.