Bug #4110 now will not run
Submitted: 11 Jun 2004 17:28 Modified: 14 Jul 2004 16:30
Reporter: Matt Gibbs Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:Linux (slackware 9.0)
Assigned to: CPU Architecture:Any

[11 Jun 2004 17:28] Matt Gibbs
Description:
Below is stack trace. I had MSQL working. then I tried to ge mysqladmin3 to work. I updated the glibc to 3.2.X and when I went to restart I get the below. everything else seems to work?

root@gibbsest:/usr/local/mysql/data# resolve_stack_dump -s /tmp/mysqld.sym -n ../data/trace
0x8070740 handle_segfault + 420
0x8247998 pthread_sighandler + 184
0x822dd34 my_error + 356
0x822d9ce my_fopen + 286
0x8071c7f read_init_file__FPc + 23
0x80719a1 main + 2901
0x82573a4 __libc_start_main + 212
0x8048101 _start + 33

How to repeat:
buy just runing 

/usr/local/mysql# bin/mysqld_safe --user=mysql &
[1] 23782
root@gibbsest:/usr/local/mysql# Starting mysqld daemon with databases from /usr/local/mysql/data

Number of processes running now: 0
040611 03:10:23  mysqld restarted
[12 Jun 2004 7:49] Sergei Golubchik
check that errmsg.sys files correspond to the mysqld version your're actually running

(and if they don't please tell what version is mysqld and errmsg.sys - there should not be a crash nevertheless)
[14 Jun 2004 16:30] Matt Gibbs
Thank for the reply, What I actully found out was I have to upgrade my glibc library for the mysqladmin to work..When I did the binary version of mysql I had no longer worked. So what I did was go get the source code and re-complile the software using my new Glibc and whala it worked.

Matt G
[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".