Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.2.1
-
Fix Version/s: 1.3.0
-
Component/s: Core
-
Labels:None
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.
Attachments
Issue Links
- relates to
-
MXS-35 bugzillaId-451: maxscale main() exit code is always 0 after it daemonizes
-
- Closed
-