All I had in the error log I pasted in my email. I couldnt see a core file
in any of the mysql directories. Would it plant it in the data directory by
default?
Is there anything you would like me to do? To try and gather more
information.
Adam
On 11/4/05, Jonathan Miller <jmiller@stripped> wrote:
>
> Did you get a core file, or a back trace in the MySQLD error log?
>
>
> Jonathan Miller
> Austin, Texas USA
> Senior Quality Assurance Developer
> MySQL AB www.mysql.com <http://www.mysql.com>
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ /
> / /|_/ / // /\ \/ /_/ / /__
> /_/ /_/\_, /___/\___\_\___/
> <___/ www.mysql.com <http://www.mysql.com>
>
> Jumpstart your cluster!
> http://www.mysql.com/consulting/packaged/cluster.html
>
> Get training on clusters
> http://www.mysql.com/training/courses/mysql_cluster.html
>
> All-in-one Enterprise-grade Database, Support and Services
> http://www.mysql.com/network/
>
> -> -----Original Message-----
> -> From: Adam Dixon [mailto:adamtdixon@stripped]
> -> Sent: Friday, November 04, 2005 12:09 AM
> -> To: cluster@stripped
> -> Subject: Signal 11 on API Node
> ->
> -> Were actually running one of our databases on the cluster (production)
> -> all
> -> seems to be going nicely. However, out of 24hours of operation 3 sig11
> -> crashes. the mysql node in question seems to crash with signal 11, and
> -> restart. The server has 4gb of memory, so I trimmed my buffer sizes to
> -> all
> -> default levels etc. But yet it still crashes. I dont know what could be
> -> causing it, I really cant reproduce the problem.
> ->
> -> 95% of queries come from php/apache. Others from perl scripts about the
> -> place from cron.
> ->
> -> I did come up with this problem in testing but again failed to
> reproduce
> -> the
> -> problem. Can anyone point me in the right direction as to what I can do
> -> to
> -> diagnose this further?
> ->
> -> Mysql 5.0.15, 2replica, 8dn (of 6gb ram each), 2sql (of 4gb ram each).
> -> mysql-max-5.0.15-linux-x86_64-glibc23.tar.gz
> -> Linux server3 2.6.9-5.ELsmp #1 SMP Tue May 3 07:25:41 CDT 2005 x86_64
> -> x86_64
> -> x86_64 GNU/Linux
> -> All systems are dual 2.8ghz xeons running RHEL4.
> ->
> ->
> -> -----------
> -> 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=57
> -> max_connections=200
> -> threads_connected=27
> -> It is possible that mysqld could use up to
> -> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
> =
> -> 26248190 K
> -> bytes of memory
> -> Hope that's ok; if not, decrease some variables in the equation.
> ->
> ->
> -> Number of processes running now: 0
> -> 051104 14:30:10 mysqld restarted
> -> 051104 14:30:10 [Note] /usr/local/mysql/bin/mysqld: ready for
> -> connections.
> -> Version: '5.0.15-max-log' socket: '/tmp/mysql.sock' port: 3306 MySQL
> -> Community Edition - Experimental (GPL)
> -> -------------
> ->
> -> Anyone help?
>
>
