Bug #118517 Mysqlrouter 8.4.4 crashing with "Application got fatal signal: 6"

• Submitted: 24 Jun 12:19
• Modified: 10 Jul 15:45
• Reporter: Waseem Akram
• Status: Can't repeat
• Category: MySQL Router
• Severity: S3 (Non-critical)
• Version: 8.4.4
• OS: Linux
• Assigned to: MySQL Verification Team
• CPU Architecture: Any

[24 Jun 12:19] Waseem Akram

Description:
We are using MySQL router 8.4.4 version with 3 node innodb cluster, it is seen that mysql router getting crashed intermittently with below error.

terminate called after throwing an instance of 'mysqlrouter::URIError'
  what():  invalid URI: unexpected characters at position 1 for: /"><script>alert(document.domain)</script>.html
Application got fatal signal: 6
stack_bottom = 0 thread_stack 0x0
 #0 0x7f895da38f80 <unknown>
 #1 0x7f895e66498f <unknown>
 #2 0x7f895c30f52f <unknown>
 #3 0x7f895c2e2e64 <unknown>
 #4 0x7f895ccc109a <unknown>
 #5 0x7f895ccc754b <unknown>
 #6 0x7f895ccc75a6 <unknown>
 #7 0x7f895ccc785c <unknown>
 #8 0x7f895a532a05 <unknown>
 #9 0x7f895a55c45e <unknown>
 #10 0x7f895a55cca4 <unknown>
 #11 0x7f895a5298f6 <unknown>
 #12 0x7f895a52a135 <unknown>
 #13 0x7f895a529dcb <unknown>
 #14 0x7f895a52a64a <unknown>
 #15 0x7f895e9ea497 <unknown>
 #16 0x7f895e9ec608 <unknown>
 #17 0x7f895ccf3b22 <unknown>
 #18 0x7f895e65a1c9 <unknown>
 #19 0x7f895c2fa8d2 <unknown>
 #20 0xffffffffffffffff <unknown>

How to repeat:
setup 2 individual group replication cluster(assuming the nodes are in two data centers) and install mysql router in each primary node, both versions should be in 8.4.4 version.

Configure the router to connect cross DC primary node and setup replication b/w 2 clusters with master_host=127.0.0.1 and monitor router health.

[10 Jul 15:45] MySQL Verification Team

Hi,

I am not able to reproduce this. 

We had some issues with DNS that might be the reason for this (should be fixed in 8.4.6). Try adding your hosts in /etc/hosts and see if that solves the crashing issue.

[10 Jul 17:20] MySQL Verification Team

This could be also duplicate of Bug #117252 if you upgrade to 8.4.5 if that is the culprit you should be in the clear.