Problemas con MySQL Owncloud (Problems with MySQL Owncloud)

Keywords: OwnCloud - Virtual Machines - How to - Other
Description:
Inicio owncloud sobre ubuntu 14.04 y mysql no levanta, y arroja este error
Start owncloud on ubuntu 14.04 and mysql does not raise, and throws this error

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68108 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 = 0 thread_stack 0x40000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace+0x35)[0x9122f5]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x3d8)[0x675f18]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f594ca27330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f594b622c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f594b626028]
/opt/bitnami/mysql/bin/mysqld.bin[0x9eab78]
/opt/bitnami/mysql/bin/mysqld.bin[0x9ec226]
/opt/bitnami/mysql/bin/mysqld.bin[0x9da9ef]
/opt/bitnami/mysql/bin/mysqld.bin[0x9de6e2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f594ca1f184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f594b6e637d]
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.
2018-05-14 02:34:12 3872 [Note] Plugin ‘FEDERATED’ is disabled.
2018-05-14 02:34:12 3872 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-14 02:34:12 3872 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-14 02:34:12 3872 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-14 02:34:12 3872 [Note] InnoDB: Memory barrier is not used
2018-05-14 02:34:12 3872 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-14 02:34:12 3872 [Note] InnoDB: Using Linux native AIO
2018-05-14 02:34:12 3872 [Note] InnoDB: Using CPU crc32 instructions
2018-05-14 02:34:12 3872 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2018-05-14 02:34:12 3872 [Note] InnoDB: Completed initialization of buffer pool
2018-05-14 02:34:12 3872 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-14 02:34:12 3872 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7901802348
2018-05-14 02:34:12 3872 [Note] InnoDB: Database was not shutdown normally!
2018-05-14 02:34:12 3872 [Note] InnoDB: Starting crash recovery.
2018-05-14 02:34:12 3872 [Note] InnoDB: Reading tablespace information from the .ibd files…
2018-05-14 02:34:12 3872 [Note] InnoDB: Restoring possible half-written data pages
2018-05-14 02:34:12 3872 [Note] InnoDB: from the doublewrite buffer…
InnoDB: Doing recovery: scanned up to log sequence number 7901806241
2018-05-14 02:34:12 3872 [Note] InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percent: 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
2018-05-14 02:34:12 3872 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-14 02:34:12 3872 [Note] InnoDB: Waiting for purge to start
2018-05-14 02:34:13 7f0f069ec700 InnoDB: Assertion failure in thread 139702512305920 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:34:13 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68108 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 = 0 thread_stack 0x40000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace+0x35)[0x9122f5]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x3d8)[0x675f18]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f0fbef03330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0fbdafec37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0fbdb02028]
/opt/bitnami/mysql/bin/mysqld.bin[0x9eab78]
/opt/bitnami/mysql/bin/mysqld.bin[0x9ec226]
/opt/bitnami/mysql/bin/mysqld.bin[0x9da9ef]
/opt/bitnami/mysql/bin/mysqld.bin[0x9de6e2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f0fbeefb184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0fbdbc237d]
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.
2018-05-14 02:36:12 4288 [Note] Plugin ‘FEDERATED’ is disabled.
2018-05-14 02:36:12 4288 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-14 02:36:12 4288 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-14 02:36:12 4288 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-14 02:36:12 4288 [Note] InnoDB: Memory barrier is not used
2018-05-14 02:36:12 4288 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-14 02:36:12 4288 [Note] InnoDB: Using Linux native AIO
2018-05-14 02:36:12 4288 [Note] InnoDB: Using CPU crc32 instructions
2018-05-14 02:36:12 4288 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2018-05-14 02:36:12 4288 [Note] InnoDB: Completed initialization of buffer pool
2018-05-14 02:36:12 4288 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-14 02:36:12 4288 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7901802348
2018-05-14 02:36:12 4288 [Note] InnoDB: Database was not shutdown normally!
2018-05-14 02:36:12 4288 [Note] InnoDB: Starting crash recovery.
2018-05-14 02:36:12 4288 [Note] InnoDB: Reading tablespace information from the .ibd files…
2018-05-14 02:36:12 4288 [Note] InnoDB: Restoring possible half-written data pages
2018-05-14 02:36:12 4288 [Note] InnoDB: from the doublewrite buffer…
InnoDB: Doing recovery: scanned up to log sequence number 7901806241
2018-05-14 02:36:12 4288 [Note] InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percent: 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
2018-05-14 02:36:13 4288 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-14 02:36:13 4288 [Note] InnoDB: Waiting for purge to start
2018-05-14 02:36:13 7f5e62cfd700 InnoDB: Assertion failure in thread 140043361441536 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:36:13 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68108 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 = 0 thread_stack 0x40000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace+0x35)[0x9122f5]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x3d8)[0x675f18]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f5f1b214330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f5f19e0fc37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f5f19e13028]
/opt/bitnami/mysql/bin/mysqld.bin[0x9eab78]
/opt/bitnami/mysql/bin/mysqld.bin[0x9ec226]
/opt/bitnami/mysql/bin/mysqld.bin[0x9da9ef]
/opt/bitnami/mysql/bin/mysqld.bin[0x9de6e2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f5f1b20c184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5f19ed337d]
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.
2018-05-14 02:38:12 4703 [Note] Plugin ‘FEDERATED’ is disabled.
2018-05-14 02:38:12 4703 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-14 02:38:12 4703 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-14 02:38:12 4703 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-14 02:38:12 4703 [Note] InnoDB: Memory barrier is not used
2018-05-14 02:38:12 4703 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-14 02:38:12 4703 [Note] InnoDB: Using Linux native AIO
2018-05-14 02:38:12 4703 [Note] InnoDB: Using CPU crc32 instructions
2018-05-14 02:38:12 4703 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2018-05-14 02:38:12 4703 [Note] InnoDB: Completed initialization of buffer pool
2018-05-14 02:38:12 4703 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-14 02:38:12 4703 [Note] InnoDB: Log scan progressed past the checkpoint lsn 7901802348
2018-05-14 02:38:12 4703 [Note] InnoDB: Database was not shutdown normally!
2018-05-14 02:38:12 4703 [Note] InnoDB: Starting crash recovery.
2018-05-14 02:38:12 4703 [Note] InnoDB: Reading tablespace information from the .ibd files…
2018-05-14 02:38:12 4703 [Note] InnoDB: Restoring possible half-written data pages
2018-05-14 02:38:12 4703 [Note] InnoDB: from the doublewrite buffer…
InnoDB: Doing recovery: scanned up to log sequence number 7901806241
2018-05-14 02:38:12 4703 [Note] InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percent: 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
2018-05-14 02:38:13 4703 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-14 02:38:13 4703 [Note] InnoDB: Waiting for purge to start
2018-05-14 02:38:13 7fe2710d5700 InnoDB: Assertion failure in thread 140610536036096 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:38:13 UTC - 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68108 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 = 0 thread_stack 0x40000
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace+0x35)[0x9122f5]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x3d8)[0x675f18]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7fe3295ec330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fe3281e7c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fe3281eb028]
/opt/bitnami/mysql/bin/mysqld.bin[0x9eab78]
/opt/bitnami/mysql/bin/mysqld.bin[0x9ec226]
/opt/bitnami/mysql/bin/mysqld.bin[0x9da9ef]
/opt/bitnami/mysql/bin/mysqld.bin[0x9de6e2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7fe3295e4184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fe3282ab37d]
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.

