Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
23.08.4
-
None
-
DEV
Description
Hello,
We recently upgraded from maxscale 6.4 to 23.08.
Since then, we notice in the maxscale logfile error like these :
2024-01-23 11:29:07 error : (2039) (IM46130D-Service); Lost connection to backend server: Network error: 104, Connection reset by peer (IM46130D1, session=2039, conn_id=4531072)
2024-01-23 11:29:26 error : (2062) (IM46130D-Service); Lost connection to backend server: Network error: 104, Connection reset by peer (IM46130D1, session=2062, conn_id=4531091)
2024-01-23 11:29:38 error : (2071) (IM46130D-Service); Lost connection to backend server: Network error: 104, Connection reset by peer (IM46130D1, session=2071, conn_id=4531101)
It seems whenever a connection reaches interactive_timeout it is then reported as an error in the log file (I can see it clearly by doing some "list sessions", when 600s reached --> reported as error). I've tried to set connection_keepalive=30s to the service in maxscale config file but it does not help.
On the backend mariadb :
interactive_timeout=600
wait_timeout=600
Service in maxscale :
[IM46130D-Service]
type=service
router=readconnroute
router_options=master
servers=IM46130D1,IM46130D2
user=xxx
password=xxx
connection_keepalive=30s
I've found a similar issue saying it is fixed but I'm still having the problem. Here :
https://jira.mariadb.org/browse/MXS-4440
Could you have a look?
Thank you
Attachments
Issue Links
- relates to
-
MXS-4440 Lost connection to backend server: network error (server1: 104, Connection reset by peer)
- Closed