mysql_error:Error starting thread:Resource temporarily unavailable
Sql代碼 www.2cto.com
121031 18:53:17 InnoDB: Unable to open the first data file
InnoDB: Error in opening ./ibdata1
121031 18:53:17 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
121031 18:53:17 InnoDB: Could not open or create data files.
121031 18:53:17 InnoDB: If you tried to add new data files, and it failed here,
121031 18:53:17 InnoDB: you should now edit innodb_data_file_path in my.cnf back
121031 18:53:17 InnoDB: to what it was, and remove the new ibdata files InnoDB created
121031 18:53:17 InnoDB: in this failed attempt. InnoDB only wrote those files full of
121031 18:53:17 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
121031 18:53:17 InnoDB: remove old data files which contain your precious data!
121031 18:53:17 [ERROR] Plugin 'InnoDB' init function returned error.
121031 18:53:17 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
121031 18:53:17 [ERROR] Unknown/unsupported storage engine: INNODB
121031 18:53:17 [ERROR] Aborting
121031 18:53:17 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete
121031 18:53:17 mysqld_safe mysqld from pid file /data/mysql/mysql_3301/mysql_3301.pid ended
121031 18:54:29 mysqld_safe Starting mysqld daemon with databases from /data/mysql/mysql_3301
121031 18:54:29 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-
query-log'/'--slow-query-log-file' instead.
121031 18:54:29 InnoDB: The InnoDB memory heap is disabled
121031 18:54:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121031 18:54:29 InnoDB: Compressed tables use zlib 1.2.3
121031 18:54:30 InnoDB: Initializing buffer pool, size = 2.9G
121031 18:54:30 InnoDB: Completed initialization of buffer pool
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
121031 18:54:30 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
121031 18:54:30 InnoDB: Retrying to lock the first data file
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock ./ibdata1, error: 11
Sql代碼
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
Error starting thread: Resource temporarily unavailable
www.2cto.com
經過深入查詢，排除了內存，句柄數等問題. 並且切換至root用戶打開大量線程時沒有問題。試著調整ulimit各項參數,最後發現是"max user processes "參數有問題，通過root用戶調整大小至 12000,線程數也隨著增大.
Java代碼
root@blog:/home/badqiu# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 143360
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 2048
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 2046
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
www.2cto.com
在linux系統內生效。
vi /etc/security/limits.conf
Java代碼
* soft nproc 12000
* hard nproc 12000
nproc就是"max user processes"，完整描述是: nproc - max number of processes
參數含義:
單個用戶可以啟動的線程數，因為進程也會啟動一個線程，所以也間接對進程數有限制。
注意：
該參數只對普通用戶有用，root用戶不在此限制。 所以用root用戶可以啟動幾萬個線程，無法重現這個問題.
