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 [2018/05/29 20:11]
Daniel P.
developmental:troubleshooting-database-connection-errors [2018/05/30 11:44] (current)
Daniel P. [InnoDB Forced Recovery]
Line 281: Line 281:
 To check for crashed MyISAM tables, run the following command, and if errors are present, check that the date for which they are present is, in fact, the current date (cPanel will detect and automatically fix crashed tables for you in most cases, which is why you would need to check the date of the errors): To check for crashed MyISAM tables, run the following command, and if errors are present, check that the date for which they are present is, in fact, the current date (cPanel will detect and automatically fix crashed tables for you in most cases, which is why you would need to check the date of the errors):
  
-  grep -i crash /​var/​lib/​mysql/​HOSTNAME.err+  grep -i crash /​var/​lib/​mysql/​`hostname`.err
  
 You will see errors such as this: You will see errors such as this:
Line 337: Line 337:
 You may want to watch the error log in a separate terminal while running this command: You may want to watch the error log in a separate terminal while running this command:
  
-  tail -f /​var/​lib/​mysql/​HOSTNAME.err+  tail -f /​var/​lib/​mysql/​`hostname`.err
  
 If your databases are very large, then you may want to use the screen utility to run the command above in to make sure that it can complete even if you log out: If your databases are very large, then you may want to use the screen utility to run the command above in to make sure that it can complete even if you log out:
developmental/troubleshooting-database-connection-errors.txt · Last modified: 2018/05/30 11:44 by Daniel P.