[MXS-4363] maxscale signal 6 crash after killed by watchdog timeout Created: 2022-10-25  Updated: 2022-11-11  Resolved: 2022-10-27

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

Type: Bug Priority: Major
Reporter: Paul Moen Assignee: Unassigned
Resolution: Not a Bug Votes: 1
Labels: None
Environment:

Red Hat Enterprise Linux release 8.6 (Ootpa), AWS


 Description   

maxscale crashed.

Stack trace

2022-10-24 13:35:05   alert  : MaxScale 6.4.1 received fatal signal 6. Commit ID: 8ac5dcd8c87e10d79993a7db11987f4bb4c845e7 System 
name: Linux Release string: Red Hat Enterprise Linux release 8.6 (Ootpa)
 
2022-10-24 13:35:05   alert  : Statement currently being classified: none/unknown
 
2022-10-24 13:35:05   notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] sec
 
tion.
 
  /lib64/libpthread.so.0(+0x10d96): ??:?
 
  /lib64/libpthread.so.0(+0x10e88): ??:?
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN8maxscale13RoutingWorker20execute_concurrentlyERKSt8functionIFvvEE+0x52): max
 
utils/maxbase/include/maxbase/semaphore.hh:146
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x1b88c3): /usr/include/c++/8/bits/std_function.h:256
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker14handle_messageERNS_12MessageQueueERKNS_19MessageQueueMessage
 
E+0xa9): maxutils/maxbase/src/worker.cc:474
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase12MessageQueue18handle_poll_eventsEPNS_6WorkerEj+0x98): maxutils/maxb
 
ase/src/messagequeue.cc:307
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x219): maxutils/maxbase/src/worker.cc:857
 
  /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x4f): maxutils/maxbase/src/worker.cc:558
 
  /usr/bin/maxscale(main+0x1f8a): server/core/gateway.cc:2240
 
  /lib64/libc.so.6(__libc_start_main+0xf3): ??:?
 
  /usr/bin/maxscale(_start+0x2e): ??:?
 
alert  : Writing core dump.



 Comments   
Comment by Bryan Bancroft (Inactive) [ 2022-10-25 ]

markus makela

Grants are wildcard or ip

user@%
 
or
 
user@10.1.0.180

skip_name_resolve is on

+-------------------+-------+
 
| Variable_name     | Value |
 
+-------------------+-------+
 
| skip_name_resolve | ON    |
 
+-------------------+-------+
 
1 row in set (0.001 sec)

Comment by Bryan Bancroft (Inactive) [ 2022-10-27 ]

markus makela This was a 1 time event as of now and has not reoccurred.

I think we can resolve this and reopen should an issue crop back up

Comment by markus makela [ 2022-10-27 ]

Closing as Not a Bug as it hasn't occurred before and based on all the evidence it was a DNS related issue.

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