MariaDB Does not Start after Update

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 20.0.5): 27.0.1 Docker
Operating system and version (eg, Ubuntu 20.04): Debian 11 with Docker
Apache or nginx version (eg, Apache 2.4.25): idk i use traefik
PHP version (eg, 7.4): ``
Mariadb version : latest

The issue you are facing: Updated from 25 to 27.0.1 After the Update the web page shows the following:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

The output of your Nextcloud log in Admin > Logging:

"app":"PHP","method":"GET","url":"/settings/ajax/checksetup","message":"dns_get_record(): A temporary server error occurred. at /var/www/html/lib/private/Http/Client/DnsPinMiddleware.php#57"



"app":"richdocuments","method":"GET","url":"/settings/admin/overview","message":"Failed to fetch the Collabora capabilities endpoint: cURL error 6: Could not resolve host: my.secreturl.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html``) for https://my.secreturl.com``/custom_apps/richdocumentscode/proxy.php?req=/hosting/capabilities``"

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'trusted_proxies' => 
  array (
    0 => '172.22.0.4',
  ),
  'overwritehost' => 'my.secreturl.com',
  'overwriteprotocol' => 'https',
  'htaccess.RewriteBase' => '/',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' => 
  array (
    0 => 
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 => 
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
    ),
  ),
  'memcache.distributed' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => 'nextcloud-redis',
    'password' => 'test',
    'port' => 6379,
  ),
  'instanceid' => 'abcdefg',
  'passwordsalt' => 'or/abcdefg',
  'secret' => 'abcdefg/wp',
  'trusted_domains' => 
  array (
    0 => 'my.secreturl.com',
  ),
  'datadirectory' => '/var/www/html/data',
  'dbtype' => 'mysql',
  'version' => '25.0.3.2',
  'overwrite.cli.url' => 'my.secreturl.com',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextcloud-db',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => 'abcdefg',
  'installed' => true,
  'default_phone_region' => 'US',
  'app_install_overwrite' => 
  array (
    0 => 'ojsxc',
  ),
  'loglevel' => 2,
  'maintenance' => false,
  'theme' => '',
  'mail_from_address' => 'sebastian',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'url.com',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtphost' => 'smtp.url.com',
  'mail_smtpport' => '587',
  'mail_smtpsecure' => 'tls',
  'mail_smtpauth' => 1,
  'mail_smtpname' => 'sebastian@url.com',
  'mail_smtppassword' => 'abdef',
);

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

PASTE HERE


Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

PASTE HERE

I did some more research and found that the database does not start.

Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: core
Kernel version: Linux version 5.10.0-9-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.70-1 (2021-09-30)
Fatal signal 11 while backtracing
2023-08-08 16:03:38+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.0.2+maria~ubu2204 started.
2023-08-08 16:03:38+02:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-08-08 16:03:38+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.0.2+maria~ubu2204 started.
2023-08-08 16:03:39+02:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2023-08-08 16:03:39+02:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2023-08-08 16:03:39 0 [Note] Starting MariaDB 11.0.2-MariaDB-1:11.0.2+maria~ubu2204-log source revision 0005f2f06c8e1aea4915887decad67885108a929 as process 1
2023-08-08 16:03:39 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-08-08 16:03:39 0 [Note] InnoDB: Number of transaction pools: 1
2023-08-08 16:03:39 0 [Note] InnoDB: Using generic crc32 instructions
2023-08-08 16:03:39 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-08-08 16:03:39 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked limit, ulimit -l, or https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd (262144 bytes required)
2023-08-08 16:03:39 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2023-08-08 16:03:39 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-08-08 16:03:39 0 [Note] InnoDB: Completed initialization of buffer pool
2023-08-08 16:03:39 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
2023-08-08 16:03:39 0 [Note] InnoDB: Upgrading the change buffer
2023-08-08 16:03:39 0 [ERROR] [FATAL] InnoDB: Unable to find charset-collation for 15
230808 16:03:39 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 11.0.2-MariaDB-1:11.0.2+maria~ubu2204-log source revision: 0005f2f06c8e1aea4915887decad67885108a929
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468023 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 = 0x0 thread_stack 0x49000
Printing to addr2line failed
mariadbd(my_print_stacktrace+0x32)[0x5565240e3a62]
mariadbd(handle_fatal_signal+0x488)[0x556523bb6e28]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f86d37c3520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7f86d3817a7c]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7f86d37c3476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7f86d37a97f3]
mariadbd(+0x69753b)[0x5565237cb53b]
mariadbd(+0x6812f7)[0x5565237b52f7]
mariadbd(+0xdf703f)[0x556523f2b03f]
mariadbd(+0xdd3c92)[0x556523f07c92]
mariadbd(+0x6b2ebc)[0x5565237e6ebc]
mariadbd(+0x691449)[0x5565237c5449]
mariadbd(+0xd7aad9)[0x556523eaead9]
mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x86)[0x556523bba0b6]
mariadbd(+0x83d686)[0x556523971686]
mariadbd(_Z11plugin_initPiPPci+0x91d)[0x55652397284d]
mariadbd(+0x70bb91)[0x55652383fb91]
mariadbd(_Z11mysqld_mainiPPc+0x424)[0x556523845324]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f86d37aad90]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f86d37aae40]
mariadbd(_start+0x25)[0x556523839b05]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        unlimited            unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             unlimited            unlimited            processes 
Max open files            1048576              1048576              files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       63856                63856                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: core
Kernel version: Linux version 5.10.0-9-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.70-1 (2021-09-30)
Fatal signal 11 while backtracing

I’ve got the exact same issue! Have you found a solution yet?