Skip to main content
NetApp Knowledge Base

Workload Security agent servics failed to start with URL not found on the token error

Views:
85
Visibility:
Public
Votes:
0
Category:
data-infrastructure-insights
Specialty:
netapp_console
Last Updated:

Applies to

  • Software Workload Security (SWS)
  • Data Infrastructure Insight (DII- Formerly known as Cloud Insights aka CI)
  • Linux agent

Issue

  • SWS agent service  failed to start
  • Error on cloudsecure-agent-service.log:
org.apache. http.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {tls}->http://proxyappbnet.bnet.luxds.net:8080->https://xw2539.cs01-eu-1.cloudinsights.netapp.com:443: Connection reset
 
Terminated... Bye
Terminated... Bye
 
....
 
....
 
Stopped Cloud Secure Agent Daemon Service.
-- Reboot --
Started Cloud Secure Agent Daemon Service.
JAVA PATH: /opt/netapp/cloudsecure/agent/java64/bin/java
Exception in thread "main" com.netapp.datafabric.metadatacatalog.agent.FrameworkException: Agent failed to generate application conf. reason Key serverUrl is not available in the oneTimeToken
at com.netapp.datafabric.metadatacatalog.agent.AgentBootstrapper.bootstrap(AgentBootstrapper.java:34)
at com.netapp.datafabric.metadatacatalog.agent.app.ContrailAgent$.delayedEndpoint$com$netapp$datafabric$metadatacatalog$agent$app$ContrailAgent$1(ContrailAgent.scala:25)
...
...
 
cloudsecure-agent.service: Main process exited, code=exited, status=1/FAILURE
cloudsecure-agent.service: Failed with result 'exit-code'.
cloudsecure-agent.service: Service RestartSec=15s expired, scheduling restart.
cloudsecure-agent.service: Scheduled restart job, restart counter is at 1.
Stopped Cloud Secure Agent Daemon Service.
 
  • journalctl -u cloudsecure-agent.service also shows: Exception in thread "main" com.netapp.datafabric.metadatacatalog.agent.FrameworkException: Agent failed to generate application conf. reason Key serverUrl is not available in the oneTimeToken
  • Reboot of the server/restart of the services fail with the same error
  • Proxy connectivity is working fine

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.