Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.2.2
-
None
Description
The Maxscale service crashes on start-up on a fresh CentOS 7 host.
The latest version of Maxscale 2.2.2 has been Downloaded as RPM and installed through Yum on a freshly provisioned CentOS 7 host with the following error(s):
2018-03-06 14:35:55 error : Could not create pipe for worker: Invalid argument
2018-03-06 14:35:55 error : Could not create message queue for worker.
2018-03-06 14:35:55 error : Failed to initialize workers.
2018-03-06 14:35:55 info : Starting log flushing to disk.
2018-03-06 14:35:56 alert : Fatal: MaxScale 2.2.2 received fatal signal 11. Attempting backtrace.
2018-03-06 14:35:56 alert : Commit ID: d1465e03c3eef6c8758a80ac30d84f75307a6cbd System name: Linux Release string: CentOS Linux release 7.3.1611 (Core)
2018-03-06 14:35:56 alert : /usr/bin/maxscale() [0x4079d1]: ??:0
2018-03-06 14:35:56 alert : /lib64/libpthread.so.0(+0xf370) [0x7f2c3fd99370]: sigaction.c:?
2018-03-06 14:35:56 alert : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN8maxscale6Worker12shutdown_allEv+0x22) [0x7f2c402aa822]: /home/ec2-user/MaxScale/server/core/worker.cc:939 (discriminator 2)
2018-03-06 14:35:56 alert : /usr/bin/maxscale(maxscale_shutdown+0x22) [0x407e42]: /home/ec2-user/MaxScale/server/core/gateway.cc:2354
2018-03-06 14:35:56 alert : /usr/bin/maxscale() [0x407eef]: ??:0
2018-03-06 14:35:56 alert : /lib64/libpthread.so.0(+0xf370) [0x7f2c3fd99370]: sigaction.c:?
2018-03-06 14:35:56 alert : /lib64/libpthread.so.0(write+0x2d) [0x7f2c3fd9843d]: :?
2018-03-06 14:35:56 alert : /usr/bin/maxscale(_Z21write_child_exit_codeii+0x1a) [0x408ada]: /home/ec2-user/MaxScale/server/core/gateway.cc:2970
2018-03-06 14:35:56 alert : /usr/bin/maxscale(main+0xadc) [0x404e7c]: /home/ec2-user/MaxScale/server/core/gateway.cc:2328
2018-03-06 14:35:56 alert : /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f2c3dc9fb35]: ??:?
2018-03-06 14:35:56 alert : /usr/bin/maxscale() [0x4069f5]: ??:0
2018-03-06 14:35:56 info : Starting log flushing to disk.
This happens both with the default config template and with our custom settings.