Hola @joel_moya1387,

Debido al gran numero de usuarios que accede a este foro, vamos a responder el caso en inglés. Por favor, haznos saber si hay algún problema para entender la información

It seems that there is something wrong in the MySQL database, did you modify any setting or perform any change recently?

We have a Support Tool that will gather relevant information for us to debug the issue. Could you please download and execute it on the machine where the stack is running by following the steps described in the guide below?

How to Run the Bitnami Support Tool

Please note that you need to paste the code outputted by the tool in your reply.

Thanks

mysqld.zip (4.3 KB)
error_log.zip (10.3 KB)

Hi @joel_moya1387,

Thank you for that information but could you also share with us the code that the Bitnami Support tool generates when running it in your instance?

Thanks

Hello
Try upload but the photo restricts me, the instance weighs about 9 megabytes, if you can give me an email to send it to you by gmail.

Intente subirlo pero el foto me restringe, la instancia pesa alrededor de 9 megas, si puedes dame un correo para mandartelo por gmail.

Hi @joel_moya1387,

You only need to copy the code here. You can write the code and you don’t need to upload any photo or file to the forum.

Simplemente necesitas mandarnos el código que obtuviste. Puedes escribirlo aquí sin necesidad de enviar una foto o fichero al foro.

Thanks

bueno dias
Disculpa que no entienda un poco lo que me dices, el resultado de la herrmaienta en un comprimido ZIP, que adentro tiene varias log, cual de ellos es lo que necesitas???

Hi @joel_moya1387

If you ran the Bitnami Support tool, it should have given a code to you at the end of the execution, we need that code so we will have access to all the information our tool collects. In case you do not have that code, you can run the Support tool again and share the new code with us.

Al ejecutar la herramienta de soporte, esta mostrará un código al final de la ejecución (algo parecido a b37ekb9c-7982-c8f9-4310-87ef8dre7c6e). Nosotros necesitamos ese código para poder acceder a toda la información que la herramienta obtiene. En caso de que no copiaras ese código, puedes ejecutar la herramienta de soporte de nuevo y compartir dicho código con nosotros.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.