[MXS-2408] MaxScale 2.3.4 logs "Lost connection to the master server, closing session." although no network problem Created: 2019-03-25  Updated: 2020-08-25  Resolved: 2019-03-28

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

Type: Bug Priority: Major
Reporter: Claudio Nanni Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MXS-2410 Hangup delivered to wrong DCB Closed
Relates
relates to MXS-2860 MaxScale 2.3.16 logs "Lost connection... Closed

 Description   

2.3.4 with a plain R/W Split router logs:

2019-03-19 09:41:50 error : (244356) Lost connection to the master server, closing session. Lost connection to master server while waiting for a result. Connection has been idle for 0.0 seconds. Error caused by: #HY000: Lost connectio
 
2019-03-19 09:57:47 error : (244934) Lost connection to the master server, closing session. Lost connection to master server while waiting for a result. Connection has been idle for 0.0 seconds. Error caused by: #HY000: Lost connectio
 
2019-03-19 10:01:51 error : (245113) Lost connection to the master server, closing session. Lost connection to master server while waiting for a result. Connection has been idle for 0.0 seconds. Error caused by: #HY000: Lost connectio
 
2019-03-19 14:54:26 error : (256194) Lost connection to the master server, closing session. Lost connection to master server while waiting for a result. Connection has been idle for 0.0 seconds. Error caused by: #HY000: Lost connection

There are no network problems thou(or very much unlikely)

 Comments   
Comment by markus makela [ 2019-03-28 ]

I think this is caused by MXS-2410.

Comment by markus makela [ 2019-03-28 ]

I'll close this as a duplicate since MXS-2410 is likely to solve this problem.

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