kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Heo <jason.heo....@gmail.com>
Subject I got an "authentication token expired" error.
Date Wed, 14 Jun 2017 09:44:33 GMT
Hi.

I'm using Apache Kudu 1.4.0.

And I have a long running Java Daemon which is a kudu client at the same
time.

Today (7 days has been past since the Java Daemon has been started) I
suddenly got an following error.


W0614 15:29:11.934401 62459 negotiation.cc:310] Unauthorized connection
attempt: Server connection negotiation failed: server connection from
ip_addr:56604: authentication token expired

W0614 15:29:11.956845 62459 negotiation.cc:310] Unauthorized connection
attempt: Server connection negotiation failed: server connection from
ip_addr:56606: authentication token expired

...

...

...

W0614 17:47:18.347970 74099 negotiation.cc:310] Unauthorized connection
attempt: Server connection negotiation failed: server connection from
ip_addr:56172: authentication token expired

W0614 17:47:20.488306 74100 negotiation.cc:310] Unauthorized connection
attempt: Server connection negotiation failed: server connection from
ip_addr:56180: authentication token expired



Kudu is started with this options

--unlock_experimental_flags=true

...

--superuser_acl=user1,user2

The Java Daemon is started with user2 account.

How can I prevent from happening this error again.

I've read this manual.
https://kudu.apache.org/docs/security.html#known-limitations

It says that "so long-lived clients in secure clusters are not supported"
Then Should I set `--rpc-authentication=disable`?

Thanks.

Regards,

Jason

Mime
View raw message