[MXS-2714] Binlogrouter crashes when starting with gtid position Created: 2019-10-04  Updated: 2020-09-23  Resolved: 2020-09-23

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

Type: Bug Priority: Major
Reporter: Maikel Punie Assignee: Niclas Antti
Resolution: Cannot Reproduce Votes: 1
Labels: None
Environment:

maxscale -V
MaxScale 2.4.2 - aad4148d77bf2dfbaa0042bc45abda30c101cad2
CMake flags: -DBUILD_TESTS=N -DBUILD_MMMON=Y -DBUILD_CDC=Y -DPACKAGE=Y -DDISTRIB_SUFFIX=centos.7
Jenkins build: jenkins-build-583
CentOS Linux release 7.6.1810 (Core)
Linux 3.10.0-957.21.3.el7.x86_64 #1 SMP Tue Jun 18 16:35:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


 Description   

SET @@global.gtid_slave_pos='0-1-35574476549';
CHANGE MASTER TO MASTER_HOST='10.255.10.32', MASTER_USER='repl', MASTER_PASSWORD='........', master_use_gtid=slave_pos, MASTER_PORT=3306;
start slave;

and then i see this in the logs

2019-10-04 09:49:43 notice : (10296644) [binlogrouter] BinLogSVC: START SLAVE executed by repl@::ffff:127.0.0.1. Trying connection to master [10.255.10.32]:3306, binlog , pos 267715550, transaction safe pos 267714990
2019-10-04 09:49:47 alert : Fatal: MaxScale 2.4.2 received fatal signal 6. Attempting backtrace.
2019-10-04 09:49:47 alert : Commit ID: aad4148d77bf2dfbaa0042bc45abda30c101cad2 System name: Linux Release string: CentOS Linux release 7.6.1810 (Core)
2019-10-04 09:49:48 alert : /lib64/libc.so.6(epoll_wait+0x33): :?
2019-10-04 09:49:48 alert : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0xd0): maxutils/maxbase/src/worker.cc:795
2019-10-04 09:49:48 alert : /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x53): maxutils/maxbase/src/worker.cc:559
2019-10-04 09:49:48 alert : /usr/bin/maxscale(main+0x2a76): server/core/gateway.cc:2267
2019-10-04 09:49:48 alert : /lib64/libc.so.6(__libc_start_main+0xf5): ??:?
2019-10-04 09:49:48 alert : /usr/bin/maxscale(): ??:?

 Comments   
Comment by markus makela [ 2019-10-04 ]

Looks like MaxScale was killed by the systemd watchdog. Does it work if you comment out the following lines from /lib/systemd/system/maxscale.service? 

WatchdogSec=60s
 
NotifyAccess=all

Comment by Maikel Punie [ 2019-10-14 ]

with this disabled i don't see the stacktrace anymore.

but maxscale is not starting to replicate from the provided gtid position ... it starts from another position.

Comment by Wagner Bianchi (Inactive) [ 2019-11-07 ]

Can you check if the position you set as a start point is there on downloaded binary logs?

Comment by Niclas Antti [ 2020-09-23 ]

The original issue, a systemd signal 6, was not related to binlogrouter.

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