* [gentoo-user] mysql error
@ 2007-02-08 10:46 Arnau Bria
2007-02-08 14:34 ` Arnau Bria
0 siblings, 1 reply; 2+ messages in thread
From: Arnau Bria @ 2007-02-08 10:46 UTC (permalink / raw
To: gentoo-user
Hi,
After a power cut my server did not start again. I had to boot with a
livecd, do a fsck in my / partion (which removed some orphan inodes)
and reinstall grub in my MBR.
After all, I'm able to boot, and all my services are running
again, all except mysql.
This is what I see in my mysqld.err log:
070208 11:26:17 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=afrodita-bin' to avoid this problem.
mysqld got signal 4;
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.
****I think I can ignore this********
key_buffer_size=0
read_buffer_size=258048
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 76399 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xb690808d, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0xb690808d, stack_bottom=0xbfcb0000, thread_stack=196608, aborting backtrace.
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
*****WTH!!!!******
I have done this:
myisamchk --silent --force */*.MYI
from http://dev.mysql.com/doc/refman/5.0/en/crashing.html and I think
tables are fine (I have copied them into a new mysql and I can browse
content)
I have recompiled mysql, but I think this is not enough...
What else may I do to recover y mysql? Do I have to recompile all its
dependencies? How? Maybe a emerge --emptytree world/system?
TIA,
Arnau
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [gentoo-user] mysql error
2007-02-08 10:46 [gentoo-user] mysql error Arnau Bria
@ 2007-02-08 14:34 ` Arnau Bria
0 siblings, 0 replies; 2+ messages in thread
From: Arnau Bria @ 2007-02-08 14:34 UTC (permalink / raw
To: gentoo-user
On Thu, 8 Feb 2007 11:46:39 +0100
Arnau Bria wrote:
> Hi,
[...]
> This is what I see in my mysqld.err log:
>
> 070208 11:26:17 [Warning] No argument was provided to --log-bin, and
> --log-bin-index was not used; so replication may break when this
> MySQL server acts as a master and has his hostname changed!! Please
> use '--log-bin=afrodita-bin' to avoid this problem. mysqld got signal
> 4; 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.
>
> ****I think I can ignore this********
>
> key_buffer_size=0
> read_buffer_size=258048
> max_used_connections=0
> max_connections=100
> threads_connected=0
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size +
> sort_buffer_size)*max_connections = 76399 K bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> thd=(nil)
> 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=0xb690808d, backtrace may not be correct.
> Bogus stack limit or frame pointer, fp=0xb690808d,
> stack_bottom=0xbfcb0000, thread_stack=196608, aborting backtrace. The
> manual page at http://www.mysql.com/doc/en/Crashing.html contains
> information that should help you find out what is causing the crash.
>
> *****WTH!!!!******
I had to remove all bin files from /var/lib/mysql
After that, all works fine!
cheers!
--
Arnau Bria
http://blog.emergetux.net
Wiggum: Dispara a las ruedas Lou.
Lou: eee, es un tanque jefe.
Wiggum: Me tienes hartito con todas tus excusas.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-02-08 14:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-02-08 10:46 [gentoo-user] mysql error Arnau Bria
2007-02-08 14:34 ` Arnau Bria
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox