Problem On Steive

[hoba2010]

hello all ihave a problem on steive server:

cpanel username: hoba

my domain: http://hoba2015.heliohost.org

my server:steive

my problem : mysql (5.1.68-cll) service fail many times a day iwant a solve here my forum is down many times a day because of this problem

[wolstech]

This is sadly normal for both servers here. I'm not sure if or when it'll ever be fixed. It's been broken for almost a year and a half.

 

See http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ (it applies to Johnny too).

[hoba2010]

but sur ihave a friend who has an account on johnny and this problem not in his website

[wolstech]

The crashes don't happen as often on Johnny. I have accounts on both servers though, and do occasionally see mysql go down. The sad part is that even though mysql is more stable on Johnny, your website is down more often because of load.

[hoba2010]

but sur the load on johnny is now 2 and the load on steive is now 19 is there any solve?

[wolstech]

As of this post, Johnny is down...again.

 

There sadly is no fix for this other than tolerating it or finding another host.

[paladox2014]

What about running the MySQL tool that fixes problems.

[Tjoene]

The problem is beyond repair. It would require a full deletion of InnoDB and a fresh install.

 

That means that all the users with an InnoDB database will lose their data. That is something a webhost just can't do to it's user.

[paladox2014]

Oh ok. but in MySQL folder there is a folder that holes all tables for all users. why not backup that folder and re install innodb just suggestions and trying to help to fix problem. http://chepri.com/mysql-innodb-corruption-and-recovery/

[wolstech]

The files in that folder are likely what is corrupt. The software itself is probably fine. It's choking on damaged tables and crashing.

 

The folder you suggest we back up is what we need to delete to fix it. Making a copy, deleting it, then putting the copy back will do nothing since the copy is of the damaged tables and is just as useless as the original.

[paladox2014]

Ok but even if the links in that folder are corrupted MySQL will still work it will just stop users from using there corrupted database.

[wolstech]

Not necessarily. It will open the databases, then try to write to them and crash doing so. The whole point is to let users keep using their databases in read-only. Removing that folder would delete the data.

[paladox2014]

Ok but what I meant is Backup folder and then after fixing MySQL re upload the folder because that folder holds all the databases nothing else but makes sure it doesent override the default database in that folder.

[wolstech]

So back up damaged data, fix the (not broken) software, then restored damaged data? That'll leave us where we are now. The databases themselves, not the software, are the problem. We do not have backups of any form, and there is no way to create one that would be useful. The server is beyond repair unless we want to permanently delete every innodb database on the server.

 

TL;DR: It can't be fixed without losing data, otherwise it'd be fixed already.

[paladox2014]

Oh ok. Then i would suggest send the users email who have the damaged database requesting that can you delete it so the server can be repaired because your database is causing the server to not work. Just suggestion and yes i do know you have a lot of users.