MariaDB error Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
Zeuskk
Posts: 11
Joined: Sun Feb 07, 2021 11:20 am

MariaDB error

Post by Zeuskk »

Joulinar wrote: Mon Mar 01, 2021 11:29 am hi,

pls can you provide following information

Code: Select all

systemctl restart mariadb.service
journalctl -u mariadb
cat /var/log/mysql/error.log
readlink /var/lib/mysql
readlink -f /var/lib/mysql
Hi, @Joulinar could you also help me with this problem? I have exactly same error like Fabio, but today before i want to uninstall Nextcloud (I installed it 2 months ago but didnt even use it) I was just checking settings in dietpi and saw that MardiDB service "failed". I restarted system and services but it still shows failed.
This is what I got after running your commands:

Code: Select all

root@DietPi:~# systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@DietPi:~# systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.27 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor preset:
 enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─dietpi-services_edit.conf
   Active: failed (Result: exit-code) since Mon 2021-03-01 11:59:12 C
ET; 54s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 6332 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/ru
n/mysqld (code=exited, status=0/SUCCESS)
  Process: 6333 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START
_POSITION (code=exited, status=0/SUCCESS)
  Process: 6335 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR
= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemc
tl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/S
UCCESS)
  Process: 6391 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WS
REP_START_POSITION (code=exited, status=1/FAILURE)
 Main PID: 6391 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

mar 01 11:59:10 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 6391 ...
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 11:59:12 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 11:59:12 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 11:59:12 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
root@DietPi:~# systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@DietPi:~# journalctl -u mariadb
-- Logs begin at Mon 2021-03-01 11:50:30 CET, end at Mon 2021-03-01 12:02:30 CET
. --
mar 01 11:51:01 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 11:51:01 DietPi mysqld[1516]: 2021-03-01 11:51:01 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 1516 ...
mar 01 11:51:01 DietPi mysqld[1516]: 2021-03-01 11:51:01 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 11:51:01 DietPi mysqld[1516]: 2021-03-01 11:51:01 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 11:51:01 DietPi mysqld[1516]: [97B blob data]
mar 01 11:51:01 DietPi mysqld[1516]: 2021-03-01 11:51:01 0 [ERROR] Aborting
mar 01 11:51:01 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 11:51:01 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 11:51:01 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
mar 01 11:52:50 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 11:52:50 DietPi mysqld[2632]: 2021-03-01 11:52:50 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 2632 ...
mar 01 11:52:50 DietPi mysqld[2632]: 2021-03-01 11:52:50 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 11:52:50 DietPi mysqld[2632]: 2021-03-01 11:52:50 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 11:52:50 DietPi mysqld[2632]: [97B blob data]
mar 01 11:52:50 DietPi mysqld[2632]: 2021-03-01 11:52:50 0 [ERROR] Aborting
mar 01 11:52:50 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 11:52:50 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 11:52:50 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
mar 01 11:57:11 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 11:57:11 DietPi mysqld[5265]: 2021-03-01 11:57:11 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 5265 ...
mar 01 11:57:11 DietPi mysqld[5265]: 2021-03-01 11:57:11 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 11:57:11 DietPi mysqld[5265]: 2021-03-01 11:57:11 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 11:57:13 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 11:57:13 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 11:57:13 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
mar 01 11:59:10 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 6391 ...
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 11:59:10 DietPi mysqld[6391]: 2021-03-01 11:59:10 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 11:59:12 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 11:59:12 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 11:59:12 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
mar 01 12:02:28 DietPi systemd[1]: Starting MariaDB 10.3.27 database server...
mar 01 12:02:28 DietPi mysqld[6531]: 2021-03-01 12:02:28 0 [Note] /usr/sbin/mysq
ld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 6531 ...
mar 01 12:02:28 DietPi mysqld[6531]: 2021-03-01 12:02:28 0 [Warning] Could not i
ncrease number of max_open_files to more than 16384 (request: 32186)
mar 01 12:02:28 DietPi mysqld[6531]: 2021-03-01 12:02:28 0 [Warning] Can't creat
e test file /var/lib/mysql/DietPi.lower-test
mar 01 12:02:30 DietPi systemd[1]: mariadb.service: Main
 process exited, code=exited, status=1/FAILURE
