MySQL server crashes with owncloud file upload

Bug #1910545 reported by Alexander Balda
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-8.0 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Precondition:
I updated my server from latest Ubuntu 18.04.5 LTS to Ubuntu 20.04 LTS and this updated MySQL server from 5.7 to 8.0 and PHP from 7.2 to 7.4.
The update of PHP version caused a need to update owncloud from 10.4 to 10.6 what was also done.

So system is running:
root@cloud:/# lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04

with package
root@cloud:/# apt-cache policy mysql-server
mysql-server:
  Installiert: 8.0.22-0ubuntu0.20.04.3
  Installationskandidat: 8.0.22-0ubuntu0.20.04.3
  Versionstabelle:
 *** 8.0.22-0ubuntu0.20.04.3 500
        500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
        100 /var/lib/dpkg/status
     8.0.19-0ubuntu5 500
        500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu focal/main i386 Packages

Error reproduction:
What I did:
Uploading several files (or one bigger one about 75 MB or more) via owncloud webinterface.

What I expected:
Working upload without an error; file occuring in physical file system of teh server and the virtual file system of owncloud as well.

What happened:
Owncloud reported General error: 2006 MySQL server has gone away (see screenshot attached).
File was physically uploaded completely into server filesystem, but did not appear in ownclouds virtual file system.
In mySQL error log (see below) there was an crash report of mysql server.

Backtrace out of mySQL error.log:

13:19:20 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f501c02fa00
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 = 7f50a430ad90 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x560becce4871]
/usr/sbin/mysqld(handle_fatal_signal+0x31b) [0x560bebb494cb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0) [0x7f50b978f3c0]
/usr/sbin/mysqld(Item_splocal::this_item()+0x18) [0x560bebc74938]
/usr/sbin/mysqld(Item_sp_variable::val_str(String*)+0x24) [0x560bebc76de4]
/usr/sbin/mysqld(Arg_comparator::compare_string()+0x2b) [0x560bebc9b18b]
/usr/sbin/mysqld(Item_func_eq::val_int()+0x2f) [0x560bebc9707f]
/usr/sbin/mysqld(Item::val_bool()+0xcd) [0x560bebc7c07d]
/usr/sbin/mysqld(Item_cond_and::val_int()+0x44) [0x560bebc98364]
/usr/sbin/mysqld(Item::val_bool()+0xcd) [0x560bebc7c07d]
/usr/sbin/mysqld(sp_instr_jump_if_not::exec_core(THD*, unsigned int*)+0x31) [0x560beb986c51]
/usr/sbin/mysqld(sp_lex_instr::reset_lex_and_exec_core(THD*, unsigned int*, bool)+0x614) [0x560beb988da4]
/usr/sbin/mysqld(sp_lex_instr::validate_lex_and_execute_core(THD*, unsigned int*, bool)+0x9e) [0x560beb98983e]
/usr/sbin/mysqld(sp_head::execute(THD*, bool)+0x5db) [0x560beb97edeb]
/usr/sbin/mysqld(sp_head::execute_trigger(THD*, MYSQL_LEX_CSTRING const&, MYSQL_LEX_CSTRING const&, GRANT_INFO*)+0x2a5) [0x560beb97f715]
/usr/sbin/mysqld(Trigger::execute(THD*)+0x10c) [0x560bebb1506c]
/usr/sbin/mysqld(Trigger_chain::execute_triggers(THD*)+0x20) [0x560bebb16450]
/usr/sbin/mysqld(Table_trigger_dispatcher::process_triggers(THD*, enum_trigger_event_type, enum_trigger_action_time_type, bool)+0x4a) [0x560bebb0fdba]
/usr/sbin/mysqld(fill_record_n_invoke_before_triggers(THD*, COPY_INFO*, mem_root_deque<Item*> const&, mem_root_deque<Item*> const&, TABLE*, enum_trigger_event_type, int, bool, bool*)+0x409) [0x560beb994ef9]
/usr/sbin/mysqld(Sql_cmd_insert_values::execute_inner(THD*)+0x464) [0x560bebeb2bc4]
/usr/sbin/mysqld(Sql_cmd_dml::execute(THD*)+0x535) [0x560beba678b5]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x9f0) [0x560beba0b1a0]
/usr/sbin/mysqld(mysql_parse(THD*, Parser_state*)+0x42b) [0x560beba0f88b]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x1edc) [0x560beba11c0c]
/usr/sbin/mysqld(do_command(THD*)+0x1a4) [0x560beba128b4]
/usr/sbin/mysqld(+0x1107850) [0x560bebb3a850]
/usr/sbin/mysqld(+0x285c1ba) [0x560bed28f1ba]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f50b9783609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f50b8ec9293]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f501c181b28): is an invalid pointer
Connection ID (thread ID): 14774
Status: NOT_KILLED

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.
2021-01-07T13:19:20.861055Z 0 [Warning] [MY-011068] [Server] The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-01-07T13:19:20.863180Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.22-0ubuntu0.20.04.3) starting as process 416754
2021-01-07T13:19:20.872973Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-01-07T13:19:21.768041Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-01-07T13:19:21.894771Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2021-01-07T13:19:21.894940Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001287 - 'validate password plugin' is deprecated and will be removed in a future release. Please use validate_password component instead
2021-01-07T13:19:21.945307Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2021-01-07T13:19:21.958548Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2021-01-07T13:19:22.016931Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-01-07T13:19:22.017116Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2021-01-07T13:19:22.037020Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.22-0ubuntu0.20.04.3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu).

Revision history for this message
Alexander Balda (mb0156ba) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
I come by retriaging bugs that were dormant for too long - trying to give them another chance.

In this case no one else chimed in yet e.g. seeing the same issue.
And OTOH it never reached the point to be well reproducible outside your environment for debugging :-/

By now - due to time passing - we are multiple stable releases further down the road.
 mysql-8.0 | 8.0.29-0ubuntu0.20.04.3 | focal-updates | source

Maybe it is worth a try (I assume you have deployed some workaround by now that you need to revert to test this?) with the new version if the same still happens.

Or OTOH maybe you found more about this but didn't yet have a chance to update the bug.
In this case please share what you learned about this issue.

Changed in mysql-8.0 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-8.0 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.