Any thoughts?

errno: 145 is a corrupt table. You'll want to run the following SQL command:

REPAIR TABLE ubbt_POSTS

yes except remember to put an I in the repair...

Oopsie Edited my post

trying that - no luck so far

Do you get any info back when you run the command?

If you have shell access:
myisamchk -r ubbt_POSTS.MYI

@Rick

Didn't you make a change to one of the cache tables or something like that in 7.1b?? for similar issue?

no just times out in phphmyadmin

You should run commands through the command line; the php script (phpmyadmin) likely times out because your tables are so large.

I would if I knew the syntax LOL

I am now throwing money at it, in the vain hope of getting them back up.....

Not looking to good at the moment....

Looks like You're back up now. Were you able to get this fixed yourself or did your host need to do it?

Yes, i'm quite curious how it got fixed as well as repair didnt seem to do much...

just a case of keep repairing.... Fixed the posts, but then other tables were also corupted.

Ahh, did you use my sugguestion of not using phpmyadmin to repair tables? lol

after I tried....

lol, and did it work better?

nah - only after I took down mysql and had all my clients calling me here in Hong Kong saying their email was down....

expensive calls to whine ;)... I hope they weren't calling your uk #...

yep... my mobile... (cell to you)

'eh you sent me a list of a ton of numbers, i looked at them and shrugged lol

hehe - my washington number would work for you Will either end up on my PC as VOIP or divert to my mobile....

I always love when peopel talk about Washington, generally they referr to Washington DC, but with Washington (state) being above me I sometimes get confused ;)...

If multiple tables were corrupted it definitely sounds like an issue that could be trouble. Single table corruption can happen, but when it's multiple tables this points to a larger problem.

I hope this never happens to me!

What would, or could, cause such a problem?

Poor slow hardware normally. If it tries to do a read and can't get a response it's not too bad, but if it can't write because it's too busy or too slow then you have problems.

There are thousands of MySQL databases out in the World and Business running very large sites with no problems.

Wikipedia which is big runs on MySQL

certainly not poor slow hardware - thank you!

Not trying to anger you or step on your toes but slow hardware most certainly can cause corruption. There are certainly other things that can cause it though.

I think initially looking at the error log it was just the massive posts table - then the users table became corrupted once the posts had been fixed.

Sorry Ian, I was only replying to Daryl's question, not meaning your db issue.

oops - my apologies - it is 04:30 here and I have a plane to catch, so I will use that as my excuse

You know, I've been logged into his server all night checking sar often; the iowait isn't half bad so it's likely not a hw issue; though he does have occasional spikes...

table has corrupted again...

trying to repair from database tools within threads

not sure how long one table takes - but it is a good 45 minutes so far

timed out

I am walking away from this now...

Which table is it this time, the posts table or the topics table?

posts again

Hmm, what version of MySQL are you currently running? There are certain versions that are more prone to corruption than others and since the posts table is actually written to less often in this version than prior versions there is definitely something funky going on.

You might try and check the uptime of MySQL to see how long it's actually been running, possibly stopped and restarted during a write? It could be anything like memory, cpu or a hard drive issue.

One thing, make sure you close your forums while trying to repair it. Since it's the post table it can take awhile because it is one of the larger tables. But if your forum is still open while working on it, it can actually corrupt it further.

I think the forums were closed, and still are.

repaired the table - can't reach the site though.

getting no mysql errors in the logs for the site.

Do you have server level access? If so, then the best bet would be to try and repair directly from the MySQL prompt.

If you can't reach the site, the repair you ran through threads might still be running. If you have direct access, then you can check if it's still running by typing in "show processlist" from the mysql command prompt.

What version of MySQL are you running? There are several versions of MySQL that are more prone to corruption, in their release notes they do mention a few versions that were updated for this reason, so a MySQL upgrade might be in order.

SQL Error: Can't open file: 'ubbt_POSTS.MYI' (errno: 144)

If you can try and repair directly from within MySQL , you'll actually get some useful information at the end of the repair. That will give some information on what happened if the repair failed.

It could be something as simple as out of hard drive space on the MySQL partition.

I had the same problem, but only once so far.

I tried the repair table, etc. without any success.

The only way I was able to function again was to have the host server provider import a back-up that they had fortunately done.

