On Tuesday 22 May 2001 21:37, Stephan Skusa wrote:
> Another signal 11 dump ... cutting down sort_buffer to 4194296 Bytes
> seems not to be the solution for the signal 11 at 0 o'clock ... stated
> some weeks ago!
>
>
>
> mysqld got signal 11;
> The manual sect
Stephan Skusa writes:
>
> What?? ... no I haven't ...
>
> It's slightly a problem doing exact logs ... cause this Database-Server
> crashes every 2-4 Days ... and does about 600,000 Queries an hour ...
>
> I generated a mysqld.sym ... if anybody needs this ... I'll send it ...
> I think this Ma
cept this large mailings ... ;o)
> -Ursprungliche Nachricht-
> Von: Colin Faber [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 23. Mai 2001 05:43
> An: Stephan Skusa
> Cc: [MYSQL]
> Betreff: Re: Another signal 11 dump ...
>
>
> have you tried trussing the mysqld
have you tried trussing the mysqld process and then moving your system
time up to the crash point?
see what its calling right before it dies?
Stephan Skusa wrote:
>
> Another signal 11 dump ... cutting down sort_buffer to 4194296 Bytes
> seems not to be the solution for the signa
Another signal 11 dump ... cutting down sort_buffer to 4194296 Bytes
seems not to be the solution for the signal 11 at 0 o'clock ... stated
some weeks ago!
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core fi
