chestia asta am patit-o si eu ... atunci cand s-a dus fizic un hard uitate dupa baduri
On Fri, 2004-11-05 at 16:03, Cristi Banciu wrote: > Masina redhat 9 > mysql-3.23.58-1.9 > > incerc sa pornesc mysqld-ul si in loguri spune cam asa: > 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... > Cannot determine thread, fp=0x40ab079c, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x80e43dc > 0x4007bdf8 > (nil) > New value of fp=(nil) failed sanity check, terminating stack trace! > > Ce, cum ce cind de ce ? > > > --- > Detalii despre listele noastre de mail: http://www.lug.ro/ > > --- Detalii despre listele noastre de mail: http://www.lug.ro/
