On Wed, 12 May 2004, Stacho Pal wrote:
> On Wed, 12 May 2004, Pawe� Go�aszewski wrote:
> > On Wed, 12 May 2004, Stacho Pal wrote:
> > > Kiedy� mia�em problem z przej�ciem z mysql3 na mysql4. Winnym okaza� si�
> > > by�: nss_db-2.2-8 Na mysql3 dzia�a wszystko OK, na mysql4 nawet nie da
> > > si� zainicjowa� bazy, dostaje sig11, po wyrzuceniu nss_db wszystko wraca
> > > do normy.
> > A to niez�a ciekawostka...
>
Potwierdzam, u mnie podobne zachowanie. (z nss_db w systemie nie moge
uruchomic servera mysql) Podsylam loga.
system Ra24+general
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
read_buffer_size=131072
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 = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x848cf48
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...
frame pointer (ebp) is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x11200 is invalid pointer
thd->thread_id=138991440
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.
_______________________________________________________
z�ota zasada - kto si� nie zna, niech si� nie wypowiada
