SQL problems

Hi Guys,

While trying to track down why emails were not triggering ticket
creation in rt3.0.9 on Solaris 8, I used mysqladmin 4.0.18-max to
shutdown the database.

on restart, the server exited. Examining the logs, their was a table
inconsistency logged against the RT database. I then restored it from
the previous night backup and tried again.

Now it starts to come up, then exits with signal 11, usually at 99%
040311 00:00:44 mysqld started
040311 0:00:45 InnoDB: Starting an apply batch of log records to the
database…
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88
89 90 91 92 93 94 95 96 97 98 99 mysqld got signal 11;
This could be because you hit a bug. It is also possible that this
binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.

key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=0
max_connections=200
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 193534 K

Anyone any ideas?

Thanks

Rik
Rick Ellis Richard.Ellis@Sun.COM

Have you tried with an older backup?-----Original Message-----
From: Rick Ellis [mailto:Richard.Ellis@Sun.COM]
Sent: Jueves, 11 de Marzo de 2004 05:18 a.m.
To: rt list
Subject: [rt-users] SQL problems

Hi Guys,

While trying to track down why emails were not triggering ticket
creation in rt3.0.9 on Solaris 8, I used mysqladmin 4.0.18-max to
shutdown the database.

on restart, the server exited. Examining the logs, their was a table
inconsistency logged against the RT database. I then restored it from
the previous night backup and tried again.

Now it starts to come up, then exits with signal 11, usually at 99%
040311 00:00:44 mysqld started
040311 0:00:45 InnoDB: Starting an apply batch of log records to the
database…
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88
89 90 91 92 93 94 95 96 97 98 99 mysqld got signal 11;
This could be because you hit a bug. It is also possible that this
binary
or one of the libraries it was linked against is corrupt, improperly
built,
or misconfigured. This error can also be caused by malfunctioning
hardware.
We will try our best to scrape up some info that will hopefully help
diagnose
the problem, but since we have already crashed, something is definitely
wrong
and this may fail.

key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=0
max_connections=200
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 193534 K

Anyone any ideas?

Thanks

Rik
Rick Ellis Richard.Ellis@Sun.COM

rt-users mailing list
rt-users@lists.bestpractical.com
http://lists.bestpractical.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Rick Ellis wrote:

Hi Guys,

While trying to track down why emails were not triggering ticket
creation in rt3.0.9 on Solaris 8, I used mysqladmin 4.0.18-max to
shutdown the database.

on restart, the server exited. Examining the logs, their was a table
inconsistency logged against the RT database. I then restored it from
the previous night backup and tried again.

I had an issue similar to that two weeks ago. I seem to recall having to
delete the following files from /usr/local/mysql/data/:

ib_arch_log_0000000000
ibdata1
ib_logfile0
ib_logfile1

I moved them first, then restarted and they were recreated. Might be
related to your problem?

Tom