Bug #3135 Segfault when writing to slowlog
Submitted: 10 Mar 2004 16:02 Modified: 25 Apr 2004 10:13
Reporter: Steven Roussey Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:4.1.2 (bk from 9 Mar 04) OS:Linux (RHEL 3)
Assigned to: CPU Architecture:Any

[10 Mar 2004 16:02] Steven Roussey
In this version of MySQL, I have had several problems with the various log files I have set up. First of all, I expect the files to appear in the datadir, which they do, but occationally sometimes they appear in /usr/local/mysql/. It looks like it is writing in both sometimes, but I cannot confirm. Using a full path for the log files (like the slowlog) helps. It also has eliminated this crash:

040310  1:17:28  Error writing file 'slow-queries.log' (errno: 1)
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 843360 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=0x418e11a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x814e4f3 handle_segfault + 455
0x400437ce _end + 934889310
0x8345296 my_vsnprintf + 204
0x81b0af4 sql_print_error(char const*, ...) + 144
0x8160401 handle_one_connection + 919
0x4003e881 _end + 934869009
0x420e40c7 _end + 969101399
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil)  is invalid pointer

How to repeat:
I am travelling around between sites and can't repeat on command, but can repeat eventually. This crash usually happens after doing a ALTER TABLE USE_FRM to update a table with full-text indicies (which takes a lot longer than using myisamchk for some reason).
[25 Mar 2004 10:13] MySQL Verification Team
I have tried to repeat this several times and I failed.

We need exact procedure how to repeat this crash, as we would like to fix it.
[14 Feb 2005 22:54] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[18 Aug 2021 17:40] Rebecca Willey
13:36:41	SET SQL_MODE=@OLD_SQL_MODE	0 row(s) affected, 1 warning(s): 3135 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVIS

Attachment: sakila-schema.sql (application/octet-stream, text), 23.69 KiB.