[MDEV-33288] No startup / startup loop Created: 2024-01-21  Updated: 2024-01-22

Status: Needs Feedback
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.6.16
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Full Name Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Using Nextcloudpi, receiving an http 500 internal server error in Nextcloud UI.

journalctl -u mariadb -f

delivers:

Jan 21 19:30:38 nextcloudpi systemd[1]: Starting MariaDB 10.6.16 database server...
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] Starting MariaDB 10.6.16-MariaDB-1:10.6.16+maria~deb11 source revision b83c379420a8846ae4b28768d3c81fa354cca056 as process 96538
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Number of pools: 1
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Using ARMv8 crc32 + pmull instructions
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Using liburing
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Initializing buffer pool, total size = 1073741824, chunk size = 134217728
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Completed initialization of buffer pool
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=63209452151,63209452151
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 2 row operations to undo
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: Trx id counter is 63341608
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: To recover: 376 pages
Jan 21 19:30:58 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:58 0 [Note] InnoDB: 128 rollback segments are active.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: 10.6.16 started; log sequence number 63214302942; transaction id 63341609
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] Plugin 'FEEDBACK' is disabled.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Warning] 'innodb-large-prefix' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Warning] InnoDB: Record in index `fs_id_storage_size` of table `nextcloud`.`oc_filecache` was not found on rollback, trying to insert: TUPLE (info_bits=0, 3 fields): {[8]      $ (0x80000000000024FA),[8]        (0x8000000000000004),[8]    "h  (0x8000000122688EE1)} at: COMPACT RECORD(info_bits=0, 4 fields): {[8]      $ (0x80000000000024F2),[8]        (0x8000000000000004),[8]     d0 (0x8000000000643016),[4]   &(0x00001B26)}
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 2024-01-21 19:30:59 0 [Note] Server socket created on IP: '127.0.0.1'.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: 240121 19:30:59 [ERROR] mysqld got signal 11 ;
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Sorry, we probably made a mistake, and this is a bug.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Your assistance in bug reporting will enable us to fix this for the next release.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: We will try our best to scrape up some info that will hopefully help
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: diagnose the problem, but since we have already crashed,
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: something is definitely wrong and this may fail.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Server version: 10.6.16-MariaDB-1:10.6.16+maria~deb11 source revision: b83c379420a8846ae4b28768d3c81fa354cca056
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: key_buffer_size=134217728
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: read_buffer_size=131072
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: max_used_connections=0
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: max_threads=153
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: thread_count=1
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: It is possible that mysqld could use up to
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468013 K  bytes of memory
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Hope that's ok; if not, decrease some variables in the equation.
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Thread pointer: 0x0
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: Attempting backtrace. You can use the following information to find out
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: where mysqld died. If you see no messages after this, something went
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: terribly wrong...
Jan 21 19:30:59 nextcloudpi mariadbd[96538]: stack_bottom = 0x0 thread_stack 0x49000
Jan 21 19:30:59 nextcloudpi systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
Jan 21 19:30:59 nextcloudpi systemd[1]: mariadb.service: Failed with result 'signal'.
Jan 21 19:30:59 nextcloudpi systemd[1]: Failed to start MariaDB 10.6.16 database server.
Jan 21 19:31:04 nextcloudpi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 23.
Jan 21 19:31:04 nextcloudpi systemd[1]: Stopped MariaDB 10.6.16 database server.



 Comments   
Comment by Marko Mäkelä [ 2024-01-22 ]

Can you try to get stack traces from a core dump of the crash? Since you are using systemd, systemd-coredump and coredumpctl might be a convenient way to get a core dump.

Generated at Thu Feb 08 10:37:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.