Re: [systemd-devel] Strange behavior of socket activation units

2022-02-10 Thread Tuukka Pasanen
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

Re: [systemd-devel] Strange behavior of socket activation units

2022-02-10 Thread Lennart Poettering
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

Re: [systemd-devel] Strange behavior of socket activation units

2022-02-10 Thread Tuukka Pasanen
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

Re: [systemd-devel] Strange behavior of socket activation units

2022-02-07 Thread Lennart Poettering
On Mo, 07.02.22 09:01, Tuukka Pasanen (pasanen.tuu...@gmail.com) wrote: > 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

[systemd-devel] Strange behavior of socket activation units

2022-02-06 Thread Tuukka Pasanen
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