EDIT: Found out what I was doing wrong. I was using mariadb-dump to import instead of just mariadb.
I upgraded from MariaDB 10.x to 11.x. mariadb -V
is showing the updated version.
I exported the database (which was retained during upgrade) via MySQL/MariaDB-dump and got the infamous sandbox error.
Using sed
or piping commands, we can get it uploaded, but it's annoying.
We ran mariadb-upgrade
and it still had the same error.
/*M!999999\- enable the sandbox mode */
-- MariaDB dump 10.19-11.5.2-MariaDB, for debian-linux-gnu (x86_64)
--
-- Host: localhost Database:
-- ------------------------------------------------------
-- Server version 11.5.2-MariaDB-ubu2204
Logically, two things could be going on. One is that somehow the dump program is still the older version, possibly because it was never overwritten despite the rest being upgraded.
Second possibility is that the database itself is still the older version. Either because mariadb-upgrade
was incorrect or maybe a new database has to be made under the current MariaDB.
I have not tried mariabackup
yet, but that looks like a possible solution.
Question: How can I troubleshoot this, and any potential solutions?
EDIT: To clarify the import/export command I am using goes like this;
For export:
mariadb-dump -u username -p DBname > filename.sql
Import:
mariadb-dump -u username -p DBname < filename.sql
NOTE: I used both mariadb-dump and mysql dump (which just switched to maria).
EDIT 2:
So I think the database is exporting fine. The issue is that my database may be corrupted. /M!999999\ is different than /!999999\ sandbox bug. Looks like an M was inserted.
/*M!99999...
. Ifmariadb -V
is showing the latest version, are you using this client in some way? And per below the server version is 11.5.2. How are you using the SQL Dump in such a way as to trigger the sandbox protection? What sort of "upload" are you doing?