[MDEV-26466] Failed to get properties: mariadb-extra@.socket Created: 2021-08-24  Updated: 2022-03-23  Resolved: 2022-03-23

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 10.6.4
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Alex Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: mariadb-extra, socket
Environment:

Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
x86_64
Linux 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux

Issue Links:
Duplicate
duplicates MDEV-27715 what mariadb has with nginx? Closed

 Description   

Perform a clean install of MariaDB 10.6.4 on Debian 10 OS and then run the command:

service mariadb stop
 
service mariadb start

And before stopping/starting, you will see the message:

Failed to get properties: Unit name mariadb-extra @ .socket is neither a valid invocation ID nor unit name.
 
Failed to get properties: Unit name mariadb @ .socket is neither a valid invocation ID nor unit name.

The same message appears before stopping/starting any service.

This way you can easily reproduce the problem in MariaDB 10.6.4.



 Comments   
Comment by Alice Sherepa [ 2021-11-26 ]

Could you please add the output of

systemctl --version | head -1

There was a systemd bug introduced in v233 and fixed in v240 (https://github.com/systemd/systemd/issues/9554 , https://newbedev.com/why-does-systemd-reject-my-unit-name-as-neither-a-valid-invocation-id-nor-unit-name)

Comment by Alex [ 2021-11-26 ]

Command output systemctl --version | head -1
systemd 241 (241)

My hosting support easily reproduced the issue by installing Debian GNU/Linux 10 and MariaDB 10.6.4
But I did not find a solution - the MariaDB developers should look for a solution. This is their answer.

Comment by Daniel Black [ 2022-03-23 ]

"service" distributed by Debian/Ubuntu is broken. Use systemctl.

Generated at Thu Feb 08 09:45:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.