- 论坛徽章:
- 0
|
我最近 用和你的同样的版本，遇到了和你的同样的问题。
080719 22:06:58 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 15072540 bytes)
080719 22:06:58 [ERROR] /usr/sbin/mysqld: Sort aborted
080719 22:06:59 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 8388572 bytes)
080719 22:08:09 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 2091064 bytes)
080719 22:08:16 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 2091144 bytes)
080719 22:08:22 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 960 bytes)
080719 22:08:22 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 8164 bytes)
080719 22:08:22 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
080719 22:08:22 - mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=25165824
read_buffer_size=2093056
max_used_connections=234
max_connections=1024
threads_connected=234
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2117624 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x2d92a570
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x415458cc, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c4317
0x814601d
0x814625e
0x8149c35
0x820c7c8
0x82041cb
0x820477b
0x8222b9f
0x822a698
0x822a93d
0x81db11e
0x81e18ba
0x81e2766
0x81e31b7
0x81e3bf0
0x4423cc
0x3ad1ae
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x44df4280 is invalid pointer
thd->thread_id=741524
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
080719 22:08:22 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 2020 bytes)
080719 22:08:22 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
Number of processes running now: 0
080719 22:08:22 mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 17 1153736831
080719 22:08:22 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 17 1158979584
InnoDB: Doing recovery: scanned up to log sequence number 17 1162681199
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 5 row operations to undo
InnoDB: Trx id counter is 0 508687104
080719 22:08:23 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 752211, file name newbbs-bin.000949
InnoDB: Last MySQL binlog file position 0 338398413, file name /var/lib/mysql/binlog/bbs-bin.000123
080719 22:08:29 InnoDB: Started; log sequence number 17 1162681199
InnoDB: Starting in background the rollback of uncommitted transactions
080719 22:08:29 InnoDB: Rolling back trx with id 0 508686541, 4 rows to undo
InnoDB: Rolling back of trx id 0 508686541 completed
080719 22:08:29 InnoDB: Rolling back trx with id 0 508686090, 1 rows to undo
InnoDB: Rolling back of trx id 0 508686090 completed
080719 22:08:29 InnoDB: Rollback of non-prepared transactions completed
080719 22:08:29 [Note] Recovering after a crash using /var/lib/mysql/binlog/bbs-bin
080719 22:08:35 [Note] Starting crash recovery...
080719 22:08:35 [Note] Crash recovery finished.
080719 22:08:35 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode.
080719 22:08:35 [Warning] 'user' entry '@localhost.localdomain' ignored in --skip-name-resolve mode.
080719 22:08:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.51a-community-log' socket: '/usr/local/mysql/mysql.sock' port: 3306 MySQL Community Edition (GPL)
080719 22:10:15 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 8388572 bytes)
080719 22:10:56 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 2091204 bytes)
080719 22:10:59 [ERROR] /usr/sbin/mysqld: Out of memory (Needed 2091064 bytes)
080719 22:11:01 InnoDB: Error: cannot allocate 901120 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 1286660988 bytes. Operating system errno: 12
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: Note that in most 32-bit computers the process
InnoDB: memory space is limited to 2 GB or 4 GB.
InnoDB: We keep retrying the allocation for 60 seconds... |
|
免费注册
发表于 2008-07-23 08:01
发表于 2008-07-23 09:04
发表于 2008-09-05 10:39