[rt-users] working RT3.8.8 since Nov-2010 now fails login with blank page

[Kevin Falcone]

On Wed, Jan 04, 2012 at 12:27:31PM +0000, o.nash at cs.ucc.ie wrote:
> Hi Kevin, yes thanks for your reply.
> The log in /var/log/mysql has:-
> 120104  8:21:24 [ERROR] /usr/sbin/mysqld: Table './rt3/sessions' is
> marked as crashed and last (automatic?) repair failed
> InnoDB: Database page corruption on disk or a failed
> InnoDB: file read of page 21225.
> InnoDB: You may have to recover from a backup.
> 120104  8:22:52  InnoDB: Page dump in ascii and hex (16384 bytes):
>  len 16384; hex f6c2475b000052e9000052eaffffffff000000006366b80f45b
> ..... cut big hex dump file.
> 
> the apache log has:-
> [Tue Jan 03 09:44:59 2012] [notice] Apache/2.2.17 (Unix)
> mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
> [Tue Jan 03 09:45:07 2012] [notice] child pid 1646 exit signal
> Segmentation fault (11)
> [Tue Jan 03 09:57:34 2012] [error] [client 143.239.74.160] Connect
> Failed Can't connect to local MySQL server through socket
> '/var/run/mysqld/
> mysqld.sock' (111)\n at /opt/rt3/bin/../lib/RT.pm line 206
> 
> Running:
> /opt/rt3/sbin# ./rt-validator --check
> it runs for several minutes and returns nothing.
> 
> The RT Db is accessible via mysql cmd line tools ok.
> But I did not try to read every table.

rt-validator doesn't check every table that RT uses.

It sounds like you had a big mysql crash and you should be using the
mysql tools to validate every table.  If only sessions is corrupt, you
can always drop and recreate it since the information in there is
temporary.

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120104/87bc00d7/attachment.sig>