Mysql_error: Error starting thread: Resource temporarily unava

Mysql_error: Error starting thread: Resource temporarily unavailable SQL code 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: cocould 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 shoshould 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' registry 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_3 301. 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 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 ato Mic 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 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. innoD B: 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 code InnoDB: Error number 11 means 'Resource temporarily unavailable '. error starting thread: Resource temporarily unavailable www.2cto.com has gone through in-depth queries to eliminate problems such as memory and handle count. there is no problem when switching to the root user to open a large number of threads. Try to adjust the ulimit parameters, and finally find that there is a problem with the "max user processes" parameter. by adjusting the size of the root user to 12000, the number of threads also increases. java code 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 takes effect in linux. Vi/etc/security/limits. conf Java code * soft nproc 12000 * hard nproc 12000 nproc is "max user processes". The complete description is: nproc-max number of processes parameter meaning: number of threads that a single user can start, because the process also starts a thread, it also indirectly limits the number of processes. Note: this parameter is only useful to common users, and root users are not limited here. Therefore, the root user can start tens of thousands of threads and cannot reproduce this problem.