-
Notifications
You must be signed in to change notification settings - Fork 22
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
Fix hadoop calls for non-existent users #172
Comments
thomasdupas
added a commit
to thomasdupas/entrada
that referenced
this issue
Mar 11, 2022
* if the user you're running as doesn't exist in passwd/nss the hadoop calls failed with "Caused by: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name"
thomasdupas
added a commit
to thomasdupas/entrada
that referenced
this issue
Mar 14, 2022
* if the user you're running as doesn't exist in passwd/nss the hadoop calls failed with "Caused by: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name"
thomasdupas
added a commit
to thomasdupas/entrada
that referenced
this issue
Mar 14, 2022
* if the user you're running as doesn't exist in passwd/nss the hadoop calls failed with "Caused by: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name"
thomasdupas
added a commit
to thomasdupas/entrada
that referenced
this issue
Mar 14, 2022
* if the user you're running as doesn't exist in passwd/nss the hadoop calls failed with "Caused by: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if the user you're running as doesn't exist in passwd/nss the hadoop calls failed with "Caused by: javax.security.auth.login.LoginException: java.lang.NullPointerException: invalid null input: name"
Quite common for example when running it on kubernetes with a non-overlapping high UID per security recommendations
The text was updated successfully, but these errors were encountered: