rhel6: mariadb dies with "mysqld got signal 6", dbus and pam_fprintd.so involved

Solution Unverified - Updated -

Issue

The MariaDB instance stopped with this output:

150212 20:12:11 [ERROR] mysqld got signal 6 ;

From the error log file (/path1/MYSQL/path2/PRD/path3/filename.error.log)

process 41069: arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1397.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

150212 20:12:11 [ERROR] mysqld got signal 6 ;
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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.38-MariaDB-log
key_buffer_size=25165824
read_buffer_size=131072
max_used_connections=71
max_threads=2050
thread_count=36
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 50704337 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f049975d000
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 = 0x7f03c49ffe00 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0xaf02be]
sql/signal_handler.cc:153(handle_fatal_signal)[0x6da97c]
/lib64/libpthread.so.0(+0xf710)[0x7f16437e4710]
/lib64/libc.so.6(gsignal+0x35)[0x7f1642bac625]
/lib64/libc.so.6(abort+0x175)[0x7f1642bade05]
/lib64/libdbus-1.so.3[0x372d82aaf5]
/lib64/libdbus-1.so.3[0x372d8269a5]
/lib64/libdbus-1.so.3[0x372d80ddf2]
/lib64/security/pam_fprintd.so(pam_sm_authenticate+0x644)[0x7f043e56c514]
/lib64/libpam.so.0[0x3df1a02cee]
/lib64/libpam.so.0(pam_authenticate+0x40)[0x3df1a02600]
/TEST/MYSQL/xe101/TEST/xe101/lib/plugin/auth_pam.so(+0xabb)[0x7f1642978abb]
sql/sql_acl.cc:9036(do_auth_once)[0x51a42d]
sql/sql_acl.cc:9149(acl_authenticate(THD*, unsigned int, unsigned int))[0x528115]
sql/sql_connect.cc:1030(login_connection(THD*))[0x64216a]
sql/sql_connect.cc:1189(thd_prepare_connection(THD*))[0x64251f]
sql/sql_connect.cc:1257(do_handle_one_connection(THD*))[0x6427b5]
sql/sql_connect.cc:1183(handle_one_connection)[0x64293c]
perfschema/pfs.cc:1018(pfs_spawn_thread)[0x8508b8]
/lib64/libpthread.so.0(+0x79d1)[0x7f16437dc9d1]
/lib64/libc.so.6(clone+0x6d)[0x7f1642c629dd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
Connection ID (thread ID): 84060832
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off

These issues started after an update of the glibc packages.

Environment

  • Red Hat Enterprise Linux (RHEL) 6
  • MariaDB (not shipped with RHEL)
  • pam_fprintd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content