[MXS-1415] Length (0) is 0 or query string allocation failed ((nil)). Buffer is 5 bytes. Created: 2017-09-14  Updated: 2017-09-27  Resolved: 2017-09-27

Status: Closed
Project: MariaDB MaxScale
Component/s: mmmon, readwritesplit
Affects Version/s: 1.4.5
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: kabilesh Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

OS :CentOS release 6.9 (Final)



 Description   

Hello Team,

Our maxscale log is getting over-flooded with the below error,

Error:
------
2017-09-14 04:43:22 error : Length (0) is 0 or query string allocation failed ((nil)). Buffer is 5 bytes.
2017-09-14 04:43:22 error : Unable to parse query, out of resources?
2017-09-14 04:43:22 error : Length (0) is 0 or query string allocation failed ((nil)). Buffer is 5 bytes.
2017-09-14 04:43:22 error : Unable to parse query, out of resources?

We are using version : maxscale-1.4.5-1.x86_64

We are using maxscale for RW splitting with master-master replication with one being active and other being Passive(Reads)

While checking Maxscale we could see queries being routed to respective node, kindly provide solution to fix the same

Thanks
Kabilesh



 Comments   
Comment by Johan Wikman [ 2017-09-14 ]

Can you pinpoint the query causing this?

If so, we might be able to suggest a workaround. It's not very likely that we would provide a new version for 1.4.

Comment by kabilesh [ 2017-09-14 ]

Hi John,

Am unable to get you the exact query, but i know the application is PHP based.

Can you suggest me some way to capture query from Maxscale, so that i could help you on query part.

Thanks
Kabilesh

Comment by Johan Wikman [ 2017-09-20 ]

Please add

log_info=1

to the MaxScale configuration file. That should cause the statement to be logged.

Note that this causes an excessive amount of logging, so do not enable it in a production environment.

Comment by Johan Wikman [ 2017-09-27 ]

Closing, as more information has not been provided.

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