mysql_error:Error starting thread:Resource temporarily unava_MySQL
bitsCN.com
mysql_error:Error starting thread:Resource temporarily unavailable
Sql代码
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
经过深入查询,排除了内存,句柄数等问题. 并且切换至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
在linux系统内生效。
vi /etc/security/limits.conf
Java代码
* soft nproc 12000
* hard nproc 12000
nproc就是"max user processes",完整描述是: nproc - max number of processes
参数含义:
单个用户可以启动的线程数,因为进程也会启动一个线程,所以也间接对进程数有限制。
注意:
该参数只对普通用户有用,root用户不在此限制。 所以用root用户可以启动几万个线程,无法重现这个问题.
bitsCN.com

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

InnoDBBufferPool reduces disk I/O by caching data and indexing pages, improving database performance. Its working principle includes: 1. Data reading: Read data from BufferPool; 2. Data writing: After modifying the data, write to BufferPool and refresh it to disk regularly; 3. Cache management: Use the LRU algorithm to manage cache pages; 4. Reading mechanism: Load adjacent data pages in advance. By sizing the BufferPool and using multiple instances, database performance can be optimized.

MySQL efficiently manages structured data through table structure and SQL query, and implements inter-table relationships through foreign keys. 1. Define the data format and type when creating a table. 2. Use foreign keys to establish relationships between tables. 3. Improve performance through indexing and query optimization. 4. Regularly backup and monitor databases to ensure data security and performance optimization.
