Problem-with-start

Problem-with-start

am 18.07.2003 15:43:51 von Ulises Coniglio

Hi, I have a problem with MySQL. This problem was begin when I restart the
MySQL. I have MySQL 4.0 installed on Linux Mandrake 9.1.
The logs is repoted:

------------------------------------------------------------ ----------------
030714 15:58:32 mysqld started
030714 15:58:32 bdb: Recovery function for LSN 1 286647 failed
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=16777216
read_buffer_size=131072
sort_buffer_size=1768645487
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 =
782005 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x84661a8
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=0xbffff278, stack_bottom=0x6d3d656c,
thread_stack=196608, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x62616972 is invalid pointer
thd->thread_id=12341

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 12341 did to cause the crash. In some cases of
really
bad corruption, the values shown above may be invalid.

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash.
030714 15:58:32 mysqld ended
------------------------------------------------------------ ----------------


I was desinstalled and installed MySQL but not solution this problem.
Can you help me?

Ulises



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Problem-with-start

am 18.07.2003 20:51:00 von Sinisa Milivojevic

Ulises Coniglio writes:
> Hi, I have a problem with MySQL. This problem was begin when I restart the
> MySQL. I have MySQL 4.0 installed on Linux Mandrake 9.1.
> The logs is repoted:
>
> I was desinstalled and installed MySQL but not solution this problem.
> Can you help me?
>
> Ulises
>
>

HI!

We can not reproduce a behaviour you are describing.

Which binary are you using ???

Also please follow all our installation instructions from our manual.

--

Regards,

--
For technical support contracts, go to https://order.mysql.com/?ref=msmi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB
/_/ /_/\_, /___/\___\_\___/ Fulltime Developer and Support Coordinator
<___/ www.mysql.com Larnaca, Cyprus


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Problem-with-start

am 18.07.2003 23:36:39 von Sergei Golubchik

Hi!

On Jul 18, Ulises Coniglio wrote:
> Hi, I have a problem with MySQL. This problem was begin when I restart the
> MySQL. I have MySQL 4.0 installed on Linux Mandrake 9.1.
> The logs is repoted:
>
> ------------------------------------------------------------ ----------------
> 030714 15:58:32 mysqld started
> 030714 15:58:32 bdb: Recovery function for LSN 1 286647 failed
> mysqld got signal 11;

It looks like you hit a bug in bdb, and it crashes trying to repair
broken table.

> ------------------------------------------------------------ ----------------
>
> I was desinstalled and installed MySQL but not solution this problem.
> Can you help me?
>
> Ulises

Try to move *.db files out from mysql datadir, if mysqld will work then,
it's a bug in bdb code, and we will need broken bdb table in question.

Regards,
Sergei

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org