Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6, 10.11, 11.4, 11.8, 12.0(EOL), 10.11.14
-
None
Description
Using docker image "mariadb:10.11" I made a dump of my NextCloud database. However, I was unable to restore it because I kept getting an error. I finally found it was related to the table memories_planet_geometry from the memories app (https://github.com/pulsejet/memories).
I made a dump without the memories_planet_geometry table and was able to complete my restore. I then made a dump with just that table and am able to reproduce the error. The dump of just that table is 233MB or 83 zipped so I was not able to upload it here.
When I try to start the database doing a restore from this table, first it starts printing out a bunch of junk that looks like data from the dump and then it ends with an error like this:
db-1 | ('1343025_0','1343025_0',1,1343025,'�\0\0\0\0\0\0\0\0\0\0\05�8EG�@��&S�R����H�@�W�2��R����ZӼ@f�c]��R�ŏ1w�@)�\r�0�R����镲@�|гY�R����o�@��v���R�����ׁ@������R��٬�\\m@@�߾�R�NbX9t@~8gD�R��4�8E�@��JY��R��}8g�@�I
|
+�R��B�i�q@�▒s��R��`TR\'�@0�\'
|
�R�5�8EG�@��&S�R�')
|
db-1 | --------------
|
db-1 |
|
db-1 | ERROR 2013 (HY000) at line 124330: Lost connection to server during query
|
db-1 | /usr/local/bin/docker-entrypoint.sh: line 298: 91 Segmentation fault (core dumped) "$@" --skip-networking --default-time-zone=SYSTEM --socket="${SOCKET}" --wsrep_on=OFF --expire-logs-days=0 --skip-slave-start --loose-innodb_buffer_pool_load_at_startup=0
|
This last dump was made with:
docker exec nextcloud-db-1 mariadb-dump --defaults-extra-file=/app/db-env.cnf --single-transaction --host=localhost nextcloud memories_planet_geometry > db_dump_memories_planet_geometry.sql
|
The interesting part of the docker-compose.yml file is:
db:
|
image: mariadb:10.11
|
command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW --log_bin_trust_function_creators=1 --max-allowed-packet=268435456 --key_buffer_size=268435456
|
restart: always
|
volumes:
|
- db:/var/lib/mysql
|
# For mysqldump conf file for backup.
|
- /data/blue/nextcloud/docker/db_test/db-env.cnf:/app/db-env.cnf:ro
|
# On first start initializing the database contents from backup dump https://hub.docker.com/_/mariadb#initializing-the-database-contents
|
- /home/montereytest/db_dump_memories_planet_geometry.sql:/docker-entrypoint-initdb.d/db_dump_nextcloud.sql
|
environment:
|
- MARIADB_AUTO_UPGRADE=1
|
- MARIADB_DISABLE_UPGRADE_BACKUP=1
|
- MYSQL_DATABASE=db_test
|
- MYSQL_USER=s=db_test
|
- MYSQL_ROOT_PASSWORD_FILE=/run/secrets/db_root_password
|
- MYSQL_PASSWORD_FILE=/run/secrets/db_password
|
secrets:
|
- db_root_password
|
- db_password
|
profiles: [db-build, db-test]
|
Here is a link to the dump file. Not sure how long I will leave it there.
https://drive.google.com/file/d/1nSSJeZgUOWtqrVr1AZCBarTGRwhYyBZK/view?usp=sharing
Let me know if there is anything more I can do to help.
P.S. Here is the stackexchange thread that lead to this.
https://dba.stackexchange.com/questions/347306/mariadb-docker-fails-to-initialize-database-contents-from-dump-file
Update:
I used the following command to just try a different way of dumping the table.
sudo docker exec db_test-db-1 sh -c 'mariadb -v -u root -p"rootpassword" nextcloud < /docker-entrypoint-initdb.d/db_dump_nextcloud.sql'
|
There was some interesting difference. Most of the time it ran without any kind of an error, at least that I would see in the output on the screen. However, it is not completing successfully because every time it would give me a different number of records (SELECT count
FROM memories_planet_geometry ).
About the 5th time it got to some lines that looked like the end of the dump with 560659 records. I was going to share the last part of the output here but it seems to freeze up the terminal I have open the the ssh connection to the test server.
('13246111_28','13246111_28',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0?������\Z/��]@�D����[B>���]@��~j�����7���]@.�!�����:p��]@?������\Z/��]@'), |
('13246111_29','13246111_29',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0V-��o�[�����]@�� h\"l�r�m�*:���]@V-��o�[�����]@'), |
('13246111_3','13246111_3',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0r�-��������]@?���9��m4�]@��v�����ׁsF�]@Y��\0����@���]@r�-��������]@'), |
('13246111_30','13246111_30',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0r�������46�]@��B�i��#J{�/�]@W[�������6\Z�]@9��v���Gx |
$�]@r�������46�]@'), |
('13246111_31','13246111_31',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0�@�����\nףp=�]@�ǘ������(\\��]@��_���\'�W�]@���<,�� |
F%u�]@�@�����\nףp=�]@'),
|
('13246111_32','13246111_32',1,13246111,'�\0\0\0\0\0\0\0\0\0\0\0usertest@systemtest:~$ |
It is interesting how it dumps a bunch of numbers and letters to the local terminal after the run. This one bellow was very short. Sometimes there is two to three lines. This one also give an example of the error message I do see some times.
$(~
|
G@1�*▒��I@6�>W[G@'), |
('5498487_0','5498487_0',1,5498487,'�\0\0\0\0\0\0\0\0\0\0\0�_vO�>@M�\rOZ��g��s�>@$����Z�J{�/L�>@c�ZB> Z�F%u��>@��?�Z��_vO�>@M�\rOZ�') |
--------------
|
|
|
ERROR 2013 (HY000) at line 402719: Lost connection to server during query |
usertest@systemtest:~$ 62;1;4c62;1;4c62;1;4c |
Attachments
Issue Links
- duplicates
-
-
- Confirmed
-
- relates to
-
-
- In Progress
-
-
-
- Open
-