Hallo,
I have a problem with general log configuration; after setting my.cnf file in this mode:
general_log=1
general_log_file=/var/lib/mysql/mysql_access.fifo
where mysql_access.fifo is a fifo file.
This file is read and filtered (Connect|Quit), then redirected to logger for having an access log file.
No problems with mysql 5.1 but with 5.5.37 version when i stopped the service this crashing and restarting with the follow message:
10:50:44 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338508 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
stack_bottom = 0 thread_stack 0x40000
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x7f79cf65194e]
/usr/libexec/mysqld(handle_fatal_signal+0x493)[0x7f79cf53a6a3]
/lib64/libpthread.so.0(+0x327de0f710)[0x7f79ced28710]
/usr/libexec/mysqld(_ZN9MYSQL_LOG5closeEj+0x1f6)[0x7f79cf5c36c6]
/usr/libexec/mysqld(_ZN25Log_to_file_event_handler7cleanupEv+0xd)[0x7f79cf5c3c5d]
/usr/libexec/mysqld(+0x2857b9)[0x7f79cf3dd7b9]
/usr/libexec/mysqld(_Z10unireg_endv+0xe)[0x7f79cf3ddb0e]
/usr/libexec/mysqld(+0x2875d9)[0x7f79cf3df5d9]
/usr/libexec/mysqld(kill_server_thread+0xe)[0x7f79cf3df69e]
/lib64/libpthread.so.0(+0x327de079d1)[0x7f79ced209d1]
/lib64/libc.so.6(clone+0x6d)[0x7f79cd227b5d]
The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
140918 12:50:44 mysqld_safe Number of processes running now: 0
140918 12:50:44 mysqld_safe mysqld restarted
best regards
Federico