Skip to main content
NetApp Knowledge Base

The installation of AU for DII fails at step 2/8 "Sending Certificate-Signing Request" due to a timeout

  1. Last updated
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
data-infrastructure-insights
Specialty:
om
Last Updated:

 

Applies to

  • Data Infrastracture Insights (DII)
  • Acquisition Unit (AU)

Issue

  • Installing AU fails at step 2/8 "Sending Certificate-Signing Request" due to a timeout.
  • acq.log shows the following error repeatedly

INFO [main] com.onaro.sanscreen.acquisition.framework.mgmt.security.TlsUtils (TlsUtils.java:121) - Loading current TLS context
INFO [main] com.netapp.oci.common.vault.FileVault (FileVault.java:83) - AUDIT: Retrieve truststore_new_password from vault
INFO [main] com.onaro.sanscreen.acquisition.framework.mgmt.security.TlsUtils (TlsUtils.java:513) - Loaded one-time token from file acquisition.properties
ERROR [main] com.onaro.sanscreen.acquisition.framework.mgmt.FrameworkService (FrameworkService.java:84) - Framework service start error: Illegal base64 character 2d
java.lang.IllegalArgumentException: Illegal base64 character 2d
 at java.base/java.util.Base64$Decoder.decode0(Base64.java:852) ~[?:?]
 at java.base/java.util.Base64$Decoder.decode(Base64.java:570) ~[?:?]
 at java.base/java.util.Base64$Decoder.decode(Base64.java:593) ~[?:?]
 at com.onaro.sanscreen.acquisition.framework.mgmt.security.OneTimeToken.parse(OneTimeToken.java:80) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.security.OneTimeToken.<init>(OneTimeToken.java:32) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.security.TlsUtils.saveIncomingToken(TlsUtils.java:187) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at java.base/java.util.Optional.ifPresent(Optional.java:178) ~[?:?]
 at com.onaro.sanscreen.acquisition.framework.mgmt.security.TlsUtils.installOneTimeToken(TlsUtils.java:162) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.CommunicationManager.initTlsContext(CommunicationManager.java:719) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.CommunicationManager.doStart(CommunicationManager.java:333) ~[au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.FrameworkService.start(FrameworkService.java:79) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.ServiceManager.doStart(ServiceManager.java:291) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.mgmt.FrameworkService.start(FrameworkService.java:79) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.Main.run(Main.java:194) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.Main.startUp(Main.java:156) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.Main.doMain(Main.java:316) [au.jar:hotfix_1_783_1-SNAPSHOT]
 at com.onaro.sanscreen.acquisition.framework.Main.main(Main.java:302) [au.jar:hotfix_1_783_1-SNAPSHOT]

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.