[systemd-devel] My experience with MySQL and systemctl

[Samuel Williams]

Lennart, it's absolutely possible this is the case, and as I stated
originally, I'm not sure where fault lies, but just that some issues
happened. I agree, perhaps MySQL/MariaDB should output one line for
each progress step.

On 20 April 2017 at 04:41, Lennart Poettering <lennart at poettering.net> wrote:
> On Wed, 19.04.17 15:25, Samuel Williams (space.ship.traveller at gmail.com) wrote:
>
>> I am using MariaDB - and the .service file launches mysqld directly -
>> it doesn't use mysqld_safe
>>
>> Here is the basic config, from Arch linux package:
>>
>> -- mariadb.service
>> ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER
>> $_WSREP_START_POSITION
>> ExecStartPost=/bin/sh -c "systemctl unset-environment _WSREP_START_POSITION"
>> KillMode=process
>> KillSignal=SIGTERM
>> SendSIGKILL=no
>> Restart=on-abort
>> RestartSec=5s
>>
>> I checked correctly and the log output did appear stopped. Even though
>> the process was still running. The log output of mysqld during
>> recovery is only single progress counter without any newline
>> character.. perhaps this was part of the problem?
>
> So mysql is not logging via syslog() but via stdout/stderr? If so:
> journald expects \n as log record separator, and if you never send any
> then the record will never be generated (except when an EOF is read).
>
> Lennart
>
> --
> Lennart Poettering, Red Hat