Mysql keeps going down

[richclever]

My mysql server keeps going down, and I can't work out why.

I enclose the latest part of my error log that deals with the latest crash.

If anyone has any ideas please let me know. I must get it working properly.

Thanks

Richard

Version: '4.0.20-standard' socket: '/tmp/mysql.sock' port: 3306
050112 9:00:16 Aborted connection 49 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
050112 9:00:16 Aborted connection 50 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
050112 9:51:15 Aborted connection 3 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
050112 9:51:17 Aborted connection 4 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
050112 9:51:19 Aborted connection 5 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
050112 9:54:28 Aborted connection 51 to db: 'cybermed' user: 'cybermed' host: `localhost' (Got an error writing communication packets)
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=8388600
read_buffer_size=131072
max_used_connections=12
max_connections=100
threads_connected=8
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x87c4568
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfe1ac88, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8070740
0x8247998
0x8273ecf
0x82079ad
0x821289e
0x82129c3
0x82129c3
0x82129c3
0x82129c3
0x82126b2
0x821376f
0x82317d9
0x82317e9
0x82317ad
0x82317ad
0x82317e9
0x82317ad
0x82317ad
0x82317ad
0x8231703
0x8231788
0x82318b0
0x8213660
0x8212609
0x821225f
0x80c5abd
0x80a4095
0x80d75e3
0x80d6e8e
0x807d3c0
0x807ebda
0x807a3d3
0x8079e2d
0x8079669
0x824514c
0x827b17a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read

http://www.mysql.com/doc/en/Using_stack_trace.html

and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x87e0f48 = LOAD DATA LOCAL INFILE '/usr/local/psa/home/vhosts/cybermed.it/httpdocs/data/search.idx' INTO TABLE searchidx
thd->thread_id=56
The manual page at

http://www.mysql.com/doc/en/Crashing.html

contains
information that should help you find out what is causing the crash.
050112 09:54:44 mysqld ended

050112 11:12:23 mysqld started
050112 11:12:23 Warning: Asked for 196608 thread stack, but got 126976
050112 11:12:23 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43912
InnoDB: Doing recovery: scanned up to log sequence number 0 43912
050112 11:12:23 InnoDB: Flushing modified pages from the buffer pool...
050112 11:12:23 InnoDB: Started
050112 11:12:23 /usr/local/mysql/bin/mysqld: Can't create/write to file '/usr/home/mysql/data/barnes.pid' (Errcode: 2)
/usr/local/mysql/bin/mysqld: ready for connections.
Version: '4.0.20-standard' socket: '/tmp/mysql.sock' port: 3306