Re: Changing systemd startup timeout

2018-05-16 Thread David Wright
On Wed 16 May 2018 at 14:09:43 (+0200), Sven Joachim wrote: > On 2018-05-16 06:04 -0500, Dave Sherohman wrote: > > > I'm running a galera cluster of three mariadb servers. It's been > > brought down twice because one node has detected an inconsistency, > > killed itself, and then systemd automati

Re: Changing systemd startup timeout

2018-05-16 Thread Dave Sherohman
On Wed, May 16, 2018 at 02:09:43PM +0200, Sven Joachim wrote: > Have you tried setting TimeoutStartSec rather than TimeoutStartUSec? > Though I have to admit that I did not perform a web search but cheated > by looking at the systemd.service(5) manpage, which mentions the former > but not the latte

Re: Changing systemd startup timeout

2018-05-16 Thread Curt
On 2018-05-16, Sven Joachim wrote: >> >> # systemctl edit mysql >> >> # systemctl show mysql -p TimeoutStartUSec >> TimeoutStartUSec=1min 30s >> # systemctl daemon-reload >> # systemctl show mysql -p TimeoutStartUSec >> TimeoutStartUSec=1min 30s >> # systemctl daemon-reexec >> # systemctl show my

Re: Changing systemd startup timeout

2018-05-16 Thread Sven Joachim
On 2018-05-16 06:04 -0500, Dave Sherohman wrote: > I'm running a galera cluster of three mariadb servers. It's been > brought down twice because one node has detected an inconsistency, > killed itself, and then systemd automatically restarted it. This is all > good so far. > > The problem comes

Changing systemd startup timeout

2018-05-16 Thread Dave Sherohman
Short version: How can I extend (or remove) the startup timeout for a single systemd service? Longer version: I'm running a galera cluster of three mariadb servers. It's been brought down twice because one node has detected an inconsistency, killed itself, and then systemd automatically restar