[MXS-1577] Segmentation fault - MaxScale 2.1.10 received fatal signal 11 Created: 2017-12-13  Updated: 2018-01-16  Resolved: 2018-01-16

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

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

Debian 9.2.

Attachments: File avro.tar.gz     File mariadb-bin.000001.gz     File maxscale_fault.log.gz     File maxscale_fault_DDL.sql    
Sprint: 2017-49

 Description   

After some successful tests, today we found a possible issue with maxscale:

  • Maxscale stopped working while we were doing some inserts, deletes, updates on PartyPersonalDetails table (attached DDL) to test CDC events.
  • Then we looked at maxscale.log (attached), and saw that maxscale process died with an error like this, which seems a segmentation fault: 

    2017-12-11 11:29:54   alert  : Fatal: MaxScale 2.1.10 received fatal signal 11. Attempting backtrace.

If we restart maxscale service, it dies again with exactly the same error.

This is the kind of tests we were doing when the problem raised:

update PartyPersonalDetails set Gender = 'M' where PP_ID = 'AAAAA'

Attached also the binlog that's causing the error: mariadb-bin.000001.gz

Could you take a look, and advice any possible cause or solution?

 Comments   
Comment by Dipti Joshi (Inactive) [ 2017-12-13 ]

c.friaszapater Please download and use MaxScale 2.1.11

Regards,
Dipti

Comment by Carlos Frias [ 2017-12-13 ]

Hi @Dipti Joshi , is this bug fixed in MaxScale 2.1.11?

Comment by Carlos Frias [ 2017-12-14 ]

We upgraded MaxScale:

curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash
 
apt-get install --only-upgrade maxscale
 
maxscale --version
 
MaxScale 2.1.12

Then tried to restart maxscale, and the same error occurs on maxscale.log and terminates:
2017-12-14 11:08:26 alert : Fatal: MaxScale 2.1.12 received fatal signal 11. Attempting backtrace.

Comment by markus makela [ 2018-01-04 ]

With a fresh installation, the attached binlog file does not cause a crash and is successfully processed with 2.1.12.

If possible, stop MaxScale, remove the avro-conversion.ini and avro.index files as well as all .avro and .avsc files from the /var/lib/maxscale/ directories and then start MaxScale.

Comment by markus makela [ 2018-01-16 ]

c.friaszapater Please try this again with MaxScale 2.1.13. If it still fails, please open this issue again.

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