Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Cannot Reproduce
-
2.4.10
-
Debian 10 Buster
3 Maxscale Servers on top of 3 galera nodes.
-
MXS-SPRINT-113
Description
Maxscale unexpectedly segfaults with the following error, this appears to only happen on nodes that are not directly on the elected master node.
2020-07-07 09:30:01 alert : Fatal: MaxScale 2.4.10 received fatal signal 6. Commit ID: 7781f7042ab077811e2431794c2280162c0a6a3d System name: Linux Release string: undefined |
nm: /lib/x86_64-linux-gnu/libc.so.6: no symbols |
nm: /lib/x86_64-linux-gnu/libc.so.6: no symbols |
2020-07-07 09:30:01 alert : |
/lib/x86_64-linux-gnu/libc.so.6(epoll_wait+0x4f): ??:0 |
/usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0xd0): maxutils/maxbase/src/worker.cc:795 |
/usr/lib/x86_64-linux-gnu/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559 |
/usr/bin/maxscale(main+0x21fe): server/core/gateway.cc:2273 |
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb): ??:0 |
/usr/bin/maxscale(_start+0x2a): ??:? |
unfortunately this is so badly service affecting it requires us to jump to another load balancing solution but i thought I would leave this bug report with hopes that it gets a fix sooner rather than later.
Attachments
Issue Links
- relates to
-
-
- Closed
-