[MXS-4488] MaxScale can hang if non-MariaDB data is sent to a MariaDB protocol port Created: 2023-01-25  Updated: 2023-04-17  Resolved: 2023-01-25

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 22.08.4
Fix Version/s: 22.08.5

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Problem/Incident
causes MXS-4402 MaxScale 22.08 received fatal signal 6 Closed

 Description   

The following test reproduces the problem:

#!/usr/bin/env python3                                                                                                                                                                                                                                                                    
 
 
import socket
 
import time
 
 
 
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
 
s.connect(("127.0.0.1", 4006))
 
 
 
for i in range(0, 2000):
 
  s.send(bytes([0xff, 0xff, 0xff, 0]))
 
 
 
time.sleep(1000)

This can potentially happen when something does a health check on the MaxScale port that doesn't use the MariaDB protocol to do it.
Generated at Thu Feb 08 04:29:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.