Hello.
> /usr/local/mysql/libexec/mysqld: Out of memory (Needed 32704 bytes) > /usr/local/mysql/libexec/mysqld: Can't read dir of '/var/tmp/' (Errcode: 11) > /usr/local/mysql/libexec/mysqld: Out of memory (Needed 8156 bytes) Decrease your memory related variables. You have rather old versions of MySQL, I strongly recommend you to upgrade. See this link as well: http://dev.mysql.com/doc/mysql/en/crashing.html [EMAIL PROTECTED] wrote: > Hi all > > a few days a go i have troubles with mysql, the service stops and this is on > two boxes wiht diferents OS. The first one is a FreeBSD 5.3-RELEASE on a > sparc64 the mysql Version is '4.1.5-gamma' and i got this messages in my > logs: > > > 050816 17:11:06 mysqld restarted > Fatal error 'gc cannot wait for a signal' at line 194 in file > /usr/src/lib/libc_r/uthread/uthread_gc.c (errno = 0) > mysqld got signal 6; > 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=0 > read_buffer_size=131072 > max_used_connections=0 > max_connections=100 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = > 217599 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > 050816 17:11:07 mysqld ended > > 050817 11:13:51 mysqld started > 050817 11:13:52 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 050817 11:13:52 InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 43634. > InnoDB: Doing recovery: scanned up to log sequence number 0 43634 > 050817 11:13:52 InnoDB: Flushing modified pages from the buffer pool... > 050817 11:13:52 InnoDB: Started; log sequence number 0 43634 > /usr/local/libexec/mysqld: ready for connections. > Version: '4.1.5-gamma' socket: '/tmp/mysql.sock' port: 3306 FreeBSD port: > mysql-server-4.1.5 > > > > > > The other one is a solaris 8 on a sparc64 whit mysql version 3.23.45 and i > got this error messages: > > > 050815 19:01:08 mysqld restarted > /usr/local/mysql/libexec/mysqld: ready for connections > 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 agaist 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=16773120 > record_buffer=131072 > sort_buffer=524280 > max_used_connections=7 > max_connections=500 > threads_connected=2 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 336376 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 050815 19:41:01 mysqld restarted > /usr/local/mysql/libexec/mysqld: ready for connections > 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 agaist 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=16773120 > record_buffer=131072 > sort_buffer=524280 > max_used_connections=1 > max_connections=500 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 336376 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 050815 19:41:02 mysqld restarted > /usr/local/mysql/libexec/mysqld: ready for connections > 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 agaist 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=16773120 > record_buffer=131072 > sort_buffer=524280 > max_used_connections=0 > max_connections=500 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 336376 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 050815 19:41:03 mysqld restarted > /usr/local/mysql/libexec/mysqld: Out of memory (Needed 32704 bytes) > /usr/local/mysql/libexec/mysqld: Can't read dir of '/var/tmp/' (Errcode: 11) > /usr/local/mysql/libexec/mysqld: Out of memory (Needed 8156 bytes) > 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 agaist 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=16773120 > record_buffer=131072 > sort_buffer=524280 > max_used_connections=0 > max_connections=500 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (record_buffer + sort_buffer)*max_connections = 336376 K > bytes of memory > Hope that's ok, if not, decrease some variables in the equation > > 050815 19:41:03 mysqld ended > > 050816 09:08:58 mysqld started > /usr/local/mysql/libexec/mysqld: ready for connections > 050816 09:54:51 mysqld started > /usr/local/mysql/libexec/mysqld: ready for connections > > > Does anyone knows what is the source of this error? > What should I do for fix this troubles? > > Thanks in advance > > Best regards > > Mario > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
