Centos 6.7

Can you upload the .avsc files that were generated? One possible cause for this might be a malformed schema definition.

Is there a way to anonymize tables definitions into avsc files ? I'm doing this setup with a production like database and I work in a financial company so unfortunately I won't have authorization to upload those informations.

Ah, I think validating the JSON in the .avsc files would be enough. The actual values aren't relevant as long as they conform to the Avro specification. You can use something like jq to validate it.

You can also enable the info log level to get some extra information about the binlog conversion process. If you spot a certain spot in the binlogs that causes this, it would be good to take a look at the binlogs at that point with mysqlbinlog. Since it crashes on startup, I'd assume it's the first binlog that is causing the problems.

You can also try and see what happens if you create a similar table, insert some data and start MaxScale without the generated .avsc files. This way MaxScale itself will generate the .avsc files from the CREATE TABLE statements in the binlogs and we can see if the problem is with the generated .avsc files or something else.

We've also made a few minor fixes for the next 2.0 release that could fix this bug. If you have the possibility of building MaxScale from the source, I'd recommend you try out the 2.0 branch on GitHub and see if this still happens.

JSON structure seems good for every .avsc files, I tried to open the first binlog but I get this message :

" mysqlbinlog: unknown variable 'default-character-set=utf8' "

It seems to be caused by the 'default-character-set=utf8' statement in my.cnf configuration, which is deprecated.
Is that blocking the binlog conversion process ?

I don't think that should prevent the binlogs from being processed.

Does the error log have any errors apart from the one that's already shown?

maxscale203_startup.log Here is the full startup log.

I opened the first binlog with these options " mysqlbinlog --no-defaults --base64-output=DECODE-ROWS mariadb-bin.000032 " and what we can see at pos 526 is :

# at 407

# at 460

#170109 14:23:24 server id 38  end_log_pos 460  Table_map: `bbdb`.`_partition` mapped to number 100

#170109 14:23:24 server id 38  end_log_pos 526  Update_rows: table id 100 flags: STMT_END_F

# at 526

#170109 14:23:24 server id 38  end_log_pos 553  Xid = 63945799

COMMIT/*!*/;

# at 553

#170109 14:23:24 server id 38  end_log_pos 591  GTID 0-38-45226

/*!100001 SET @@session.gtid_seq_no=45226*//*!*/;

BEGIN

/*!*/;

# at 591

I tried to build from source in order to test fixes from 2.0.4 but it fail during 'make test' command on the last test (binlogrouter).

We've pushed a fix to the test failure in the 2.0 branch on GitHub. The test should pass now as it was a simple configuration error in the test declaration.

I tried with version 2.0.4 and still can't start Maxscale, I have the same log :

2017-02-01 11:53:01 error : Failed to initialize avrofile.
2017-02-01 11:53:01 error : Fatal: MaxScale 2.0.4 received fatal signal 11. Attempting backtrace.
2017-02-01 11:53:01 error : Commit ID: a8780b892498f0a4df03ab8c09625603874582d5 System name: Linux Release string: CentOS release 6.7 (Final)
2017-02-01 11:53:01 error : /usr/bin/maxscale() [0x403b9c]
2017-02-01 11:53:01 error : /lib64/libpthread.so.0(+0xf7e0) [0x7feb226de7e0]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(maxavro_file_open+0x25f) [0x7feb1d298395]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(avro_index_file+0x29) [0x7feb1d2623c0]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(avro_update_index+0x97) [0x7feb1d2628e3]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(avro_flush_all_tables+0x90) [0x7feb1d261bbb]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(avro_read_all_events+0xb06) [0x7feb1d26163b]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libavrorouter.so(converter_func+0x69) [0x7feb1d258c00]
2017-02-01 11:53:01 error : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x40ad2) [0x7feb22fefad2]
2017-02-01 11:53:01 error : /lib64/libpthread.so.0(+0x7aa1) [0x7feb226d6aa1]
2017-02-01 11:53:01 error : /lib64/libc.so.6(clone+0x6d) [0x7feb2125caad]
2017-02-01 11:53:01 info : Starting log flushing to disk.

I tried with an other binlog start index, I always have this error.