mysqld 4.0.8 crashes

Hi,
I've serious problem with mysqld
(mysql-standard-4.0.8-gamma-pc-linux-i686) dying on linux i686 with kernel
2.4.20, SMP kernel with HIGHMEM:

0x806f3bb handle_segfault + 447
0x8269928 pthread_sighandler + 184
0x807724c check_connections__FP3THD + 200
0x8077665 handle_one_connection + 337
0x82670dc pthread_start_thread + 220
0x829c67a thread_start + 4

How-To-Repeat:
We have found the clients crashing this 4.0.8 binary. It's linux with
mysql-3.23.49 mysql binary client. When he connect using the mysql binary
directly to the server, it crashes.

But, this guy runs some proxy service on the mysql server itself. When
he uses -P option to connect to that proxy port instead, he can work. He
says, the only difference is IP in the packet.

We have found that my BK binaries from Nov 25 (4.0.6) work fine even
when he connects directly. Those binaries exhibit the error:

021018 13:19:33 mysqld started
crashing: /proc/613/exe: Permission denied
BFD load failed..

... which I've reported earlier. So, this threads problem got fixed in
between Nov 25 and 4.0.8.


Back to the current bug:

netopyr:~/Program/perl/Celeg>/usr/bin/mysql -u xx -h xx -P3307
ERROR 2013: Lost connection to MySQL server during qu[...]


thd=0x84a94f8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbff5f608, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8071e4a
0x8293d68
0x807aa2c
0x807af13
0x829151c
0x82c6c2a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instr uctions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid.

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash.

Program received signal SIG33, Real-time event 33.
0x082c5dee in __select () at __select:-1
-1 __select: No such file or directory.
in __select
(gdb) bt
#0 0x082c5dee in __select () at __select:-1
#1 0x084a9e90 in ?? ()
#2 0x080731bd in main (argc=33, argv=0x8471ca8) at mysqld.cc:2229
#3 0x082a3774 in __libc_start_main (main=0x8072708

Re: mysqld 4.0.8 crashes

=?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> Hi,
> I've serious problem with mysqld
> (mysql-standard-4.0.8-gamma-pc-linux-i686) dying on linux i686 with kernel
> 2.4.20, SMP kernel with HIGHMEM:
>
> 0x806f3bb handle_segfault + 447
> 0x8269928 pthread_sighandler + 184
> 0x807724c check_connections__FP3THD + 200
> 0x8077665 handle_one_connection + 337
> 0x82670dc pthread_start_thread + 220
> 0x829c67a thread_start + 4
>
> How-To-Repeat:
> We have found the clients crashing this 4.0.8 binary. It's linux with
> mysql-3.23.49 mysql binary client. When he connect using the mysql binary
> directly to the server, it crashes.
>
> But, this guy runs some proxy service on the mysql server itself. When
> he uses -P option to connect to that proxy port instead, he can work. He
> says, the only difference is IP in the packet.
>

Hi!

This looks like some report we already received.

Were you working with very large queries or BLOB's ??

If not, can you try our debug 4.0.8 binary, available from 4.0
download page ??

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com

Join MySQL Users Conference and Expo:
http://www.mysql.com/events/uc2003/


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13499@lists.mysql.com
To unsubscribe, e-mail

Re: mysqld 4.0.8 crashes

On Thu, 16 Jan 2003, Sinisa Milivojevic wrote:

Hi,


> =?iso-8859-2?Q?Martin_MOKREJ=A9?= writes:
> > Hi,
> > I've serious problem with mysqld
> > (mysql-standard-4.0.8-gamma-pc-linux-i686) dying on linux i686 with kernel
> > 2.4.20, SMP kernel with HIGHMEM:
> >
> > 0x806f3bb handle_segfault + 447
> > 0x8269928 pthread_sighandler + 184
> > 0x807724c check_connections__FP3THD + 200
> > 0x8077665 handle_one_connection + 337
> > 0x82670dc pthread_start_thread + 220
> > 0x829c67a thread_start + 4
> >
> > How-To-Repeat:

> This looks like some report we already received.
>
> Were you working with very large queries or BLOB's ??

No, just connecting.

> If not, can you try our debug 4.0.8 binary, available from 4.0
> download page ??

I've tried that already and the debugging output was at the end of my
mail!

As Peter Zaitser suggested, I've tried 4.0.9 binaries and there the
problem is fixed. So yo know the cause?

--
Martin Mokrejs ,
PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
MIPS / Institute for Bioinformatics
GSF - National Research Center for Environment and Health
Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
tel.: +49-89-3187 3683 , fax: +49-89-3187 3585

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13508@lists.mysql.com
To unsubscribe, e-mail

Re: mysqld 4.0.8 crashes

=3D?iso-8859-2?Q?Martin_MOKREJ=3DA9?=3D writes:
> On Thu, 16 Jan 2003, Sinisa Milivojevic wrote:
>=20
> Hi,
>=20
> I've tried that already and the debugging output was at the end of my=

> mail!
>=20
> As Peter Zaitser suggested, I've tried 4.0.9 binaries and there the
> problem is fixed. So yo know the cause?
>=20
> --=20
> Martin Mokrejs ,
> PGP5.0i key is at http://www.natur.cuni.cz/~mmokrejs
> MIPS / Institute for Bioinformatics
> GSF - National Research Center for Environment and Health
> Ingolstaedter Landstrasse 1, D-85764 Neuherberg, Germany
> tel.: +49-89-3187 3683 , fax:=A0+49-89-3187 3585
=20

Ohh, that is why stack trace looked familiar to me.

Yes, it is fixed in 4.0.9. It was this bug fix:

* A security patch in 4.0.8 causes the mysqld server to die if the
remote hostname can't be resolved. This is now fixed.


Good that we do not have to investigate this further.=20

--=20
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic >
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ www.mysql.com

Join MySQL Users Conference and Expo:
http://www.mysql.com/events/uc2003/


------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread13510@lists.mysql.com
To unsubscribe, e-mail