[MXS-4072] signal 6 Created: 2022-03-31  Updated: 2022-05-23  Resolved: 2022-05-23

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 2.4.19
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Massimo Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

centos 7

Sprint: MXS-SPRINT-157

 Description   

we have a crash

2022-03-31 08:48:10 notice : Updated 'passive' from 'true' to 'false'
2022-03-31 08:48:49 alert : Fatal: MaxScale 2.4.19 received fatal signal 6. Commit ID: 0a83e64a9c47157074e22a101b2e431b0c7e64fe System name: Linux Release string: NAME="CentOS Linux"
2022-03-31 08:48:49 alert : Statement currently being classified: none/unknown
2022-03-31 08:48:50 alert :
/lib64/libc.so.6(epoll_wait+0x33): :?
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0xd0): maxutils/maxbase/src/worker.cc:795
/usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
/usr/bin/maxscale(main+0x2975): server/core/gateway.cc:2336
/lib64/libc.so.6(__libc_start_main+0xf5): ??:?
/usr/bin/maxscale(): ??:?

 Comments   
Comment by markus makela [ 2022-04-24 ]

This is most likely caused by slowdowns in other parts of the system that cause something in MaxScale to take too long.

Generated at Thu Feb 08 04:26:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.