When I take a thread dump, I see this thread probably hung. Has anybody 
reported an issue related to SecureRandom?

"init" #17 prio=5 os_prio=0 cpu=137.55ms elapsed=56.86s tid=0x0000558cd1870800 
nid=0x34 runnable  [0x00007fbc59aa7000]
   java.lang.Thread.State: RUNNABLE
        at 
sun.security.pkcs11.Secmod.nssInitialize(jdk.crypto.cryptoki@11.0.17/Native 
Method)
        at 
sun.security.pkcs11.Secmod.initialize(jdk.crypto.cryptoki@11.0.17/Secmod.java:239)
        - locked <0x00000000f88f2928> (a sun.security.pkcs11.Secmod)
        at 
sun.security.pkcs11.SunPKCS11.<init>(jdk.crypto.cryptoki@11.0.17/SunPKCS11.java:243)
        at 
sun.security.pkcs11.SunPKCS11$1.run(jdk.crypto.cryptoki@11.0.17/SunPKCS11.java:143)
        at 
sun.security.pkcs11.SunPKCS11$1.run(jdk.crypto.cryptoki@11.0.17/SunPKCS11.java:140)
        at java.security.AccessController.doPrivileged(java.base@11.0.17/Native 
Method)
        at 
sun.security.pkcs11.SunPKCS11.configure(jdk.crypto.cryptoki@11.0.17/SunPKCS11.java:140)
        at 
sun.security.jca.ProviderConfig$3.run(java.base@11.0.17/ProviderConfig.java:251)
        at 
sun.security.jca.ProviderConfig$3.run(java.base@11.0.17/ProviderConfig.java:242)
        at java.security.AccessController.doPrivileged(java.base@11.0.17/Native 
Method)
        at 
sun.security.jca.ProviderConfig.doLoadProvider(java.base@11.0.17/ProviderConfig.java:242)
        at 
sun.security.jca.ProviderConfig.getProvider(java.base@11.0.17/ProviderConfig.java:222)
        - locked <0x00000000f889aac0> (a sun.security.jca.ProviderConfig)
        at 
sun.security.jca.ProviderList.getProvider(java.base@11.0.17/ProviderList.java:266)
        at 
sun.security.jca.ProviderList$3.get(java.base@11.0.17/ProviderList.java:156)
        at 
sun.security.jca.ProviderList$3.get(java.base@11.0.17/ProviderList.java:151)
        at 
java.util.AbstractList$Itr.next(java.base@11.0.17/AbstractList.java:371)
        at 
java.security.SecureRandom.getDefaultPRNG(java.base@11.0.17/SecureRandom.java:264)
        at 
java.security.SecureRandom.<init>(java.base@11.0.17/SecureRandom.java:219)
        at org.apache.accumulo.core.util.Retry.<clinit>(Retry.java:49)
        at 
org.apache.accumulo.core.fate.zookeeper.ZooReader.<clinit>(ZooReader.java:46)
        at 
org.apache.accumulo.server.init.Initialize.execute(Initialize.java:532)
        at org.apache.accumulo.start.Main.lambda$execKeyword$0(Main.java:122)
        at 
org.apache.accumulo.start.Main$$Lambda$145/0x00000008401af040.run(Unknown 
Source)
        at java.lang.Thread.run(java.base@11.0.17/Thread.java:829)

________________________________
From: Samudrala, Ranganath [USA] via user <user@accumulo.apache.org>
Sent: Tuesday, January 10, 2023 9:21 AM
To: user@accumulo.apache.org <user@accumulo.apache.org>
Subject: [External] accumulo init error in K8S

Hello,
I am trying to configure Accumulo in K8S using Helm chart. Hadoop and Zookeeper 
are up and running in the same K8S namespace.
accumulo.properties is as below:

  
instance.volumes=hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/data0/accumulo
  general.custom.volume.preferred.default=accumulo
  instance.zookeeper.host=accumulo-zookeeper
  # instance.secret=DEFAULT
  general.volume.chooser=org.apache.accumulo.core.spi.fs.PreferredVolumeChooser
  
general.custom.volume.preferred.logger=hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/data0/accumulo
  trace.user=tracer
  trace.password=tracer
  instance.secret=accumulo
  tserver.cache.data.size=15M
  tserver.cache.index.size=40M
  tserver.memory.maps.max=128M
  tserver.memory.maps.native.enabled=true
  tserver.sort.buffer.size=50M
  tserver.total.mutation.queue.max=16M
  tserver.walog.max.size=128M

accumulo-client.properties is as below:

 auth.type=password
 auth.principal=root
 auth.token=root
 instance.name=accumulo
 # For Accumulo >=2.0.0
 instance.zookeepers=accumulo-zookeeper
 instance.zookeeper.host=accumulo-zookeeper

When I run 'accumulo init --add-volumes', I see an error as below and what is 
wrong with the setup?

java.lang.RuntimeException: None of the configured paths are initialized.
        at 
org.apache.accumulo.server.ServerDirs.checkBaseUris(ServerDirs.java:119)
        at 
org.apache.accumulo.server.init.Initialize.addVolumes(Initialize.java:449)
        at 
org.apache.accumulo.server.init.Initialize.execute(Initialize.java:543)
        at org.apache.accumulo.start.Main.lambda$execKeyword$0(Main.java:122)
        at java.base/java.lang.Thread.run(Thread.java:829)
2023-01-09T21:22:13,530 [init] [org.apache.accumulo.start.Main] ERROR: Thread 
'init' died.
java.lang.RuntimeException: None of the configured paths are initialized.
        at 
org.apache.accumulo.server.ServerDirs.checkBaseUris(ServerDirs.java:119) 
~[accumulo-server-base-2.1.0.jar:2.1.0]
        at 
org.apache.accumulo.server.init.Initialize.addVolumes(Initialize.java:449) 
~[accumulo-server-base-2.1.0.jar:2.1.0]
        at 
org.apache.accumulo.server.init.Initialize.execute(Initialize.java:543) 
~[accumulo-server-base-2.1.0.jar:2.1.0]
        at org.apache.accumulo.start.Main.lambda$execKeyword$0(Main.java:122) 
~[accumulo-start-2.1.0.jar:2.1.0]
        at java.lang.Thread.run(Thread.java:829) ~[?:?]
Thread 'init' died.

I have attached complete log:

Reply via email to