Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've had mysql 4.0 running for the past couple months and then all of a sudden, it's no longer running. When I try to restart it, I get the message:
Starting mysqld daemon with databases from /var/lib/mysql
031125 20:35:40 mysqld ended
My error log says:
031125 20:35:40 mysqld started
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.
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
Bogus stack limit or frame pointer, fp=0xbfffed68, stack_bottom=0x10001, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x10001 is invalid pointer
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 33 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid.
The manual page at <url to mysql crash manual removed because otherwise, I can't post> contains
information that should help you find out what is causing the crash.
031125 20:35:40 mysqld ended
I've checked the permissions of the files in /var/lib/mysql and everything looks correct. Does anyone have any idea how to fix this? If there's any other information you need, please tell me what and how to get it.
Okay, I just found out my server was upgraded to Fedora Core 1 and is probably what broke mysql. Does anyone know how to get mysql running again without losing my database? Everything in the data directory appears to still be there. Do I just need to save the data and reinstall mysql from the rpms?
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Originally posted by BaenSidhe Okay, I just found out my server was upgraded to Fedora Core 1 and is probably what broke mysql. Does anyone know how to get mysql running again without losing my database? Everything in the data directory appears to still be there. Do I just need to save the data and reinstall mysql from the rpms?