Re: Mysqld 3.23.56 crash on concurrent ALTER TABLE and FLUSH TABLE

Sergei,

On Wed, Jan 14, 2004 at 05:39:09PM +0100, Sergei Golubchik wrote:
> I failed to repeat this. I had two processes constantly doing
> FLUSH+ALTER on two diffeent merge tables. Nothing crashed.
>  

Thank you for trying. After Sinisa's response I was about to try the
same myself. I'll probably do this anyway to be sure with my setup, but
are hesitant to crash a running operational MySQL daemon. I'll probably
run a different instance for this with another datadir.


> Try to generate a core dump. There's command line switch --core-file.
> And pay attention to limits. Check the manual - there is a chapter there
> about coredumps.
>

Finally think I found it.

I checked everything before, including the credentials and limits of the
running mysqld process. But even though all s/r/euid are mysql, the fact
that it at one time called setuid, takes away its permission to dump
core files (on Solaris at least). This is described in the manual, but I
understood it as refering only to a process that has different e/r/suid's.

Now I start it with 'su - mysql safe_mysqld' and hope to get a core file
next time.


Thanks again for your help.



Regards,

Fred.

-- 
Fred van Engen                              XB Networks B.V.
email: [email protected]                Televisieweg 2
tel: +31 36 5462400                         1322 AC  Almere
fax: +31 36 5462424                         The Netherlands

-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]