Navigate
or
Contact Us
Subscribe Download PDF

What does: "Debug_Code: 524, Message: mysql_version_len:15 greatlen:13..." in Query Error Log stand for?

Arun Sangameswaran
2017-11-13
0 Comments
in ScaleArc Registered User

  

What does: "Debug_Code: 524, Message: mysql_version_len:15 greatlen:13..." in Query Error Log stand for?

Release Classification Level DB Platform Categories
3.11.0.4 Message

MySQL Error Message 

 

QUESTION

Why do i see the following error messages in my 'Query Error Logs' and what do they mean?

 
2017-10-13 12:59:53
CID: 1, Client IP: 10.51.70.193, User: Unknown, Debug_Code: 524, Message: Client Greeting:0x3b, 0x00, 0x00, 0x00, 0x0a, 0x35, 0x2e, 0x37, 0x2e, 0x31, 0x38, 0x2d, 0x31, 0x36, 0x2d, 0x6c, 0x6f, 0x67, 0x00, 0xaf, 0x36, 0x02, 0x00, 0x36, 0x32, 0x32, 0x34, 0x30, 0x34, 0x39, 0x66, 0x00, 0xdf, 0xf7, 0x08, 0x02, 0x00, 0xe7, 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x64, 0x38, 0x66, 0x64, 0x33, 0x32, 0x35, 0x62, 0x30, 0x32, 0x32, 0x34, 0x00, 0xf2, 0x50, SSL: No , State: -1, SSID: 165115, DB: Unknown, DB IP: NONE, Type: 37
2017-10-13 12:59:53
CID: 1, Client IP: 10.51.70.193, User: Unknown, Debug_Code: 524, Message: Original Greeting:0x3d, 0x00, 0x00, 0x00, 0x0a, 0x35, 0x2e, 0x36, 0x2e, 0x33, 0x32, 0x2d, 0x37, 0x38, 0x2e, 0x30, 0x2d, 0x6c, 0x6f, 0x67, 0x00, 0x01, 0x00, 0x00, 0x00, 0x6b, 0x27, 0x7c, 0x5f, 0x46, 0x21, 0x70, 0x31, 0x00, 0xdf, 0xf7, 0x08, 0x02, 0x00, 0x67, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x43, 0x3f, 0x50, 0x53, 0x31, 0x38, 0x65, 0x74, 0x3a, 0x61, 0x5b, 0x27, 0x00, SSL: No , State: -1, SSID: 165115, DB: Unknown, DB IP: NONE, Type: 37
2017-10-13 12:59:53
CID: 1, Client IP: 10.51.70.193, User: Unknown, Debug_Code: 524, Message: mysql_version_len:15 greatlen:13 first_salt_pos:25 checkNUll:fffffff7 second_salt_pos:52 checkNull:50 server_capabilities:208f7df client_greeting_capabilities:e7000208 prev_ssid:165114 cur_ssid:165115 SSL: No , State: -1, SSID: 165115, DB: Unknown, DB IP: NONE, Type: 37

 

ANSWER
 
These errors appear in Query Erorr Logs in the event where you added two MySQL DBs with different versions with in a cluster one after the other. For instance, if you initially had a MySQL 5.6.13 which has a version length of 6 bytes and then later added a MySQL 5.7.136 to the same cluster which has a version length of 7 bytes.
ScaleArc uses a static variable to store this length at the startup when the very first client connection to ScaleArc is established (servergt). 
Now with the second dbserver in the cluster with new version length, though ScaleArc will modify the greeting with the newly generated value correctly, it will yet log the discrepancy in the error log.
 
That said, you may safely ignore these errors as they have no impact on any functionality. You may also opt to restart ScaleArc clusters once to suppress these errors.
These are also charted out and tracked for getting dynamically handled without logging in the future ScaleArc release.
 

  

If you are experiencing issues with ScaleArc or with any of its features, please contact ScaleArc Support. We are available 24x7 by phone at 855 800 7225 or +1 408 412 7315. For general support inquiries, you can also e-mail us at support@scalearc.com.

Copyright ©2017 ScaleArc, Inc. All rights reserved. Contact Support |  Contact ScaleArc |  Feedback

2901 Tasman Drive Santa Clara, CA 95054 | Email:  support@scalearc.com

 

 

 

 

 

 

 

Permalink: https://support.scalearc.com/kb/articles/4449