Problem with Mariadb on Easy Engine Afther Upgrade #1763
Unanswered
jonasmarques
asked this question in
Support Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Helloall;
I manage a server with 20 smal sites on Digital Ocean.
My setup are a $25 Droplet with high CPU and 4 GB RAM.
2 days ago, my server goes completely offline and the message Error establishing a database connection appears.
Following the community instructions, I made the OS update "From ubunto 20.04 to 22.04" and updated Easy Engine too.
But the erro still here.
My mysql docker logs says:
2023-01-04 15:35:06+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.2+maria
focal started.focal started.2023-01-04 15:35:06+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-01-04 15:35:06+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.2+maria
2023-01-04 15:35:07+00:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2023-01-04 15:35:07+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2023-01-04 15:35:07 0 [Note] mariadbd (server 10.8.2-MariaDB-1:10.8.2+maria~focal-log) starting as process 1 ...
2023-01-04 15:35:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-01-04 15:35:07 0 [Note] InnoDB: Number of transaction pools: 1
2023-01-04 15:35:07 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-01-04 15:35:07 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2023-01-04 15:35:07 0 [Note] InnoDB: Using Linux native AIO
2023-01-04 15:35:07 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-01-04 15:35:07 0 [Note] InnoDB: Completed initialization of buffer pool
2023-01-04 15:35:07 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-01-04 15:35:07 0 [Note] InnoDB: Transaction 160331975 was in the XA prepared state.
2023-01-04 15:35:07 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2023-01-04 15:35:07 0 [Note] InnoDB: Trx id counter is 160332460
2023-01-04 15:35:07 0 [Note] InnoDB: 128 rollback segments are active.
2023-01-04 15:35:07 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2023-01-04 15:35:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-01-04 15:35:07 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-01-04 15:35:07 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
2023-01-04 15:35:07 0 [Note] InnoDB: Rollback of non-prepared transactions completed
2023-01-04 15:35:07 0 [Note] InnoDB: log sequence number 102224639287; transaction id 160332461
2023-01-04 15:35:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-01-04 15:35:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-01-04 15:35:07 0 [Note] InnoDB: Starting recovery for XA transactions...
2023-01-04 15:35:07 0 [Note] InnoDB: Transaction 160331975 in prepared state after recovery
2023-01-04 15:35:07 0 [Note] InnoDB: Transaction contains changes to 2 rows
2023-01-04 15:35:07 0 [Note] InnoDB: 1 transactions in prepared state after recovery
2023-01-04 15:35:07 0 [Note] Found 1 prepared transaction(s) in InnoDB
230104 15:35:07 [ERROR] mysqld got signal 11 ;
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: 10.8.2-MariaDB-1:10.8.2+maria~focal-log
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 = 467995 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
free(): corrupted unsorted chunks
Fatal signal 6 while backtracing
2023-01-04 15:35:07 0 [Note] InnoDB: Buffer pool(s) load completed at 230104 15:35:07
Printing to addr2line failed
mariadbd(my_print_stacktrace+0x32)[0x5638013ba372]
mariadbd(handle_fatal_signal+0x485)[0x563800e7afa5]
free(): corrupted unsorted chunks
Fatal signal 6 while backtracing
Can anyone help me with this?
Beta Was this translation helpful? Give feedback.
All reactions