[MXS-491] MaxScale can time out systemd if startup of services takes too long Created: 2015-11-25  Updated: 2015-11-26  Resolved: 2015-11-26

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.2.1
Fix Version/s: 1.3.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-35 bugzillaId-451: maxscale main() exit ... Closed

 Description   

This relates to the fix to MXS-35 which makes MaxScale wait until it has daemonized itself and that all services have been started before exiting. This causes a problem if the startup takes longer than the default timeout of 90 seconds.

Either a timeout in the maxscale.service file needs to be added or a way to start MaxScale without waiting for the services to start needs to be added. The preferred option would be to increase the timeout in maxscale.service.

 Comments   
Comment by markus makela [ 2015-11-26 ]

Increased the timeout of the maxscale.service file to 120 seconds. This can be further increased by the user if 120 seconds is not enough.

Generated at Thu Feb 08 03:59:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.