Dealing with SQLSTATE errors

You got 500phtml error >enabled debug mode >saw SQLSTATE error. What to do next?

SQLSTATE errors indicate that something is wrong in the way script communicates with your database. This document lists most common SQLSTATE errors reported by Oxwall community members and ways to deal with them.

 Message: SQLSTATE[HY000]: General error: 126 Incorrect key file for table '/var/tmp/#sql_3ce9c_0.MYI'; try to repair it 

• Reported to happen when: varies
• Status: Server configuration. Not a bug.
• Caused by: /tmp folder running out of space on client's server.
• Links to discussions on Oxwall forum:
• * http://www.oxwall.org/forum/topic/16126?page=1#post-81101
• * http://www.oxwall.org/forum/topic/16031?page=1#post-81098

Message: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 0, 1' at line 1

• Reported to happen when: signing in using Facebook Connect.
• Status: Oxwall Software bug. Fix planned for 1.6
• Caused by: special symbols in user's name on Facebook. Example: Öliya
• Link to discussion on Oxwall forum:
• *http://www.oxwall.org/forum/topic/3834?&page=2
• *http://www.oxwall.org/forum/topic/16031?page=1#post-81098

Message: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'table_name” doesn't exist.

• Reported to happen during: installation, core update, plugin updates.
• Status: Varies.
• Caused by:
  • * server side issue.
  • * corrupted plugin/core archives
  • * upload was not finished completely/successfully
  • * mismatching versions of core and plugins.
• Solution:
  • * contact hosting company to find out whether they had any downtimes on their end
  • * reinstall or run update again
  • * contact plugin developer
  • * check whether your server meets our requirements
  • * make sure that all of your plugins are up to date.
• Links to various discussions on Oxwall forum:
  • * http://www.oxwall.org/forum/topic/8625
  • * http://www.oxwall.org/forum/topic/9298?&page=1
  • * http://www.oxwall.org/forum/topic/7751
  • * http://www.oxwall.org/forum/topic/14969
  • * http://www.oxwall.org/forum/topic/8138
  • * http://www.oxwall.org/forum/topic/3306
  • * http://www.oxwall.org/forum/topic/8056

Message: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry ‘2145871224’ for key “PRIMARY”

• Screen shot of the exact error message
• Reported to happen when: using “Newsfeed” plugin.
• Caused by: duplicate entries in database ( known to happen on sites with lots of data).
• Solution: truncate ow_newsfeed_action_set database table.
• Link to the solution on Oxwall forum: http://www.oxwall.org/forum/topic/11519?page=1#post-58164

Message: SQLSTATE[08S01]: Communication link failure: 1153 Got a packet bigger than 'max_allowed_packet' bytes

• Reported to happen when: sending mass mailing.
• Status: Server configuration. Not a bug.
• Caused by: the length of the request exceeding the MySQL limit of max_allowed_packet. The limit is set to1M by default.
• Solution: Increase max_allowed_packet value. Root access required. If you don't have root access, contact your host. If you do have root access: http://forums.cpanel.net/f34/how-increase-max_allowed_packet-361521.html
• Link to the solution on Oxwall forum: http://www.oxwall.org/forum/topic/15187

Message:SQLSTATE[HY000]: General error: 1030 Got error 28 from storage engine. Unknown: write failed: No space left on device (28) File: Unknown Line: 0

• Reported to happen when: loging in as any user.
• Status: Server configuration. Not a bug.
• Caused by: no space left.
• Solution: clean up unneeded files. Example: clear the /tmp folder to free up hard drive space on the server root.
• Links to discussions on Oxwall forum:
  • * http://www.oxwall.org/forum/topic/9039
  • * http://www.oxwall.org/forum/topic/1117

Message:SQLSTATE[28000] [1045] Access denied for user 'user@localhost(using password: YES)

• Reported to happen when: software installation is completed.
• Status: Server configuration. Not a bug.
• Caused by: incorrect permissions given to user over the certain database.
• Solution: granting the user all privileges to the database.
• Links to discussions on Oxwall forum:
  • * http://www.oxwall.org/forum/topic/2678
  • * http://www.oxwall.org/forum/topic/11025
  • * http://www.oxwall.org/forum/topic/1961
  • * http://www.oxwall.org/forum/topic/2275