Есть Postfix c хранением пользователей в MySQL. Время от времени, переодичность разная, падает MySQL. В логах постфикса в это время появляются записи

Mar 23 12:06:49 mx postfix/trivial-rewrite[17244]: warning: mysql query failed: Lost connection to MySQL server during query
Mar 23 12:06:49 mx postfix/trivial-rewrite[17244]: fatal: mysql:/usr/local/etc/postfix/mysqlmaps/alias.conf(0,100): table lookup problem
Mar 23 12:06:50 mx postfix/cleanup[17465]: warning: premature end-of-input on private/rewrite socket while reading input attribute name
Mar 23 12:06:50 mx postfix/cleanup[17465]: warning: problem talking to service rewrite: Unknown error: 0
Mar 23 12:06:50 mx postfix/smtpd[17437]: warning: premature end-of-input on private/rewrite socket while reading input attribute name
Mar 23 12:06:50 mx postfix/master[610]: warning: process /usr/local/libexec/postfix/trivial-rewrite pid 17244 exit status 1
Mar 23 12:06:53 mx postfix/cleanup[17465]: warning: 3D276A102A: virtual_alias_maps map lookup problem for postmaster@mx.domain.ru

файл alias.conf
user = postfix
password = password
hosts = 127.0.0.1
dbname = postfix
table = alias
select_field = goto
where_field = address

MySQL версии 4.1.18
mysql -u postfix -ppassword -h localhost отрабатывает нормально, т.е коннект к базе есть. Да и работает связка до наступления критической ситуации нормально.
Чем могут быть обусловлены такие падения??? Или хоть подскажите как отследить из за чего MySQL падает?

• Проблема с Postfix или MySQL ???,Skif, 11:39 , 23-Мрт-06
  • Проблема с Postfix или MySQL ???,Deus, 12:52 , 23-Мрт-06
    • Проблема с Postfix или MySQL ???,Skif, 13:02 , 23-Мрт-06

лог мускула на это время.

>лог мускула на это время.

060323 12:06:49  InnoDB: Started; log sequence number 0 44320
/usr/local/mysql/libexec/mysqld: ready for connections.
Version: '4.1.18'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
mysqld got signal 10;
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=16384
read_buffer_size=258048
max_used_connections=76
max_connections=100
threads_connected=45
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 31615 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

060323 13:09:16  mysqld restarted

>060323 12:06:49  InnoDB: Started; log sequence number 0 44320
>/usr/local/mysql/libexec/mysqld: ready for connections.
>Version: '4.1.18'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
>mysqld got signal 10;
>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=16384
>read_buffer_size=258048
>max_used_connections=76
>max_connections=100
>threads_connected=45
>It is possible that mysqld could use up to
>key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 31615 K
>bytes of memory
>Hope that's ok; if not, decrease some variables in the equation.
>
>060323 13:09:16  mysqld restarted

Ну вот вам и ответ на ваш вопрос. ковыряйте mysql