Skip to main content
NetApp Knowledge Base

Cloud Sync failed with Error: no such file or directory, open './vault/keys.json'

Views:
342
Visibility:
Public
Votes:
0
Category:
cloud-sync
Specialty:
bluexp
Last Updated:

Applies to

  • Cloud Sync

Issue

  • Cloud Sync data broker shows status as failed in UI

clipboard_e18027f016aa945a0bfec6858451263ba.png

  • Data Broker logs show error "errno: -2, code: 'ENOENT', syscall: 'open', path: './vault/keys.json'"


[ERROR] [MASTER] [0] [6291] Failed to prepare vault for data broker Error: connect ECONNREFUSED 127.0.0.1:8200
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 8200,
[ERROR] [MASTER] [0] [2789] Got unhandled rejection { p: Promise { <rejected> [Error: ENOENT: no such file or directory, open './vault/keys.json'] { errno: -2, code: 'ENOENT', syscall: 'open', path: './vault/keys.json' } }, reason: [Error: ENOENT: no such file or directory, open './vault/keys.json'] { errno: -2, code: 'ENOENT', syscall: 'open', path: './vault/keys.json' } }

  • Under "/opt/netapp/databroker/vault" we could only find config.hcl and the other directories and keys.json was missing.
     

# ls -al /opt/netapp/databroker/vault/
total 12
drwxr-xr-x.  5 root root   79 May  1 07:43 .
drwxr-xr-x. 10 root root 4096 May  1 03:49 ..
-rw-r--r--.  1 root root  280 May  1 07:43 config.hcl
#

  • Vault is missing from pm2 status 

# pm2 status
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id  │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0   │ data-broker    │ N/A         │ 1.0.29  │ fork    │ 2789     │ 19h    │ 0    │ online    │ 0%       │ 122.0mb  │ root     │ disabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

  • Rebooting data broker doesn't fix the issue

 

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.
Scan to view the article on your device