Re: [systemd-devel] Strange behavior of socket activation units
Hello, Ok thank you for support and I'll figure out. Tuukka Lennart Poettering kirjoitti 10.2.2022 klo 12.50: On Do, 10.02.22 10:09, Tuukka Pasanen (pasanen.tuu...@gmail.com) wrote: Hello, Thank you for your sharp answer. Is there any way to debug what launches these sockets and makes socket activation? these log messages look like they are generated client side. hence figure out where they come from. Lennart -- Lennart Poettering, Berlin
Re: [systemd-devel] Strange behavior of socket activation units
Hello, Thank you for your sharp answer. Is there any way to debug what launches these sockets and makes socket activation? Tuukka Lennart Poettering kirjoitti 7.2.2022 klo 14.40: My educated guess is that some script specific to mariadb in debian assumes that you only run templated instances of mariadb, and if you don#t things break. Plese work with the mariadb people at Debian to figure this out, there's nothing much we can do from systemd upstream about that. Lennart -- Lennart Poettering, Berlin
[systemd-devel] Strange behavior of socket activation units
Hello, I have encountered this kind of problem. This particularly is MariaDB 10.6 installation to Debian. Nearly every application that is restarted/started dies on: Failed to get properties: Unit name mariadb-extra@.socket is missing the instance name. Failed to get properties: Unit name mariadb@.socket is missing the instance name. This is kind of strange as those are for multi target version and should not be launched if I don't have mariadb@something.service added or make specified systemctl enable mariadb@something.socker which I haven't. They don't show up in dependencies of mariadb.service or other service file? Sincerely, Tuukka
