server crashes with userstats ON
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
New
|
Undecided
|
Unassigned |
Bug Description
With userstat=1, mysql attempts to start and dies immediately. MySQL had been restarted before with userstat=1 without a problem, but now it is having problems. Only thing different is the box has swap now. I've verified this on multiple servers. Commenting out userstat=1 causes the server to start fine. It looks like this bug, https:/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: 20:46:43 UTC - mysqld got signal 11 ;
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: This could be because you hit a bug. It is also possible that this binary
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: We will try our best to scrape up some info that will hopefully help
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: diagnose the problem, but since we have already crashed,
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: something is definitely wrong and this may fail.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Please help us make Percona Server better by reporting any
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: bugs at http://
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld:
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: key_buffer_
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: read_buffer_
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: max_used_
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: max_threads=1200
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: thread_count=0
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: connection_count=0
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: It is possible that mysqld could use up to
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: key_buffer_size + (read_buffer_size + sort_buffer_
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Hope that's ok; if not, decrease some variables in the equation.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld:
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Thread pointer: 0x7fff9932e600
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Attempting backtrace. You can use the following information to find out
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: where mysqld died. If you see no messages after this, something went
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: terribly wrong...
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: stack_bottom = 7fff99331710 thread_stack 0x30000
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /lib/libpthread
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /lib/libc.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: /usr/sbin/
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld:
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Trying to get some variables.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Some pointers may be invalid and cause the dump to abort.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Query (0): is an invalid pointer
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Connection ID (thread ID): 0
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: Status: NOT_KILLED
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld:
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: You may download the Percona Server operations manual by visiting
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: http://
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: in the manual which will help you identify the cause of the crash.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld:
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: The "--memlock" argument, which was enabled, uses system calls that are
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: unreliable and unstable on some operating systems and operating-system versions (notably, some versions of Linux).
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: This crash could be due to use of those buggy OS calls.
Aug 22 16:46:43 DEVELOP-DB daemon err mysqld: You should consider whether you really need the "--memlock" parameter and/or consult the OS distributer about "mlockall" bugs.
Aug 22 16:46:43 DEVELOP-DB daemon notice mysqld_safe: mysqld from pid file /var/lib/
I think this is a duplicate bug of https:/ /bugs.launchpad .net/percona- server/ 5.5/+bug/ 1011047