List:General Discussion« Previous MessageNext Message »
From:AdmSA Date:March 28 2012 9:56am
Subject:Mysqld remote dont stop
View as plain text  
Hello:

We have a problem when we try to stop the mysql service (mysql  Ver 14.14 Distrib 5.5.12,
for Linux (x86_64) using readline 5.1) on a remote server throught SSH.
The problem is that mysql_safe, start again mysqld before that mysql kill all the
connection and stop the process. So cannot stop properly the server.
Attached the log of .err when we send the command "ssh server service mysql stop"
Thanks for your help.

Muchas gracias y un saludo.
________________________________
ADMSA - Administración de Sistemas Abiertos - Diego

Servicio de Sistemas Informáticos - División de Tecnologías de la
Información
Oficina Española de Patentes y Marcas - Mº.  Industria, Turismo y Comercio
DTI  - Servicio de Sistemas Informáticos
admsa@stripped<mailto:admsa@stripped>
________________________________
91 34 95361 Francisco Nievas
91 34 93091 Roberto Toledo
91 34 93092 Diego Martín


________________________________
Oficina Española de Patentes y Marcas
**********************************************************************************************
Este mensaje y los ficheros adjuntos pueden contener información confidencial
destinada solamente a la(s) 
persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar
inmediatamente al remitente y destruir el 
mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, la Oficina
Española de Patentes y Marcas 
no se hace responsable por su contenido. Su contenido no constituye ningún
compromiso para la Oficina 
Española de Patentes y Marcas. salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede
garantizar nada al 
respecto y no será responsable de cualesquiera daños que puedan resultar de
una transmisión de virus.

