Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.4.17
-
None
-
Kubernetes using official maxscale docker.
Description
We have a kubernetes install of maxscale, its been rock solid for months and our of the blue, we are getting:
error : (8) (process_packets): Unexpected result state. cmd: 0x00, len: 120
error : (8) (process_packets): Unexpected result state. cmd: 0x00, len: 152
error : (8) (process_packets): Unexpected result state. cmd: 0x00, len: 40
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:213
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:43
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:99
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:106
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:68
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:97
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:55
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:100
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:116
warning: (8) (mxs_mysql_parse_ok_packet): recieved unexpecting session track type:115 (subsequent similar messages suppressed for 10000 milliseconds)
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
error : (8) (leint_value): Unexpected length encoding 'ff' encountered when reading length-encoded integer.
alert : (8) (sigfatal_handler): Fatal: MaxScale 2.4.17 received fatal signal 11. Commit ID: a8bfbbe254095d931aed351871fee72ce9ea645c System name: Linux Release string: CentOS Linux release 8.3.2011
I am trying to figure out where this error would even come from. The instance crashed and restarts, will run for a few minutes, and do it again.. Any help would be appreciated.