Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 09-17-2017 12:43 AM - edited 09-16-2022 05:15 AM
sqoop import - errors out
GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
WARN security.UserGroupInformation: PriviledgedActionException as:pars7611 (auth:KERBEROS) cause:java.io.IOException: Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)];
ERROR tool.ImportTool: Import failed: java.io.IOException: Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)];
sqoop eval runs good.
Created 09-17-2017 05:58 AM
Looks like you dont have any valid ticket , as you clusters is using kerberos .
Intialize a fresh ticket using KINIT
please follow the link that would walk through
https://sqoop.apache.org/docs/1.99.7/security/AuthenticationAndAuthorization.html
syntax kinit [email protected]
Created 09-17-2017 05:58 AM
Looks like you dont have any valid ticket , as you clusters is using kerberos .
Intialize a fresh ticket using KINIT
please follow the link that would walk through
https://sqoop.apache.org/docs/1.99.7/security/AuthenticationAndAuthorization.html
syntax kinit [email protected]
Created on 08-11-2018 01:03 PM - edited 08-11-2018 01:04 PM
I know this is old post, but for the benefit of others...
I was getting the same error while trying to execute sqoop commands (sqoop list command was working but not exec & show) directly on Edge node and I was able to resolve it by reconnecting to Edge node, it was open for long time may be session got expired.
For some reasons I restricted myself to use edge node not Hue-Oozie.