Skip to main content
NetApp Knowledge Base

Connector in unknown status after deployment from BlueXP

Views:
21
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
bluexp
Last Updated:
5/26/2025, 10:34:42 AM

Applies to

  • BlueXP Connector
  • Amazon Web Services (AWS)

Issue

Connector deployment from BlueXP fails and connector shows up as unknown in the BlueXP Console. EC2 instance is up in AWS console but there are no containers running when checked using command docker ps 
 
Error seen in BlueXP GUI when deployment fails :
{"message":"Waiting for agent to be active...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Polling connector status...","priority":"info"}
{"message":"Failed to deploy connector.","priority":"error"}
{"message":"Connector is not ready. Attempts exhausted.","priority":"error"}
{"message":"Error: Connector is not ready. Attempts exhausted.\n    at n.project (https://cloudmanager.netapp.com/static/js/AddConnector.xxxxxx.chunk.js:1:xxxx)\n    at n._next (https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:x:xxxx)\n    at t.next (https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:x:xxxx)\n    at n.notifyNext (https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:x:xxxxx)\n    at n._next (https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:x:xxxx)\n    at t.next (https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:x:xxxx)\n    at https://cloudmanager.netapp.com/static/js/xxxx.xxxxxxxx.chunk.js:1:xxxxx","priority":"error"}
 
Error seen in BlueXP install logs :
[INFO] 2025-05-06T17:11:21.509Z {"title":"Waiting for OCCM, It may take few minutes","success":false,"errorTitle":"Timed out waiting for http://localhost/service-manager/isHealthy","errorDescription":"Waited for 600 seconds","data":{"success":false,"requiredUrl":{"url":"http://localhost/service-manager/isHealthy","expectedStatus":[200]},"text":"connect ECONNREFUSED 127.0.0.1:80","axiosError":{"message":"connect ECONNREFUSED 127.0.0.1:80","name":"Error","stack":"Error: connect ECONNREFUSED 127.0.0.1:80\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:xxxx:xx)","config":{"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false},"transformRequest":[null],"transformResponse":[null],"timeout":3000,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"headers":{"Accept":"application/json, text/plain, */*","User-Agent":"axios/x.xx.x"},"method":"get","url":"http://localhost/service-manager/isHealthy"},"code":"ECONNREFUSED","status":null}}}
 

 

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.