auth_pam plugin prevents startup

Bug #1245523 reported by Ammon Sutherland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

RHEL 5.9, 64bit.
Percona Server 5.5.31-rel30.3.520.rhel5 OR 5.5.33-rel31.1.566.rhel5

After installing the auth_pam plugin ('INSTALL PLUGIN auth_pam SONAME 'auth_pam.so';) in the server (which works) if I try to restart mysql it is unable to start and I get the following errors in the logs for both 5.5.31 and 5.5.33 builds

Oct 28 09:37:26 mysqld: You may download the Percona Server operations manual by visiting
Oct 28 09:37:26 mysqld: http://www.percona.com/software/percona-server/. You may find information
Oct 28 09:37:26 mysqld: in the manual which will help you identify the cause of the crash.
Oct 28 09:37:26 mysqld_safe: mysqld from pid file /var/lib/mysql/.pid ended
Oct 28 09:45:35 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Oct 28 09:45:35 mysqld: 131028 9:45:35 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
Oct 28 09:45:35 mysqld: 14:45:35 UTC - mysqld got signal 11 ;
Oct 28 09:45:35 mysqld: This could be because you hit a bug. It is also possible that this binary
Oct 28 09:45:35 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Oct 28 09:45:35 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 28 09:45:35 mysqld: We will try our best to scrape up some info that will hopefully help
Oct 28 09:45:35 mysqld: diagnose the problem, but since we have already crashed,
Oct 28 09:45:35 mysqld: something is definitely wrong and this may fail.
Oct 28 09:45:35 mysqld: Please help us make Percona Server better by reporting any
Oct 28 09:45:35 mysqld: bugs at http://bugs.percona.com/
Oct 28 09:45:35 mysqld:
Oct 28 09:45:35 mysqld: key_buffer_size=8388608
Oct 28 09:45:35 mysqld: read_buffer_size=262144
Oct 28 09:45:35 mysqld: max_used_connections=0
Oct 28 09:45:35 mysqld: max_threads=1502
Oct 28 09:45:35 mysqld: thread_count=0
Oct 28 09:45:35 mysqld: connection_count=0
Oct 28 09:45:35 mysqld: It is possible that mysqld could use up to
Oct 28 09:45:35 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1949244 K bytes of memory
Oct 28 09:45:35 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Oct 28 09:45:35 mysqld:
Oct 28 09:45:35 mysqld: Thread pointer: 0x7fff6df2f910
Oct 28 09:45:35 mysqld: Attempting backtrace. You can use the following information to find out
Oct 28 09:45:35 mysqld: where mysqld died. If you see no messages after this, something went
Oct 28 09:45:35 mysqld: terribly wrong...
Oct 28 09:45:35 mysqld: stack_bottom = 7fff6df32a60 thread_stack 0x40000
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7b81e5]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x692c94]
Oct 28 09:45:35 mysqld: /lib64/libpthread.so.0[0x3212c0eca0]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(my_hash_insert+0x331)[0x79fad1]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_ZN7handler25update_global_table_statsEv+0x285)[0x69a145]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_Z18close_thread_tableP3THDPP5TABLE+0xb9)[0x5581b9]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_Z19close_thread_tablesP3THD+0x18b)[0x55879b]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_Z18close_mysql_tablesP3THD+0x11)[0x558821]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld[0x59c51d]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x998)[0x59f658]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld[0x51b62b]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x46d)[0x51f17d]
Oct 28 09:45:35 mysqld: /lib64/libc.so.6(__libc_start_main+0xf4)[0x321241d9c4]
Oct 28 09:45:35 mysqld: /usr/sbin/mysqld[0x514239]
Oct 28 09:45:35 mysqld:
Oct 28 09:45:35 mysqld: Trying to get some variables.
Oct 28 09:45:35 mysqld: Some pointers may be invalid and cause the dump to abort.
Oct 28 09:45:35 mysqld: Query (0): is an invalid pointer
Oct 28 09:45:35 mysqld: Connection ID (thread ID): 0
Oct 28 09:45:35 mysqld: Status: NOT_KILLED

my.cnf file as follows:

[mysqld]
federated
max_allowed_packet = 128M
table_cache = 10000
sort_buffer_size = 1M
read_buffer_size = 256k
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 512M
thread_cache_size = 8
query_cache_size = 256M
thread_concurrency = 4
local-infile=1
join_buffer_size=256k
skip-slave-start
long_query_time=1
tmp_table_size=32m
max_heap_table_size=32m
max_connections=1500
read-only
tmpdir=/tmp/mysql_tmp
skip-name-resolve
log-bin=/var/lib/mysql_logs/mysql-bin
binlog-format=MIXED
expire_logs_days=8
log-slave-updates=1
server-id = 17521
slave_skip_errors=1062
slave_compressed_protocol=1
innodb_buffer_pool_size = 2G
innodb_log_buffer_size = 4M
innodb_log_file_size = 256M
innodb_flush_log_at_trx_commit = 2
innodb_thread_concurrency = 12
innodb_flush_method = O_DIRECT
innodb_file_per_table = 1
innodb_stats_on_metadata=0
innodb_stats_method=nulls_unequal
innodb_stats_sample_pages=32
innodb_io_capacity=500
default-storage-engine=MyISAM
innodb_locks_unsafe_for_binlog=1
transaction-isolation = READ-COMMITTED
innodb_buffer_pool_instances=2
innodb_use_sys_stats_table=1
innodb_file_format=barracuda
userstat=1
slow_query_log=0
slow_query_log_file=slow.log
log_slow_slave_statements = 1
log_slow_verbosity=full
log_slow_admin_statements

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

This issue has already been reported as bug 1011047, please track it there. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.