Rick, his load from mysql at times shows 250 in the cpu column of TOP, it's insane the load being produced on his server lol...

Yeah, I think we've narrowed it down to one of the users on the server. I saw a spike this morning where mysqld was showing 325% cpu usage.

Theres also some command named "VV" that seems to be provided by some software installed "Linux Agent" that also takes up its share of resources:
20670 root 18 0 16284 3676 1960 R 67 0.2 5:21.46 VV

Lol you have a shell on his box too huh?

I have a shell on everyone's box Ok, not everyone's, but if someones having a problem it's the easiest way to find the root cause.

Lol, I think you have a shell on both my VPS and home dev machine lol... so I'll go with the idea that you have a shell on everyones box ;)...

can't find this VV thing or agent linux - must be looking in the wrong place.... LOL

Wow so that's like a super computer ? How do you get more than 100% I might need that kind of magic on my system

.

Not sure where it's hiding itself, but an example of the process name:
^[[m^O 7254 root 18 0 16284 3720 1960 D 2 0.2 14:08.89 VV

Above it's only using .2% of your memory, and 2% of your processor; but it's been MUCH higher (keep in mind i sat there and let it run for quite the while as i played FFV so i watched it pop up time and time again...

That is a backup - it should only run at night (GMT) - might be intensive for short periods.

ahh... ok would make sense...

Myself, I just use a crontask to tell "tar" to backup space, then ncftp to send them to my machine

backups have been a nightmare on my machine LOL They seem to grind threads to a halt at night LOL

tar and ncftp are two very basic systems that shouldn't be too resource intensive; i can't vouch for the utility that you currently use.

we have two systems - the once above works fine - it is an incremental backup that allows individual files to be restored easily.

ahh, likely why it can be system intensive then ;)...

Myself what I'd do would be to have two backup cycles, one that does a full backup every month (or week) which tells mysql to dump all db's then tar up those dbs, then tar up your webspaces, then tar both of the tarred files together (easier to keep track of).

Then I'd have another which backs up MySQL every week (or day) then tar those files (compress with bzip to save space).

Then you'd have daily backups of sql data which generally constantly changes, and then monthly backups of your site space, basically similar to what i use.

far too complicated for my little mind LOL

for me its as easy as setting a crontask to run /home/gizmo/backup.c monthly and /home/gizmo/incrimental.c weekly ;)...

crons are easy - it is the script they run

yeh well customizing said script isn't the hardest task once you've played with all of the commands lol...

Like i said, it's my hobby lol

hobby away then LOL

What do I get? :x...

corrupted again

Trying to repair once more....

I know that repairing takes quite a while but I have done..

mysql> REPAIR TABLE ubbt_POSTS;

I assume it is correct just to sit on a blank line - I do not get any progress. Is this correct? Never done it via this method before, so unsure. But assume it is correct.

I guess that was wrong - just sat there for about 2 hours.

trying alternative method now....

right back up again...

gone again - this is getting beyond a joke....



it really does look like threads from what I can see.

We now have numerous posts that do not exist - these are all numbered 0 - i.e. http://www.fansfocus.com/forums/ubbthreads.php?ubb=showflat&Number=0


When I look at the process list there are several instances for the forums, but they are all locked. At the same time the load increases to 15+ and that is when the database corrupts.

BTW - rick that other process has now been uninstalled, that was causing some spikes.

so far so good - fingers crossed...

I went to your site and didn't have any problem accessing any I selected, except for the link you previously provided, therefore, it does seem to be a selective threads problem.

I have had 919 posts in the last 24 hours, so any problematic ones tend to get pushed down on some forums.

There are still some.

Of course my main concern is the constant corrupting of the database. This has never happened before in several years, so why it should start now is a puzzler.

Anyway thanks for popping by to check

Were you always using threads since threads was created?

since perl days - or wwwthreads

For now I'd disable the option to show the number of new posts. Those are pretty intense queries, especially when you add in the all the subforums. It appears that every one of those queries are being written to your mysql_slow_query_log file, so that's not helping matters at all.

My next question is, at what version did all the problems begin?

so far so good today....

Had 1078 posts in the last 24 hours, so things are fairly busy...

Many thanks to everyone who has helped on this issue.

With any luck things stay "well"

Amen, good luck.