Mysql Error Errno 145
Updates: Status: Not a Bug Impact on me: None Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical) Version:4.0.15 Binary&Source OS:Linux (Linux Redhat) Assigned to: View Add Comment Files Developer Edit Submission View Progress Log Contributions [25 Sep 2003 3:53] Tom Sommer Description: Some of our customers are experiancing problems after we upgraded our mySQL servers to MySQL 4.0.15 They are at random intervals receiving this error: Can't open file: 'example.MYI'. (errno: 145) When we move them to a MySQL 3 server, they have no problems. We first used the source tarball but switched to the binary version to see if that could resolve our problem, but it did not. The problem only occurs on a few number of customers, compared to the total number. But the situation is still unacceptable How to repeat: Unknown Suggested fix: You can repair the damaged table, but the problem WILL reoccur again [25 Sep 2003 4:05] Tom Sommer I should note we used version 3.23.54a prior to upgrading And also that this error also occurred in 4.0.14 [25 Sep 2003 11:50] Indrek Siitan How often does this occur? It would be great, if you could provide us with a repeatable test case. To do this, can you follow these steps next time the corruption occurs: 1. Shut down the MySQL server 2. Take a copy of the 3 table files of the corrupted table 3. Fix the table with myisamchk 4. Add "log-bin" and "log-isam" into your /etc/my.cnf [mysqld] section. 5. Start the server. Now, if the corruption happens again, send us the following: * the corrupted table files from the first corruption * binary and MyISAM log generated since first corruption * corrupted table files from the second corruption [14 Feb 2005 22:54] Bugs System No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". [1 Sep 2006 10:34] dimitri hilverda I got this same error after upgrading on a linux RH enterprice server. is there a fix for this? My supportdesk tels me that this is the only version that works with plesk. Is there a way to rollback to the old version? [29 Jan 2011 19:10] Rahul Rajpal There is an easier way to repair the corrupted tables and recover data from them. To do so, the administrator needs to go on this link: http://www.datarecovery-info.com/database-recovery/mysql-recovery.html [3 Feb 2011 17:27] Valerii Kravchuk While recent comment is useful, I still see nothi
that make connections all over the world. Join today Community Community Home Getting Involved Chat Forum SupportInstalling Drupal user error: Can't open file: 'node.MYI'. (errno: 145) Posted by phil1011 on August 23, 2003 at 8:32pm Using version 4.10. I only tried to update a book page, and pressed Preview, then made a few changes and pressed Submit when everything went awry with the following error messages: On the home page: user error: Can't open file: 'node.MYI'. (errno: 145) query: SELECT n.nid FROM node n LEFT JOIN book b ON n.nid = b.nid WHERE b.parent = 0 AND n.status = 1 AND (n.moderate = 0 OR n.revisions != '') ORDER https://bugs.mysql.com/bug.php?id=1398 BY b.weight, n.title in /usr/www/users/photojpn/notes/includes/database.mysql.inc on line 69. user error: Can't open file: 'node.MYI'. (errno: 145) query: SELECT MAX(created) FROM node WHERE type = 'poll' AND status = '1' AND moderate = '0' in /usr/www/users/photojpn/notes/includes/database.mysql.inc on line 69. On the Administration page: user error: Can't open file: 'node.MYI'. (errno: 145) query: SELECT n.nid FROM node n LEFT JOIN book b ON n.nid = b.nid WHERE b.parent = 0 AND n.status = 1 AND https://www.drupal.org/node/2597 (n.moderate = 0 OR n.revisions != '') ORDER BY b.weight, n.title in /usr/www/users/photojpn/notes/includes/database.mysql.inc on line 69. user error: Can't open file: 'node.MYI'. (errno: 145) query: SELECT MAX(created) FROM node WHERE type = 'poll' AND status = '1' AND moderate = '0' in /usr/www/users/photojpn/notes/includes/database.mysql.inc on line 69. What do I do? Should I upgrade to 4.2? I'm not a PHP programmer. phil Log in or register to post comments Comments MySQL broken killes@www.drop.org commented August 23, 2003 at 9:14pm Seems to me that your MySQL installation went foobar. node.MYI would be a file where MySQl stores data for the node table. --Drupal servicesMy Drupal services Log in or register to post comments Thanks for the reply. I don't phil1011 commented August 23, 2003 at 10:14pm Thanks for the reply. I don't operate my own server. Both MySQL and PHP are on my Web host's (pair.com) server. What should I do? phil Log in or register to post comments Ask your hoster killes@www.drop.org commented August 23, 2003 at 11:25pm Ask the tech support. They are supposed to know what is going on on their machines. --Drupal servicesMy Drupal services Log in or register to post comments Thanks! phil1011 commented August 24, 2003 at 10:23am Thanks for the quick advice. They fixed it for me. Log in
21, 2016, 02:26:49 AM Welcome, Guest News:cpg1.5.44 Security release - upgrade mandatory!The Coppermine development team is releasing a security update for Coppermine in order to counter recently http://forum.coppermine-gallery.net/index.php?topic=10409.0 discovered vulnerabilities. It is important that all users who run version cpg1.5.42 https://www.godaddy.com/help/why-do-i-get-a-mysql-error-1016-cant-open-file-5116 or older update to this latest version as soon as possible.[more] Home Help Board Rules Search Login Register forum.coppermine-gallery.net > No Support > General discussion (no support!) > Topic: Typical Error: Can't open file: 'cpg131_pictures.MYI'. (errno: 145) « previous next » Pages: [1] Go Down Print Author mysql error Topic: Typical Error: Can't open file: 'cpg131_pictures.MYI'. (errno: 145) (Read 44380 times) 0 Members and 2 Guests are viewing this topic. kegobeer Dev Team member Coppermine addict Offline Gender: Posts: 4637 Beer - it does a body good! Typical Error: Can't open file: 'cpg131_pictures.MYI'. (errno: 145) « on: September 29, 2004, 03:43:11 AM » The error:Can't open file: 'cpg131_pictures.MYI'. mysql error errno (errno: 145)The problem:Your table is corrupted.The solution:Use your website's Control Panel to repair the table, or use phpMyAdmin to execute this sql query: repair table cpg131_pictures(Replace cpg131_pictures with your table name) « Last Edit: May 15, 2006, 08:00:33 AM by GauGau » Logged Do not send me a private message unless I ask for one. Make your post public so everyone can benefit.There are no stupid questionsBut there are a LOT of inquisitive idiots AssyMassy Coppermine newbie Offline Posts: 1 Re: Typical Error: Can't open file: 'cpg131_pictures.MYI'. (errno: 145) « Reply #1 on: June 20, 2005, 01:07:45 PM » I had the same problem, and I tried youre solution. I did the sql-query "repair table cpg_pictures" but all i got is the same error mesage agein. he can't open th e file so he can't repair the file.'I do noticed that it was the only table with the message "in use" what does that mean?Any ideas on what to do next?I have hardly any experience with this kind of stuf so I hope it doesn't beco
Name:VIP Acct Exec:Pro DashboardMy ProductsAccount SettingsMy RenewalsLog OutLog InMenuHelpGetting StartedCommunitySystem StatusBack|Home Full SiteCommunityHelpWeb & Classic HostingWeb & Classic Hosting HelpContact Us 24/7 Support (480) 505-8877 Why do I get a MySQL "error: 1016 Can't open file: ..."?Errors such as: ..."Got error: 1016: Can't open file: 'YOUR_TABLE_NAME.MYI'. (error:145) when using LOCK TABLES"... (as well as numerous other noted below) are caused by MySQL table corruption. Table corruption can be caused by a variety of events, and will make some or all of a table unavailable. Table corruption can also significantly decrease the performance of queries on effected tables. Table corruption can be be repaired by using the the REPAIR TABLE command. For more information about the REPAIR TABLE command see: MySQL 4.0, 4.1 http://dev.mysql.com/doc/refman/4.1/en/repair-table.html MySQL5.0 http://dev.mysql.com/doc/refman/5.0/en/repair-table.html Run REPAIR TABLE on an affected table Enter phpMyAdmin for the database you want to use. For more information, see Log in to phpMyAdmin. Click on the table name of the affected table. If phpMyAdmin is unable to display the table information, or encounters errors loading the table details page, another option would be to use the SQL button at the top of the left frame to enter your own query. You can repair the table manually by issuing the command REPAIR TABLE in this SQL window. Click on the Operations tab at the top of the right panel. Click Repair table at the bottom of the right panel. This command can take some time and will block some queries, such as inserts, to the table. WARNING:It is possible that the phpMyAdmin Web server will time out waiting for a response from this command. If this happens, do not issue it again. Use the processlist feature, and you'll likely see the REPAIR command still running. Wait for it to complete. On large tables, this can take hours. Some other errors that may be caused by table corruption include: Can't find file table.MYI. Duplicate unique key or constraint on write or update. Got error ERR from table handler. (ERR being a number). Index file is crashed / Wrong file format. No more room in index file. No more room in record file. Old database file. Record file is crashed. Record was already deleted (or record file crashed). table.frm is locked against change. Table is crashed and last repair failed. Ta