[
https://issues.apache.org/jira/browse/HDFS-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117393#comment-13117393
]
Arpit Gupta commented on HDFS-2387:
-----------------------------------
Seems to log the same exception in the namenode as when fsck call did not work
2011-09-29 16:11:02,873 WARN org.mortbay.log: EXCEPTION
javax.net.ssl.SSLHandshakeException: Invalid padding
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1699)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:852)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1165)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1149)
at
org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:708)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: javax.crypto.BadPaddingException: Padding length invalid: 48
at
com.sun.net.ssl.internal.ssl.CipherBox.removePadding(CipherBox.java:399)
at com.sun.net.ssl.internal.ssl.CipherBox.decrypt(CipherBox.java:247)
at
com.sun.net.ssl.internal.ssl.InputRecord.decrypt(InputRecord.java:153)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:840)
> hftp fails as it is not able to get delegation token over https
> ---------------------------------------------------------------
>
> Key: HDFS-2387
> URL: https://issues.apache.org/jira/browse/HDFS-2387
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.205.0
> Reporter: Arpit Gupta
>
> Run a dfs command with the path specified as hftp leads to the following issue
> bash-3.2$ /bin/hadoop --config HADOOP_CONF_DIR dfs -ls
> hftp://NN_HOST:50070/path
> 11/09/29 16:07:23 INFO fs.FileSystem: Couldn't get a delegation token from
> https://NN_HOST:50470 using https.
> ls: Security enabled but user not authenticated by filter
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
