Huge Problem

[psychoforum]

We don't know what is causing this, but our server is running fine. We're on Venturesonline and have our own dedicated server for $220 a month There are several html files on the site that load up with no problems. However the vbulletin is not working when we try to access it we get this message:

Parse error: parse error in /home/tforum/public_html/index.php on line 40

When we reboot MySQL it seems to fix the problem temporarily, but soon this error message comes back. Any ideas?

P

Our site is at: www.ticklingforum.com

We usually have about 100 to 120 people on there at once.

[eva2000]

you have a corrupted Session table in your database

if you view the source code of your main forum page's error message it shows

Database error in vBulletin: Invalid SQL: SELECT sessionhash,userid,host,useragent,styleid FROM session WHERE userid=0 AND host='61.9.208.141' AND useragent='Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; Dig'
mysql error: Can't open file: 'session.MYD'. (errno: 145)
mysql error number: 1016
Date: Thursday 29th of March 2001 05:52:41 PM
Script: /index.php
Referer: http://www.ticklingforum.com

[eva2000]

you need to run mysql repair command myisamchk on yoru forum database [more info - http://vbulletin.com/forum/showthread.php?threadid=3944]
to fix it

first backup your forum - you can use Chris' script here - http://vbulletin.com/forum/showthread.php?s=&threadid=4256

then

1. with you're forum closed, telnet into your server, then switch to root by issuing command

su -

and

shut down mysql

/etc/rc.d/init.d/mysql stop

then run myisamchk for MySQL 3.23.x

i run this for check all tables in the database named forum

/usr/bin/myisamchk /usr/mysql/forum/*.MYI

to repair all tables in database named forum i run

/usr/bin/myisamchk -r /usr/mysql/forum/*.MYI

after repaired i rerun the check

/usr/bin/myisamchk /usr/mysql/forum/*.MYI

then restart mysql

/etc/rc.d/init.d/mysql start

[psychoforum]

Okay thanks for the help. Do you know what would have caused this? It was working fine for about two weeks and then all of a sudden when we opened the site to the public this error started showing up.

Thanks
S

[eva2000]

could be anything happens out of the blue sometimes... straight from mysql.com docs - http://www.mysql.com/doc/C/r/Crash_recovery.html


The file format that MySQL uses to store data has been extensively tested, but there are always external circumstances that may cause database tables to become corrupted:

The mysqld process being killed in the middle of a write.
Unexpected shutdown of the computer (for example, if the computer is turned off).
A hardware error

i also found if you reboot your server while mysql is running corruptions can occur - whenever i reboot my server i always do the above check on all my mysql databases