[MXS-3221] MaxScale crashes (signal 6) in jsonp_malloc() Created: 2020-10-02  Updated: 2021-04-19  Resolved: 2021-01-07

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

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

Sprint: MXS-SPRINT-117

 Description   

Thew following crash happens:

...
2020-10-02 09:46:57   error  : (7) Write to Backend DCB X.Y.Z.T in state DCB_STATE_POLLING failed: 104, Connection reset by peer
*** Error in `/usr/bin/maxscale': corrupted double-linked list: 0x00007f851c0abdd0 ***
...
2020-10-02 09:46:58   alert  : Fatal: MaxScale 2.4.10 received fatal signal 6. Commit ID: 7781f7042ab077811e2431794c2280162c0a6a3d System name: Linux Release string: Red Hat Enterprise Linux Server release 7.8 (Maipo)
2020-10-02 09:46:59   alert  : 
  /lib64/libc.so.6(gsignal+0x37): :?
  /lib64/libc.so.6(abort+0x148): :?
  /lib64/libc.so.6(+0x78ed7): :?
  /lib64/libc.so.6(+0x7f3e4): malloc.c:?
  /lib64/libc.so.6(+0x82ba8): malloc.c:?
  /lib64/libc.so.6(__libc_malloc+0x4c): :?
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(jsonp_malloc+0x2a): ??:?
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(hashtable_init+0x44): ??:?
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(json_object+0x5c): ??:?
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN6Server22server_json_attributesEPKS_+0x23): server/core/server.cc:942
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0xf7bed): server/core/server.cc:1040
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0xf7db0): server/core/server.cc:1059
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN6Server19server_list_to_jsonEPKc+0xb4): server/core/server.cc:95
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0xdf418): server/core/resource.cc:560
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZNK8Resource4callERK11HttpRequest+0xa4): server/core/resource.cc:119
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0xe5fe9): server/core/resource.cc:1347 (discriminator 1)
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0xe770d): server/core/resource.cc:1387
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker14handle_messageERNS_12MessageQueueERKNS_19MessageQueueMessageE+0x6d): maxutils/maxbase/src/worker.cc:475
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase12MessageQueue18handle_poll_eventsEPNS_6WorkerEj+0x140): maxutils/maxbase/src/messagequeue.cc:306
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1a6): maxutils/maxbase/src/worker.cc:858
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
  /usr/local/maxscale/bin/../lib64/maxscale/libmaxscale-common.so.1.0.0(+0x1b830f): thread48.o:?
  /lib64/libpthread.so.0(+0x7ea5): pthread_create.c:?
  /lib64/libc.so.6(clone+0x6d): ??:?



 Comments   
Comment by markus makela [ 2020-10-14 ]

This could theoretically be a side-effect of MXS-3220.

Comment by markus makela [ 2020-10-19 ]

Should be verified whether this happens again once the fix to MXS-3220 has been released.

Comment by markus makela [ 2020-10-26 ]

Waiting for the results from the 2.4.13 release.

Comment by markus makela [ 2020-12-08 ]

Any updates regarding whether MXS-3220 fixed it?

Comment by markus makela [ 2021-01-07 ]

I'll close this as Cannot Reproduce since an upgrade to 2.4.14 seems to have solved it.

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