mar 01 12:02:30 DietPi systemd[1]: mariadb.service: Fail
ed with result 'exit-code'.
mar 01 12:02:30 DietPi systemd[1]: Failed to start Maria
DB 10.3.27 database server.
root@DietPi:~# cat /var/log/mysql/error.log
2021-03-01 11:57:11 0 [ERROR] mysqld: Can't create/write to file '/var/lib/mysql/aria_log_control' (Errcode: 13 "Permission denied")
2021-03-01 11:57:11 0 [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2021-03-01 11:57:11 0 [ERROR] Plugin 'Aria' init function returned error.
2021-03-01 11:57:11 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2021-03-01 11:57:11 0 [Note] InnoDB: Using Linux native AIO
2021-03-01 11:57:11 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2021-03-01 11:57:11 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-01 11:57:11 0 [Note] InnoDB: Uses event mutexes
2021-03-01 11:57:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-01 11:57:11 0 [Note] InnoDB: Number of pools: 1
2021-03-01 11:57:11 0 [Note] InnoDB: Using generic crc32 instructions
2021-03-01 11:57:11 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-01 11:57:11 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-01 11:57:11 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-01 11:57:11 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 11:57:11 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 11:57:11 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 11:57:11 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 11:57:11 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2021-03-01 11:57:11 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2021-03-01 11:57:11 0 [ERROR] InnoDB: Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
2021-03-01 11:57:11 0 [Note] InnoDB: Starting shutdown...
2021-03-01 11:57:13 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-03-01 11:57:13 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-03-01 11:57:13 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-03-01 11:57:13 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2021-03-01 11:57:13 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-03-01 11:57:13 0 [ERROR] Aborting

Warning: Memory not freed: 392
2021-03-01 11:59:10 0 [ERROR] mysqld: Can't create/write to file '/var/lib/mysql/aria_log_control' (Errcode: 13 "Permission denied")
2021-03-01 11:59:10 0 [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2021-03-01 11:59:10 0 [ERROR] Plugin 'Aria' init function returned error.
2021-03-01 11:59:10 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2021-03-01 11:59:10 0 [Note] InnoDB: Using Linux native AIO
2021-03-01 11:59:10 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2021-03-01 11:59:10 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-01 11:59:10 0 [Note] InnoDB: Uses event mutexes
2021-03-01 11:59:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-01 11:59:10 0 [Note] InnoDB: Number of pools: 1
2021-03-01 11:59:10 0 [Note] InnoDB: Using generic crc32 instructions
2021-03-01 11:59:10 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-01 11:59:10 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-01 11:59:10 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-01 11:59:10 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 11:59:10 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 11:59:10 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 11:59:10 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 11:59:10 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2021-03-01 11:59:10 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2021-03-01 11:59:10 0 [ERROR] InnoDB: Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
2021-03-01 11:59:11 0 [Note] InnoDB: Starting shutdown...
2021-03-01 11:59:12 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-03-01 11:59:12 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-03-01 11:59:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-03-01 11:59:12 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2021-03-01 11:59:12 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-03-01 11:59:12 0 [ERROR] Aborting

Warning: Memory not freed: 392
2021-03-01 12:02:28 0 [ERROR] mysqld: Can't create/write to file '/var/lib/mysql/aria_log_control' (Errcode: 13 "Permission denied")
2021-03-01 12:02:28 0 [ERROR] mysqld: Got error 'Can't create file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2021-03-01 12:02:28 0 [ERROR] Plugin 'Aria' init function returned error.
2021-03-01 12:02:28 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2021-03-01 12:02:28 0 [Note] InnoDB: Using Linux native AIO
2021-03-01 12:02:28 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2021-03-01 12:02:28 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-03-01 12:02:28 0 [Note] InnoDB: Uses event mutexes
2021-03-01 12:02:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-03-01 12:02:28 0 [Note] InnoDB: Number of pools: 1
2021-03-01 12:02:28 0 [Note] InnoDB: Using generic crc32 instructions
2021-03-01 12:02:28 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-03-01 12:02:28 0 [Note] InnoDB: Completed initialization of buffer pool
2021-03-01 12:02:28 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-03-01 12:02:28 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 12:02:28 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 12:02:28 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
2021-03-01 12:02:28 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
2021-03-01 12:02:28 0 [ERROR] InnoDB: Cannot open datafile './ibdata1'
2021-03-01 12:02:28 0 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2021-03-01 12:02:28 0 [ERROR] InnoDB: Database creation was aborted with error Cannot open a file. You may need to delete the ibdata1 file before trying to start up again.
2021-03-01 12:02:29 0 [Note] InnoDB: Starting shutdown...
2021-03-01 12:02:30 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-03-01 12:02:30 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-03-01 12:02:30 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-03-01 12:02:30 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2021-03-01 12:02:30 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-03-01 12:02:30 0 [ERROR] Aborting

Warning: Memory not freed: 392
root@DietPi:~# readlink /var/lib/mysql
/mnt/dietpi_userdata/mysql
root@DietPi:~# readlink -f /var/lib/mysql
/mnt/dietpi_userdata/mysql
Before that I even try to uninstall Nextcloud but uninstall process was very fast, that was strange.
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: MariaDB error

Post by Joulinar »

Hi,

as you have a different issue, I split your topic into an own one.

Looks like your file system permissions are incorrect as you have (Errcode: 13 "Permission denied")

can you check ls -la /var/lib/mysql/
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Zeuskk
Posts: 11
Joined: Sun Feb 07, 2021 11:20 am

Re: MariaDB error

Post by Zeuskk »

Oh, for a second I thought that I didn't apply my post and everything was deleted :P After that I realise that You have split my problem to different topic :lol: thanks
This is what I got

Code: Select all

root@DietPi:~# ls -la /var/lib/mysql/
razem 8
drwxr-xr-x  2 root root 4096 mar  1 11:56 .
drwxr-xr-x 11 root root 4096 mar  1 11:56 ..
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: MariaDB error

Post by Joulinar »

there seems to be something wrong. You are missing the entire content of the directory. Do you moved dietpi userdata to a different place like an external disk?
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Zeuskk
Posts: 11
Joined: Sun Feb 07, 2021 11:20 am

Re: MariaDB error

Post by Zeuskk »

Ye this looks very strange. I didn't touch anything or move userdata, I was just installing/uninstalling few softs from dietpi optimised section and thats all. Maybe I did something during those few months, but as I remember MariaDB was working fine. Maybe few times I saw Failed status but after restart it worked fine again. Can i somehow repair MariaDB? I tried dietpi-software reinstall 88 command but didnt help, still not working.
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: MariaDB error

Post by Joulinar »

last think to verify /mnt/dietpi_userdata/mysql is empty as well?

If yes, you should remove MariaDB as well as Nextcloud form your system and start a new installation
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Zeuskk
Posts: 11
Joined: Sun Feb 07, 2021 11:20 am

Re: MariaDB error

Post by Zeuskk »

Yes, /mnt/dietpi_userdata/mysql is empty.
I have already uninstalled Nextcloud, should I somehow remove some leftovers from system?
To uninstall and install MariaDB i just use commands dietpi-software uninstall 88 and dietpi-software install 88?
Previously I used command dietpi-software reinstall 88 and it didn't help :(

PS. Can I somehow reinstall whole DietPi and not loose software configurations (especially Sonarr/Radarr/Plex/HA) if nothing help?
PS2. I just saw that I also have some problem with Docker and containers not starting on reboot system :( I have put HA in Docker and everything was working fine, but now is not. After reboot only 2/9 start and rest I have to start manually ;/ I think I have to make separate topic for it :(

I'm sorry for so many questions and problems, still learning all of this stuff.

Image
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: MariaDB error

Post by Joulinar »

dietpi-software reinstall will simply try to install packages again. If the system "believe" the package is already available, it will be skipped. So best would be to really do a deinstallation and a new installation.

DietPi is not saving specific config files. This would need to be done manually.

Regarding Docker container failing, in Portainer you have possibility to check the log for each container. Usually it should give an indication why it is failing.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Zeuskk
Posts: 11
Joined: Sun Feb 07, 2021 11:20 am

Re: MariaDB error

Post by Zeuskk »

This is what I got when I run uninstall command

Code: Select all

root@DietPi:~# dietpi-software uninstall 88
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database

 DietPi-Software
─────────────────────────────────────────────────────
 Mode: Automated uninstall

[  OK  ] DietPi-Software | Uninstalling MariaDB: database

And after it I run install command and got this :(

Code: Select all

root@DietPi:~# dietpi-software install 88
[  OK  ] DietPi-Software | Initialised database
[  OK  ] DietPi-Software | Reading database

 DietPi-Software
─────────────────────────────────────────────────────
 Mode: Automated install

[ INFO ] DietPi-Software | 88: MariaDB is already installed
[ INFO ] DietPi-Software | Use "dietpi-software reinstall 88" to force rerun of installation and configuration steps for MariaDB.
[  OK  ] DietPi-Software | No changes applied for: MariaDB
Nothing happens, mysql folder is still empty :(
User avatar
Joulinar
Posts: 4783
Joined: Sat Nov 16, 2019 12:49 am

Re: MariaDB error

Post by Joulinar »

Pls can you try to run uninstall from inside the dietpi-software menu and not using the command. Just to see if uninstall will behave same.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply