Website crashed!!!

Something happened to website i designed. It was build on ModX. Website featured EasyPeasy gallery, news+comments.

Now it shows this:

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Can’t open file: ’modx2_site_content.MYI’ (errno: 145) »
SQL: SELECT sc.* FROM `ingus313_streetv2`.modx2_site_content sc LEFT JOIN `ingus313_streetv2`.modx2_document_groups dg ON dg.document = sc.id WHERE sc.id = ’1’ AND (sc.privateweb=0) LIMIT 1;
[Copy SQL to ClipBoard]

Parser timing
MySQL: 0.0052 s s (0 Requests)
PHP: 0.0734 s s
Total: 0.0786 s s



I can log into manager, but it does not work. i get this error message:
Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/ingus313/public_html/MyWebName/manager/frames/3.php on line 295

I cant export site, it returns:
Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/ingus313/public_html/MyWebName/manager/actions/static/export_site.static.action.php on line 94

Database Table backup does not work as well. It loads for ever. (i work on Firefox, mac os)

Are we hacked? Is there a way to restore the website (re-install the modX of something?)
I am a designer myself, just took some time to dive into ModX cms, but in general i don’t know programming. Please help.
thnx.

Hmm, it’s looking more like a corrupt database table(s) - you could try running the ’repair table’ option through phpMyAdmin.

Hello,

I have the same Website-crash:
"Can’t open file: ’modx_site_content.MYI’"

It occurs, if I want to save changes of content.
Fortunately I had a backup and could repair it - but questions stays:

Is this a problem with MODx or with the server?
How often happen this "event"?
I’m insecure ...

Server:
MODx 0.9.6
Apache 1.3
PHP 4.4.1
MySQL 3.23.58
mod_rewrite: on
friendly alias path: yes

Client:
W2K
Firefox 2 or IE6

MySQL tables experience corruption for a number of reasons (usually related to full-text or other indexes), especially when working with older versions of MySQL. You just have to be diligent with backups, try and keep your environment up-to-date, and learn how to diagnose and repair corrupted tables through a web admin tool like phpMyAdmin, the mysql client, or whatever tool you have access to with that capability.

Though it’s not extremely rare, I’ve never experienced this on any MODx installations in the 2+ years I’ve been deploying sites with it. Of course, I’ve only ever had one running on anything older than MySQL 4.1, and I made sure that client changed hosting as quickly as I could.

OK, I go to my client and recommend him to update his old MySQL-Version ...
Thx