**********************************************************************************************
Attachment: [text/html]
120328 6:00:38 [Note] /usr/sbin/mysqld: Normal shutdown 120328 6:00:38 [Note] Event Scheduler: Purging the queue. 0 events 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 13859 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 13853 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 229 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 46 user: xxx InnoDB: Error: trying to free a corrupt fetch buffer. InnoDB: Apparent memory corruption: mem dump len 500; hex 000000000000000000000000000000000000000000000000000000000000709c001d00000000d0e3001d00000000000000000000000021000000000000007078692f6a7078695f646174613123502350303300000000210000000000000048ea031d00000000682a15ed3f00000020000000000000004110000000000000b307952d00000000773073656c2e6300880c00000000000001000000000000009083001d000000009083001d000000000000000000000000000000000000000030100000000000003010000000000000000000000000000030100000000000007800000000000000000000000000000000000000000000001bc3053700f2fbae0000000000a00f003c003f0078006d006c002000760065007200730069006f006e003d00270031002e00300027003f003e003c004a0050005800490044004f00430053004b004c00200044004f004300490044003d002700310031003400360037003700360032002700200045005800540044004f004300490044003d002700450031002000200020002000200030003100330035004600310041003900430036004600450050003100200027003e003c0053004b004c004f0042004a002000490044003d0027003100270020004f00460046003d0027003000270020004c0045004e003d0027003900330030003800370027002000; asc p ! pxi/jpxi_data1#P#P03 ! H h* ? A - w0sel.c 0 0 0 x 7 < ? x m l v e r s i o n = ' 1 . 0 ' ? > < J P X I D O C S K L D O C I D = ' 1 1 4 6 7 7 6 2 ' E X T D O C I D = ' E 1 0 1 3 5 F 1 A 9 C 6 F E P 1 ' > < S K L O B J I D = ' 1 ' O F F = ' 0 ' L E N = ' 9 3 0 8 7 ' ; InnoDB: Scanning backward trying to find previous allocated mem blocks Mem block at - 124, file w0sel.c, line 3208 Mem block at - 572, file t0mem.c, line 74 Freed mem block at - 2940, file mysql.c, line 677 Mem block at - 7068, file w0sel.c, line 3208 Mem block at - 10204, file w0sel.c, line 3208 Mem block at - 13340, file w0sel.c, line 3208 Mem block at - 16476, file w0sel.c, line 3208 Mem block at - 19612, file w0sel.c, line 3208 Mem block at - 22748, file w0sel.c, line 3208 Mem block at - 25884, file w0sel.c, line 3208 InnoDB: Scanning forward trying to find next allocated mem blocks Mem block at + 20596, file t0mem.c, line 74 Mem block at + 22436, file t0mem.c, line 266 Mem block at + 22676, file t0mem.c, line 266 Mem block at + 23252, file t0mem.c, line 266 Mem block at + 24660, file mysql.c, line 677 Mem block at + 25652, file mysql.c, line 677 Mem block at + 27476, file 0pcur.c, line 46 Mem block at + 28196, file t0mem.c, line 74 Mem block at + 30036, file t0mem.c, line 266 Mem block at + 30612, file t0mem.c, line 266 120328 6:00:41 InnoDB: Assertion failure in thread 1242917184 in file row0mysql.c line 798 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 120328 6:00:41 - mysqld got signal 6 ; 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=3145728000 read_buffer_size=2147479552 max_used_connections=59 max_threads=100 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 233267938 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 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... stack_bottom = (nil) thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7cad69] /usr/sbin/mysqld(handle_segfault+0x379)[0x4fdad9] /lib64/libpthread.so.0[0x3feda0eb10] /lib64/libc.so.6(gsignal+0x35)[0x3fece30265] /lib64/libc.so.6(abort+0x110)[0x3fece31d10] /usr/sbin/mysqld[0x8460bd] /usr/sbin/mysqld[0x831aac] /usr/sbin/mysqld(_Z8closefrmP5TABLEb+0x108)[0x5ee088] /usr/sbin/mysqld(_Z19close_cached_tablesP3THDP10TABLE_LISTbm+0x705)[0x5423c5] /usr/sbin/mysqld(_Z24table_def_start_shutdownv+0xd0)[0x5427e0] /usr/sbin/mysqld[0x50166a] /usr/sbin/mysqld(_Z10unireg_endv+0xe)[0x5057ae] /usr/sbin/mysqld(kill_server_thread+0x873)[0x506033] /lib64/libpthread.so.0[0x3feda0673d] /lib64/libc.so.6(clone+0x6d)[0x3feced3d1d] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 120328 06:00:52 mysqld_safe Number of processes running now: 0 120328 06:00:52 mysqld_safe mysqld restarted 120328 6:00:52 [Warning] The syntax '--max_long_data_size' is deprecated and will be removed in a future release. Please use '--max_allowed_packet' instead. 120328 6:02:11 [Note] Plugin 'FEDERATED' is disabled. 120328 6:02:11 InnoDB: The InnoDB memory heap is disabled 120328 6:02:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120328 6:02:11 InnoDB: Compressed tables use zlib 1.2.3 120328 6:02:11 InnoDB: Using Linux native AIO 120328 6:02:13 InnoDB: Initializing buffer pool, size = 4.0G 120328 6:02:53 InnoDB: Completed initialization of buffer pool 120328 6:02:56 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 4566505439051 120328 6:03:06 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 4566505561590 120328 6:03:15 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 120328 6:03:17 InnoDB: Waiting for the background threads to start 120328 6:03:18 InnoDB: 1.1.6 started; log sequence number 4566505561590 120328 6:03:18 [Note] Event Scheduler: Loaded 0 events 120328 6:03:18 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.12-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 120328 06:07:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120328 6:07:08 [Warning] The syntax '--max_long_data_size' is deprecated and will be removed in a future release. Please use '--max_allowed_packet' instead. 120328 6:08:00 [Note] Plugin 'FEDERATED' is disabled. 120328 6:08:00 InnoDB: The InnoDB memory heap is disabled 120328 6:08:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120328 6:08:00 InnoDB: Compressed tables use zlib 1.2.3 120328 6:08:00 InnoDB: Using Linux native AIO 120328 6:08:05 InnoDB: Initializing buffer pool, size = 4.0G 120328 6:08:43 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. 120328 6:08:46 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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. 120328 6:10:26 InnoDB: Unable to open the first data file InnoDB: Error in opening ./ibdata1 120328 6:10:26 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 120328 6:10:26 InnoDB: Could not open or create data files. 120328 6:10:26 InnoDB: If you tried to add new data files, and it failed here, 120328 6:10:26 InnoDB: you should now edit innodb_data_file_path in my.cnf back 120328 6:10:26 InnoDB: to what it was, and remove the new ibdata files InnoDB created 120328 6:10:26 InnoDB: in this failed attempt. InnoDB only wrote those files full of 120328 6:10:26 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 120328 6:10:26 InnoDB: remove old data files which contain your precious data! 120328 6:10:26 [ERROR] Plugin 'InnoDB' init function returned error. 120328 6:10:26 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 120328 6:10:26 [ERROR] Unknown/unsupported storage engine: InnoDB 120328 6:10:26 [ERROR] Aborting 120328 6:10:26 [Note] /usr/sbin/mysqld: Shutdown complete 120328 06:10:26 mysqld_safe mysqld from pid file /var/lib/mysql/server.pid ended
Thread
Mysqld remote dont stop AdmSA28 Mar
  • Re: Mysqld remote dont stopJohan De Meersman28 Mar