Further to my last email on this, The query "FROM Tyres a1, Tyres a2, Cars i
" was a perl script being run from two seperate hosts, at exactly the same
time, the only thing I can put it down to is that for some reason it didnt
like the running of the query at the exactly the same time. Adjusting one of
the servers 1 minute either way doesnt seemed to of stopped the server from
crashing.
It crashed a couple of times on the weekend, and again the same query was
run just before crashing. Is there anything I can try or check as to why
this would be happening. Could it be something to do with the client version
connecting to the 5.0 servers?
During the times that it did crash I was unable to obtain a core file as it
wouldnt write one, even with ulimit -c unlimited set.
I am hesitant to put our second (more busy) database on cluster until I can
come up with a solution to this.
Adam
On 11/8/05, Adam Dixon <adamtdixon@stripped> wrote:
>
> Ok, ulimit had core size set to 0, so i set this to unlimited;
> # ulimit -c
> unlimited
>
> And started the mysql server again and let it do its stuff. And again it
> crashed over night, same deal, this was printed to my tty (along with the
> normal looking sig 11 entry in the err file)
> # ./bin/mysqld_safe: line 381: 10993 Segmentation fault nohup
> /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql
> --datadir=/usr/local/mysql/data --user=mysql
> --pid-file=/usr/local/mysql/data/sql1.pid --skip-locking --core-file --log
> >>/usr/local/mysql/data/sql1.err 2>&1
>
> Number of processes running now: 0
> 051107 19:15:09 mysqld restarted
>
> It did say that it wrote a core file, but again no core file can be found.
> No idea why. I do have the queries which ran just before the crash.
> The query involves three tables, two of which are the same table.
> eg; FROM Tyres a1, Tyres a2, Cars i
>
> Running the same query on mysql cmdline it works fine...
>
> What can be done to get this checked out further? as it has a massive
> impact on the stability of the mysql servers.
>
>
> Adam
>
> On 11/7/05, pekka@stripped < pekka@stripped> wrote:
> >
> > > Writing a core file
> >
> > Before starting mysqld, did you check "ulimit -a" ?
> >
> > > [root@sql1 data]# ./bin/mysqld_safe: line 381: 3237 Segmentation fault
> > nohup
> > > /usr/local/mysql/libexec/mysqld --basedir=/usr/local/mysql
> > > --datadir=/usr/local/mysql/data --user=mysql
> > > --pid-file=/usr/local/mysql/data/sql1.pid --skip-locking --core-file
> > > >>/usr/local/mysql/data/sql1.err 2>&1
> >
> > With these options core should be in /usr/local/mysql/data/.
> >
> > --
> > Pekka Nousiainen, Software Engineer
> > MySQL AB, www.mysql.com <http://www.mysql.com>
> > pekka@stripped +46 (0) 73 068 4978
> >
>
>
