Skip to main content ↑ ↓
Topic: MariaDB manual intervention to Update FAILED (Read 683 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

MariaDB manual intervention to Update FAILED

I got this in log:

"warning: directory permissions differ on /usr/lib/mysql/plugin/auth_pam_tool_dir/
filesystem: 700  package: 755"

I also got this right below:
"upgraded mariadb (10.6.4-1 -> 10.6.5-1)"

And when I tried this:
"mariadb-upgrade -u root -p"

I got this:

Enter password:
Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
FATAL ERROR: Upgrade failed

WHAT PASSWORD? Neither root or sudo pass work.

Now what?

Re: MariaDB manual intervention to Update FAILED

Reply #2 –
It says:
"Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)'

Shouldn't it be "/run/runit/" ?


And  what does it mean?:

""warning: directory permissions differ on /usr/lib/mysql/plugin/auth_pam_tool_dir/
filesystem: 700  package: 755""

What is the correct procedure to update mysql on Artix with runit?

Surely you don't expect me to run:

systemctl restart mariadb.service && mariadb-upgrade -u root -p

And I have never ever started it in the first place. Was it even running in the first place?

Re: MariaDB manual intervention to Update FAILED

Reply #3 –
You should actually start the service with runit first (install mariadb-runit if you haven't already). It doesn't sound like it is up hence why there is no socket. And yes, '/run/mysqld/mysqld.sock' is the correct path. It's normal for programs to put things in /run

Re: MariaDB manual intervention to Update FAILED

Reply #4 –
Quote from: Runner – on
"mariadb-upgrade -u root -p"

WHAT PASSWORD? Neither root or sudo pass work
You shouldn't be attempting to upgrade mariadb outside of pacman anyway. If you've done so in the past that might be where your problems stem from ?

But on the WHAT PASSWORD? question. It wants your mariadb (mysql) root password. Which is not the same thing as your root password. So unless you've set the two (linux root pass & mariadb root pass) to the same password, entering your linux root won't work. Even if mariadb was running.
And as stated I'm fairly sure you don't want to be running that command anyway.
I've never used mariadb on Artix or any Arch like but have for years on debian and I've never used
Quote
mariadb-upgrade
Just left it to the package manager .

Re: MariaDB manual intervention to Update FAILED

Reply #5 –
I don't know which packages had installed mariadb. I also have never ever upgraded mariadb manually. And I also have never set a password for mariadb. My lose guess would be that its part of KDE Plasma (various databases - krunner, inexing, including KDE PIM - i.e. full KDE Plasma, withouch GTK rubbish from mutter/gnome). Does it mean that something I havent' used in full KDE Plasma will have bugs/security holes because KDE Plasma WAS NOT PROPERLY UPDATED BY PACMAN? Shouldn't  pacman take care of it? Does this mean that runnit pacman and plasma become lesss and less compatible and they fall APART and I should give up? I wouldn't like it because system with runit and only a few services running is very, very snappy.

What should be the correct procedure now? Step by step in Artix ?

P.S. As you mentioned With systemd in Debian 10 and 11 (which I also both maintain) I have never ever had an issue.

Re: MariaDB manual intervention to Update FAILED

Reply #6 –
What does
Code: [Select]
pacman -Qi mariadb
output ?

Re: MariaDB manual intervention to Update FAILED

Reply #7 –
Akonadi, what else  :D I have manually started mariadb for runnit (symlinks in subfolder, sv up...).  Now what?







Re: MariaDB manual intervention to Update FAILED

Reply #8 –
Any answer how to fix it?