ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17447) Datanode start fails with umask 027 on ambari-server node
Date Mon, 27 Jun 2016 12:45:52 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-17447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Onischuk updated AMBARI-17447:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.4

> Datanode start fails with umask 027 on ambari-server node
> ---------------------------------------------------------
>
>                 Key: AMBARI-17447
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17447
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17447.patch
>
>
> This happens because of incorrect permissions set for jdk jce security files.
>     
>     
>     2016-06-27 09:56:41,335 ERROR datanode.DataNode (DataNode.java:secureMain(2633))
- Exception in secureMain
>     java.lang.ExceptionInInitializerError
>     	at javax.crypto.KeyGenerator.nextSpi(KeyGenerator.java:340)
>     	at javax.crypto.KeyGenerator.<init>(KeyGenerator.java:168)
>     	at javax.crypto.KeyGenerator.getInstance(KeyGenerator.java:223)
>     	at org.apache.hadoop.security.token.SecretManager.<init>(SecretManager.java:143)
>     	at org.apache.hadoop.hdfs.security.token.block.BlockPoolTokenSecretManager.<init>(BlockPoolTokenSecretManager.java:36)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.startDataNode(DataNode.java:1228)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.<init>(DataNode.java:449)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2511)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2398)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2445)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2626)
>     	at org.apache.hadoop.hdfs.server.datanode.DataNode.main(DataNode.java:2650)
>     Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
>     	at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:89)
>     	... 12 more
>     Caused by: java.security.PrivilegedActionException: java.io.FileNotFoundException:
/usr/jdk64/jdk1.8.0_60/jre/lib/security/US_export_policy.jar (Permission denied)
>     	at java.security.AccessController.doPrivileged(Native Method)
>     	at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:78)
>     	... 12 more
>     Caused by: java.io.FileNotFoundException: /usr/jdk64/jdk1.8.0_60/jre/lib/security/US_export_policy.jar
(Permission denied)
>     	at java.util.zip.ZipFile.open(Native Method)
>     	at java.util.zip.ZipFile.<init>(ZipFile.java:219)
>     	at java.util.zip.ZipFile.<init>(ZipFile.java:149)
>     	at java.util.jar.JarFile.<init>(JarFile.java:166)
>     	at java.util.jar.JarFile.<init>(JarFile.java:130)
>     	at javax.crypto.JceSecurity.loadPolicies(JceSecurity.java:293)
>     	at javax.crypto.JceSecurity.setupJurisdictionPolicies(JceSecurity.java:263)
>     	at javax.crypto.JceSecurity.access$000(JceSecurity.java:48)
>     	at javax.crypto.JceSecurity$1.run(JceSecurity.java:81)
>     	... 14 more
>     2016-06-27 09:56:41,338 INFO  util.ExitUtil (ExitUtil.java:terminate(124)) - Exiting
with status 1
>     2016-06-27 09:56:41,339 INFO  datanode.DataNode (LogAdapter.java:info(47)) - SHUTDOWN_MSG:

>     



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message