Re: [systemd-devel] My experience with MySQL and systemctl

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

Re: [systemd-devel] My experience with MySQL and systemctl

On Wed, 19.04.17 15:25, Samuel Williams (space.ship.travel...@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

Re: [systemd-devel] My experience with MySQL and systemctl

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

Re: [systemd-devel] My experience with MySQL and systemctl

Also, it was me sending SIGKILL, not systemctl. systemctl sent SIGTERM and then finished. But process is still running, so system ended up in weird state. On 19 April 2017 at 15:25, Samuel Williams wrote: > I am using MariaDB - and the .service file launches

Re: [systemd-devel] My experience with MySQL and systemctl

On 04/13/2017 02:48 AM, Lennart Poettering wrote: > On Wed, 12.04.17 21:09, Michael Biebl (mbi...@gmail.com) wrote: > >> 2017-04-12 20:24 GMT+02:00 Tomasz Torcz : >>> On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: The right (or, better) solution IMHO would be

Re: [systemd-devel] My experience with MySQL and systemctl

On Wed, 12.04.17 21:09, Michael Biebl (mbi...@gmail.com) wrote: > 2017-04-12 20:24 GMT+02:00 Tomasz Torcz : > > On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: > >> The right (or, better) solution IMHO would be for mysqld to signal to > >> systemd that it's running

Re: [systemd-devel] My experience with MySQL and systemctl

Am 13.04.2017 um 06:06 schrieb Andrei Borzenkov: Maybe we'd need a new state paramenter, like STARTING=1 which could be sent by the daemon to systemd in regular intervals and would signal systemd that the startup of the daemon is in process and the daemon is not actually hung. You still need

Re: [systemd-devel] My experience with MySQL and systemctl

12.04.2017 22:09, Michael Biebl пишет: > 2017-04-12 20:24 GMT+02:00 Tomasz Torcz : >> On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: >>> The right (or, better) solution IMHO would be for mysqld to signal to >>> systemd that it's running OK before recovery starts,

Re: [systemd-devel] My experience with MySQL and systemctl

2017-04-12 20:24 GMT+02:00 Tomasz Torcz : > On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: >> The right (or, better) solution IMHO would be for mysqld to signal to >> systemd that it's running OK before recovery starts, using type=notify. >> This way recovery can

Re: [systemd-devel] My experience with MySQL and systemctl

On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote: > On 04/11/2017 06:08 AM, Lennart Poettering wrote: > > On Tue, 11.04.17 13:41, Samuel Williams (space.ship.travel...@gmail.com) > > wrote: > >> - If a daemon fails to start up, trying to kill it.. may not be the > >> best option. It's

Re: [systemd-devel] My experience with MySQL and systemctl

On 04/11/2017 06:08 AM, Lennart Poettering wrote: > On Tue, 11.04.17 13:41, Samuel Williams (space.ship.travel...@gmail.com) > wrote: >> - If a daemon fails to start up, trying to kill it.. may not be the >> best option. It's probably a matter of the systemctl service file >> detecting that a

Re: [systemd-devel] My experience with MySQL and systemctl

Am Tue, 11 Apr 2017 15:08:35 +0200 schrieb Lennart Poettering : > > Eventually, after checking all our backups, I decided to issue kill > > -9 to mysqld. I then decided to try restarting the daemon using > > systemctl. It did start up, the log output showed the crash

Re: [systemd-devel] My experience with MySQL and systemctl

On Tue, 11.04.17 13:41, Samuel Williams (space.ship.travel...@gmail.com) wrote: > I had an accident last night. I tried to delete a lot of rows from a > production database in one transaction. I killed the transaction, and > I didn't realise it was still rolling back an hour later when I tried >

[systemd-devel] My experience with MySQL and systemctl

I had an accident last night. I tried to delete a lot of rows from a production database in one transaction. I killed the transaction, and I didn't realise it was still rolling back an hour later when I tried to reboot the system for updates. I might be wrong about exactly who is doing what, but