Typically, processes which die with either a signal 10 or 11 are due to
hardware
problems, such as bad memory or an overheating CPU.
You might consider trying a memory tester or simply do a 'make world' in
/usr/src
(to heavily tax the CPU and memory).
-Tilghman
--
"There cannot be a crisis today. My schedule is already full."
--Henry Kissinger
-Original Message-
From: Pawel Krawczyk [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 23, 2001 06:47
Every several hours mysqld crashes and it seems to be correlated with
heavy load. For example I can repeat the crashes with mysqldump.
MySQL is 3.23.31 started with the following options:
-O key_buffer=20M \
-O table_cache=512 \
-O sort_buffer=8M \
-O max_connections=600 \
-O record_buffer=1024k \
-O query_buffer_size==1024k \
-O max_tmp_tables=256
Host system is FreeBSD 4.2-STABLE on a SMP machine (Intel
ISP-2051 platform)
with DPT hardware RAID-5 disk array.
The process crashes with the following message in dmesg:
Jan 23 13:45:32 db /kernel: pid 8528 (mysqld), uid 1002:
exited on signal 10
(signal 10 is SIGBUS)
Can anyone suggest what could be the reason? Thanks in advance.
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
