Mysql 4.0 No Longer Starting on Fedora Core 1
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:
shell# /usr/bin/mysqld_safe 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. key_buffer_size=8388600 record_buffer=131072 sort_buffer=2097144 max_used_connections=0 max_connections=100 threads_connected=0 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 terribly wrong... 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 thd->thread_id=33 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. Thanks. BaenSidhe |
Did you try starting Mysql As root?
|
Yes, I was running as root when I ran mysql.
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?
|
Quote:
|
Well, I went and uninstalled mysql from my server and tried to reinstall it. Still no go. I'm getting the same error when the daemon is started.
The rpm I used is at http://rpmfind.net/linux/RPM/mysql/MySQL-4.0/MySQL-4.0.0-1.i386.html Has anyone been able to install and run mysql on Fedora and if so, how? (Explicit instructions please. :newbie: ) |
try this:
edit ur /etc/my.cnf (or whatever u configured it as) and change the thread stack under [mysqld] to a higher value. eg... set-variable = thread_stack=1M |
have you ever resolve this issue?
I am currently having the same problem and having a hard time trying to find the answer. |
]#apt-get install mysql (you can use php-mysql for the mysql and php package without any user configuration)
|
All times are GMT -5. The time now is 06:38 PM. |