auth_pam plugin prevents startup
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-
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://
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-
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://
Oct 28 09:45:35 mysqld:
Oct 28 09:45:35 mysqld: key_buffer_
Oct 28 09:45:35 mysqld: read_buffer_
Oct 28 09:45:35 mysqld: max_used_
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_
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/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /lib64/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /usr/sbin/
Oct 28 09:45:35 mysqld: /lib64/
Oct 28 09:45:35 mysqld: /usr/sbin/
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_
myisam_
thread_cache_size = 8
query_cache_size = 256M
thread_concurrency = 4
local-infile=1
join_buffer_
skip-slave-start
long_query_time=1
tmp_table_size=32m
max_heap_
max_connections
read-only
tmpdir=
skip-name-resolve
log-bin=
binlog-format=MIXED
expire_logs_days=8
log-slave-updates=1
server-id = 17521
slave_skip_
slave_compresse
innodb_
innodb_
innodb_
innodb_
innodb_
innodb_flush_method = O_DIRECT
innodb_
innodb_
innodb_
innodb_
innodb_
default-
innodb_
transaction-
innodb_
innodb_
innodb_
userstat=1
slow_query_log=0
slow_query_
log_slow_
log_slow_
log_slow_
This issue has already been reported as bug 1011047, please track it there. Thanks!