[MXS-3651] Xpandmon: Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-3 Created: 2021-07-01  Updated: 2021-07-14  Resolved: 2021-07-14

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

Type: Bug Priority: Major
Reporter: Manjinder Nijjar Assignee: markus makela
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MXS-3578 Unexpected result state when using co... Closed
Relates
relates to MXS-3248 "error : (1672) Unexpected result st... Closed
Sprint: MXS-SPRINT-136

 Description   

We found this error in MaxScale logs while running xpand parallel replication via MaxScale. This looks simillar to MXS-3248 but it does not appear fixed for xpandmon.

[root@karma075 ~]# maxscale -version
 
MaxScale 2.5.13

Error:

2021-06-30 15:23:58   error  : (7) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-3
 
2021-06-30 15:23:58   error  : (6) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-5
 
2021-06-30 15:23:58   error  : (11) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-2
 
2021-06-30 15:23:58   error  : (13) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-1
 
2021-06-30 15:23:58   error  : (2) Unexpected result state. cmd: 0x00, len: 107 server: @@XpandMonitor:node-3
 
2021-06-30 15:23:58   error  : (2) Unexpected result state. cmd: 0x00, len: 28 server: @@XpandMonitor:node-3

As mentioned in MXS-3248, this error does not appear when we add connection_keepalive=0s to the readconroute service in maxscale.cnf.

 Comments   
Comment by Johan Wikman [ 2021-07-01 ]

Which router are you using? This can't really be related to the xpand monitor, but must be a router issue.

Comment by Manjinder Nijjar [ 2021-07-01 ]

johan.wikman I am using readconnroute.

Comment by Johan Wikman [ 2021-07-02 ]

msnijjar Sorry, I failed to notice that you mentioned readconnroute in the original description.

If setting connection_keepalive=0s removes the error, it suggests that there is a bug in the implementation of the connection keepalive.

https://mariadb.com/kb/en/mariadb-maxscale-25-mariadb-maxscale-configuration-guide/#connection_keepalive

In your case setting it to 0 should be fine.

Comment by markus makela [ 2021-07-14 ]

I think this is a duplicate of MXS-3578.

Comment by markus makela [ 2021-07-14 ]

I'll close this as a duplicate of MXS-3578. Once the 2.5.14 release is out, you can test if this indeed was the same bug (highly likely that it is).

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