[rt-users] sessions table is lost after a system crash

[Asif Iqbal]

On Sun, Apr 12, 2009 at 6:05 PM, Joop van de Wege
<JoopvandeWege at mococo.nl>wrote:

> Asif Iqbal wrote:
>
>>    I looked at it now. So I can just delete the sessions.MYI,
>>    sessions.MYD and frm files and recreate the sessions table as in the
>>    schema? I am assuming it wont break the RT
>>
>>
>> mysqlcheck says this btw,
>>
>> [..all OK..]
>> rt3.Users                                          OK
>> rt3.sessions
>> warning  : Table is marked as crashed and last repair failed
>> warning  : 9 clients are using or haven't closed the table properly
>> warning  : Size of indexfile is: 12666880      Should be: 1024
>> error    : Found too long record at 82812800
>> error    : Corrupt
>>
> Make a backup or your RT database and remove the sessions table and
> recreate it. How you should remove the corrupt sessions table I don't know
> for sure, thats whats the backup for in case things go really wrong.
> I would try to drop the table and if that fails, remove the files from that
> table. If things go wrong, use the backup. Better, restore the backup on a
> backup machine and practice on the backup instead of the original.
>

yes drop the table and recreate based on the sessions schema worked.

thanks a lot


>
> Regards,
>
> Joop
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20090412/0a17ea14/attachment.htm>