Skip to main content
NetApp Knowledge Base

Cloud Sync data broker stops running - Got uncaught exception Error: spawn ENOMEM

  1. Last updated
  2. Save as PDF
Views:
218
Visibility:
Public
Votes:
0
Category:
cloud-sync
Specialty:
nas
Last Updated:

Applies to

Cloud Sync

Issue

Cloud Sync data broker services may stop running or fail to start under some scenarios. In some cases, this could be due to insufficient memory in the data broker host. Below is a data broker log which matches that situation:

[2022-07-07T10:02:04.461] [ERROR] [MASTER] [0] [32142] Got uncaught exception Error: spawn ENOMEM
at ChildProcess.spawn (internal/child_process.js:405:11)
at spawn (child_process.js:677:9)
at Object.execFile (child_process.js:311:17)
at exec (child_process.js:212:25)
at /opt/netapp/databroker/node_modules/systeminformation/lib/network.js:1249:13
at processTicksAndRejections (internal/process/task_queues.js:77:11) {
errno: -12,
code: 'ENOMEM',
syscall: 'spawn'
}

 

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.