Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

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

Views:
195
Visibility:
Public
Votes:
0
Category:
cloud-sync
Specialty:
cloud
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

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support