New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MySQL function SHA2 does not exist #5189
Comments
|
What's your CentOS version? |
|
Cent0S release 6.10 (Final) |
|
What SQL product are you using and it's version? |
|
You need to update to 5.5.6 or later. |
|
What about doing the crypt in code rather than the DB. |
@LiamKarlMitchell he can simply leave out the hashing or change the sql command. It was just added because there were security concerns for only using UUID. Basically doing it in code would drag some big dependencies into rAthena, which we want to prevent if we can. |
I also have this same problem. I use MD5 encoding, can that be? I use Cent0S release 6.10 (Final). Do I need to update? |
might be compatible problem for mysql that installed on your centos.i haven't tried to update mine since it was work fine before the web_auth_token implementation. |
|
I will update my mysql and check if it will resolve. EDIT: Solved after mysql update. Thank you |
Fixes #5189 Thanks to @bgamez23 and @Badarosk0
|
I have the same error , I can log in the game but I can't cast skills, can someone help. |


Description of Issue: i got this error [SQL]: DB error - FUNCTION ragnarok.SHA2 does not exist on centos but does not exist in windows server.
Result: [SQL]: DB error - FUNCTION ragnarok.SHA2 does not exist
[Debug]: at account.cpp:664 - UPDATE
loginSETweb_auth_token= LEFT( SHA2( CONCAT( UUID(), RAND() ), 256 ), 16 ),web_auth_token_enabled= '1' WHEREaccount_id= '2000000'. it also happens on another account who login the game.Expected Result:
How to Reproduce: i don't know how to produce since it only appears when i login my character.
Official Information:
Modifications that may affect results: pre-renewal setup server and vip enabled
The text was updated successfully, but these errors were encountered: