Hi... i have a mysql server with:
Mysql version: 4.0.14-standard-log Redhat: 7.2 Kernel: 2.4.18 (Highmem) 4 GB de ram. Well mysql dies with this in the logs: --------------------------------------------------- InnoDB: Apply batch completed InnoDB: In a MySQL replication slave the last master binlog file InnoDB: position 0 44772490, file name kine-bin.5404 InnoDB: Last MySQL binlog file position 0 42520648, file name ./queule-bin.18027 070207 13:00:41 InnoDB: Flushing modified pages from the buffer pool... 070207 13:00:41 InnoDB: Started 070207 13:00:41 Failed to open log (file './queule-relay-bin.352', errno 2) 070207 13:00:41 Failed to open the relay log (relay_log_name='./queule-relay-bin.352', relay_log_pos=42192790 070207 13:00:41 Could not open log file 070207 13:00:41 Failed to initialize the master info structure /usr/sbin/mysqld: ready for connections. Version: '4.0.14-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the InnoDB: previous allocated area! InnoDB: Apparent memory corruption: mem dump len 500; hex 00000000000000000000f04a000058000000ffffffff0000000000000000020800000000000000000000000000000000000002009557a44dfce180fd88d880d85fcb000000005443502f49502028373736290000000000000000000000000000000000000000510000006000f0586000f0580018f058010000009a9999999999014078e64108310000001800f0581800f0582020202020202020202020202020202020202020202020202020200104000000984b00002000000002000035a44dfcc500000000000000000000000000000000000000002100000002000035a44dfcc600000000000000000000000080114108fffffffff100000000000000705b1f09e8000000f63d775f9268a520773073656c2e6300a60800000000000000000000000000000000000000000000d80000000000000000000000d80000004000000000000000442c414342616a61206c61206dfa7369636120656e20747520456e74656c20504353212044657363617267612072696e67746f6e657320706f6c6966f36e69636f732c207265616c746f6e65732079206261636b746f6e657320617175ed2e2056616c6f72204e61766567616369f36e3a205472e16669636f2047505253206f20736567fa6e20626f6c736120636f6e74726174616461611800f058f00000002100000002000035a44dfcc60000; asc ...........J..X......................................W.M........_.....TCP/IP (776)[EMAIL PROTECTED] ......K.. ......5.M......................!......5.M................A.............p[.......=w_.h. InnoDB: Scanning backward trying to find previous allocated mem blocks Freed mem block at - 14712, file mysql.c, line 303 Freed mem block at - 14904, file 0pcur.c, line 28 Freed mem block at - 15096, file 0pcur.c, line 28 Freed mem block at - 15568, file mysql.c, line 303 Freed mem block at - 15784, file mysql.c, line 303 Freed mem block at - 21280, file x0trx.c, line 78 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=402653184 read_buffer_size=2093056 max_used_connections=323 max_connections=800 threads_connected=55 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3666809 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. ----------------------------------------------------------------------- Could this crash be caused because of this: InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the InnoDB: previous allocated area! InnoDB: Apparent memory corruption: mem dump len 500; hex ------------------------------------------------------------------------ i found in the mysql web site this: If you configure innodb_additional_mem_pool_size so small that InnoDB memory allocation spills over from it, then every 4 billionth spill may cause memory corruption. A symptom is a printout like the one following in the .err log. The workaround is to make innodb_additional_mem_pool_size big enough to hold all memory allocation. Use SHOW INNODB STATUS to determine that there is plenty of free space available in the additional mem pool, and the total allocated memory stays rather constant. InnoDB: Error: Mem area size is 0. Possibly a memory overrun of the InnoDB: previous allocated area! InnoDB: Apparent memory corruption: mem dump len 500; hex I have 4 GB RAM, and the value of this variable was: 1 MB, i increased to 500 MB, but i am not sure if this could solve the problem. If somebody can help me with this, it would be great! Thanks!!!!!!! Michael.- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
