Articles in this section

FAQ: Why can a user log in with aql but not asadm?

Detail

Why can a user log in successfully with password authentication using aql, but asadm with the same username and password fails with an error similar to
ERROR: Not able to connect any cluster with [('127.0.0.1', 3000, None)].
?

Answer

The password contains a Unicode or UTF-8 character. Different Aerospike tools, written in different languages, will handle such characters differently, so we do not recommend using them in passwords for Aerospike.

Notes

If audit logging is enabled on the Aerospike server, no connection from asadm will be shown (the illegal character causes processing to fail before the connection to the server is made).

Applies To Earliest Version

Pre 4.9

Applies To Latest Version

Current Version
Was this article helpful?
0 out of 0 found this helpful