View Full Version : Table in use?
Sometime during the mysql debacle over the past few days, my MediaWiki installation broke. Trying to load any page in it gives this error message:
Database error
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "MediaWikiBagOStuff::_doquery". MySQL returned error "145: Table './em_main/bots_wiki_objectcache' is marked as crashed and should be repaired (mysql10.powweb.com)".
In phpmyadmin, if I click on my database on the left and scroll through the tables in it, all columns to the right of "drop" for bots_wiki_objectcache (the broken table) are combined into one column that says "in use". Repairing the table didn't seem to work. I got this message when I tried:
Table is already up to date
I couldn't find anything on MediaWiki's site about the error message and couldn't turn much up on Google either. If I had to guess, I'd say it's more likely an issue with mysql than MediaWiki. Is this something I am able to fix or should I contact support?
I'd say contact support.
I've read elsewhere in the forums about other people having the same problem when trying to repair tables since the upgrade......hit repair and it says "Table is already up to date"
I'm also one of those people and am waiting for someone to help.....but yeh, support is probably the best way to go.
Contact support - I've seen reports of 'in use' problems before and usually it is support who can rectify the situation as they have higher permissions than customers do.
All right thanks, will do.
How long do these types of issues typically take to be resolved?
I got a quick response to my original ticket, but they needed some more information. I reopened the ticket and added what they needed, but haven't heard back since. All of this happened on the 23rd (7 days ago).
entrecon
8-30-07, 10:54 AM
In my experience re-opened tickets seem to get lost/ignored. I know support and the staff that check-in here will tell you to log it on the original ticket, but I have found I get quicker response on new tickets.
I was wondering if that was the case. I've never gotten a response to a re-opened ticket. Maybe there's a bug in their support system.
Thanks though, I'll try opening a new one.
dmacminn
8-30-07, 04:40 PM
Re-opened tickets actually get higher priority than new tickets ...but they may re-open assigned to the person who last replied (who may or may not be the person who worked on the ticket previously), so there might be a brief delay until that person initiates new action or the system transfers the ticket to the next available specialist....
When we're not terribly busy, it may be that the new ticket seems to get dealt with first -- but what generally happens is that the old ticket gets located, and is merged into the new (or vice-versa) for context and then the ticket is re-diagnosed if required...
I would encourage you to use the same ticket for the same issue (and stick to one issue! just like a Forum thread) as it automatically includes all the context of the previous events.
If it runs beyond 48 hours with no action in the Support Center, then its fair to add an additional comment or inquiry in the Support Center...
Now, to these database errors -- I would encourage you to do a backup of the current database as soon as you can, and download the earliest backup showing in the View Backups, immediately! Remember that the system will roll it over the next day and it will be gone...
You may have to disable your application temporarily to be sure that it has no open connections to the database -- that way, AFTER you have the backup, you can try a repair table, or import the damaged table from a recent backup.
It will quite often take up to 24 hours if you request an action be performed on database, because a very small number of people have direct access to the MySQL system -- everybody else uses exactly the same tools as you do (MyPHPAdmin) and the OPS system for access to databases; so, again, you can generally do anything related to your DB yourself -- unless it is too large.
Thanks for the response, dmacminn. I hadn't yet opened the new ticket I said I was going to yet, so I'll hold off on that. You mentioned a 48 hour guideline for additional inquiries...it's been just over 6 days without a response now though, so I guess I'll add another comment.
Unfortunately I did not think to download a backup of the database when I first noticed this problem. I would estimate it began around the 20th and being as though the backups exist only for the 28th and 29th, I'd say that solution will not work for me. :(
I tried exporting the table, but that didn't work. It just gives me that error message about the table being crashed and needing repair. I tried repairing again through phpMyAdmin, but that doesn't fix it either.
Searching around on Google for the "table in use" error message, I couldn't really turn up much. In a couple of cases, the solution was to just repair the table, but that didn't work for me. One said that restarting their server worked, but obviously this isn't an option here. Another solution said to try "FLUSH TABLES WITH READ LOCK", but when I tried that it told me I need the "RELOAD" privilege.
How often are the MySQL servers rebooted? :D
8/20 (roughly) - problem begins during MySQL upgrade
8/23 - I opened a support ticket
8/23 - I got a reply from support requesting more detailed info
8/23 - I reopened the ticket and added the additional info
8/30 - I updated the ticket saying I'm still having problems
9/5 - I updated the ticket, again saying I'm still having problems
I've been in the dark for a couple weeks now. I'm trying to be as patient as possible, but it's getting difficult because I feel ignored.
What should I do?
With that kind of delay and my experience with re-opened tickets....submit a new ticket with all of the detailed information.
Do you have a backup from before the 20th?
You might need to restore the table if support can't fix it.
8/20 (roughly) - problem begins during MySQL upgrade
8/23 - I opened a support ticket
8/23 - I got a reply from support requesting more detailed info
8/23 - I reopened the ticket and added the additional info
8/30 - I updated the ticket saying I'm still having problems
9/5 - I updated the ticket, again saying I'm still having problems
9/10 - I created a new ticket
No response to neither the old ticket nor the new ticket as of today (9/14).
I think what I'm going to end up doing is trying to extract as much information about the wiki as possible from my database (can't access the web interface of the wiki at all) and then try to import that intn a clean installation. Ideally I won't lose any data in the process, but that seems like a crapshoot unfortunately.
Well support finally got back to me, and after a few emails they were able to repair the corrupted table. My wiki once again works.
Some stories do have happy endings. :D
vBulletin v3.6.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.