HTTP ERROR 599 after upgrade

Having issues with your DietPi installation or found a bug? Post it here.
Posts: 38
Joined: Fri Dec 18, 2020 2:43 pm

Re: HTTP ERROR 599 after upgrade

Post by Fabio »

And this is the result of the error.log

Code: Select all

root@DietPi:~# cat /var/log/mysql/error.log
2021-02-23 14:51:09 0 [Note] InnoDB: Using Linux native AIO
2021-02-23 14:51:09 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-02-23 14:51:09 0 [Note] InnoDB: Uses event mutexes
2021-02-23 14:51:09 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-23 14:51:09 0 [Note] InnoDB: Number of pools: 1
2021-02-23 14:51:09 0 [Note] InnoDB: Using generic crc32 instructions
2021-02-23 14:51:09 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-02-23 14:51:09 0 [Note] InnoDB: Completed initialization of buffer pool
2021-02-23 14:51:09 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-02-23 14:51:09 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=265033300
2021-02-23 14:51:09 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2021-02-23 14:51:09 0x5784f3e0  InnoDB: Assertion failure in file /build/mariadb-10.3-S9bYSW/mariadb-10.3-10.3.27/storage/innobase/rem/ line 815
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
210223 14:51:09 [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

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.3.27-MariaDB-0+deb10u1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466214 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

User avatar
Posts: 4836
Joined: Sat Nov 16, 2019 12:49 am

Re: HTTP ERROR 599 after upgrade

Post by Joulinar »

uhh that looks like some corruption on your database tables as indicated by the error message.

Code: Select all

210223 14:51:09 [ERROR] mysqld got signal 6 ;
We had a similar case in past but no real solution. The user started with a new installation as he had not that much data on his NextCloud

I found quite an old blog describing a possible way to get it fixed. But not sure if this is still working that way. ... tep-guide/

I need to say, I'm not a MariaDB experte and I'm not sure if I could help further on this. Probably better to reach out to some MariaDB specialized board/forum and asking for assistance. Maybe their are more experienced one than I'm :(

one hint: Whatever you do, create a backup of your system first. Just in case thinks will go even more worse.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply