Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault during GTID configuration #2763

Closed
JavierJF opened this issue May 8, 2020 · 0 comments
Closed

Segfault during GTID configuration #2763

JavierJF opened this issue May 8, 2020 · 0 comments

Comments

@JavierJF
Copy link
Collaborator

JavierJF commented May 8, 2020

Description

A segfault is triggered when ProxySQL is configured for using GTID, can't connect connect to the specified 'ProxySQL binlog readers', and a new configuration for GTID is supplied to ProxySQL.

Version: Os and ProxySQL

Confirmed OSs:

Distributor ID: Ubuntu
Description:    Ubuntu 19.10
Release:        19.10
Codename:       eoan

NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster

ProxysSQL version:

ProxySQL version 2.0.12-11-gd1032d12_DEBUG, codename Truls

Steps to reproduce the isssue:

  1. Untar the provided tarball and cd into the tarball directory.
  2. Launch the provided proxysql binary with the command: ./proxysql -f -c proxysql.cnf
  3. Configure the running proxysql instance with the command: mysql -uadmin -padmin -h127.0.0.1 -P6032 < config.sql.
  4. The crash should have been triggered.

Error log:

error-log.txt

Crash tarball:

gtid-config-segfault.tar.gz

Contents

  • The coredump and the binary to reproduce the issue.
  • The full error log.
  • The current configuration necessary to reproduce the issue.
renecannao added a commit that referenced this issue May 11, 2020
Fix #2763: Segfault during GTID configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant