[MXS-2095] Fatal: MaxScale 2.2.15 received fatal signal 11 - libavrorouter.so(count_columns+0x21) Created: 2018-10-11  Updated: 2020-08-25  Resolved: 2018-11-13

Status: Closed
Project: MariaDB MaxScale
Component/s: avrorouter
Affects Version/s: 2.2.15
Fix Version/s: 2.2.17

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-1536 Fatal: MaxScale 2.1.10 received fatal... Closed
Sprint: MXS-SPRINT-69

 Description   

A user saw the following crash:

2018-10-11 19:44:36   info   : (4) [binlogrouter] Fake ROTATE_EVENT received: binlog file mariadb-bin.000001, pos 5474388
2018-10-11 19:44:37   alert  : Fatal: MaxScale 2.2.15 received fatal signal 11. Attempting backtrace.
2018-10-11 19:44:37   alert  : Commit ID: 62ce6c15dcd45be035ff6a005ca5539ca3d2adc8 System name: Linux Release string: NAME="CentOS Linux"
2018-10-11 19:44:37   alert  :   /usr/bin/maxscale() [0x407ea1]: ??:0
2018-10-11 19:44:37   alert  :   /lib64/libpthread.so.0(+0xf6d0) [0x7f2b50fb36d0]: sigaction.c:?
2018-10-11 19:44:37   alert  :   /lib64/libc.so.6(+0x13e6a8) [0x7f2b4efcc6a8]: :?
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libavrorouter.so(count_columns+0x21) [0x7f2b4bbe04d1]: /home/vagrant/MaxScale/server/modules/routing/avrorouter/avro_schema.c:606 (discriminator 1)
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libavrorouter.so(table_create_alloc+0xe8) [0x7f2b4bbe06e8]: /home/vagrant/MaxScale/server/modules/routing/avrorouter/avro_schema.c:623
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libavrorouter.so(handle_query_event+0x486) [0x7f2b4bbe5436]: /home/vagrant/MaxScale/server/modules/routing/avrorouter/avro_file.c:1154
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libavrorouter.so(avro_read_all_events+0x7ad) [0x7f2b4bbe5c4d]: /home/vagrant/MaxScale/server/modules/routing/avrorouter/avro_file.c:766
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libavrorouter.so(converter_func+0x98) [0x7f2b4bbdc388]: /home/vagrant/MaxScale/server/modules/routing/avrorouter/avro.c:1215
2018-10-11 19:44:37   alert  :   /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x5e994) [0x7f2b51490994]: /home/vagrant/MaxScale/server/core/housekeeper.cc:262
2018-10-11 19:44:37   alert  :   /lib64/libpthread.so.0(+0x7e25) [0x7f2b50fabe25]: pthread_create.c:?
2018-10-11 19:44:37   alert  :   /lib64/libc.so.6(clone+0x6d) [0x7f2b4ef8cbad]: ??:?
2018-10-11 19:44:37   info   : Starting log flushing to disk.



 Comments   
Comment by markus makela [ 2018-11-08 ]

It turns out that a statement was mistakenly classifier as a CREATE TABLE statement which caused the crash.

Comment by markus makela [ 2018-11-08 ]

Build pre-release packages with a fix to this: http://max-tst-01.mariadb.com/ci-repository/MXS-2.2-markusjm-nov8/mariadb-maxscale/

NOTE: these packages are only intended for testing and are not for production use.

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