Skip to main content
NetApp Knowledge Base

BlueXP Copy & Sync data broker log shows message forking file acl-server.js and worker PID died SIGABRT continuously

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

Applies to

  • BlueXP Copy & Sync
  • Data broker (Configured with 8 CPU/vCPU)

Issue

  • The data broker crashes and is shown in a failed status:
clipboard_e768855ba9891346793e1d960df8103cf.png
 
  • When logging into the data broker CLI might show "bash: fork: Cannot allocate memory" during login.
  • The data broker logs show :
[INFO] [MASTER] [0] [27831] Booting, number of CPUs 8
[INFO] [MASTER] [0] [27831] Prepare vault for data broker
...
[INFO] [MASTER] [0] [27831] Forking file: /opt/netapp/databroker/acl-server.js
[WARN] [MASTER] [0] [27831] Worker #28, PID 28031 died SIGABRT.
[INFO] [MASTER] [0] [27831] Restarting worker of type ACL-SERVER.
..
[INFO] [MASTER] [0] [27831] Forking file: /opt/netapp/databroker/acl-server.js
[WARN] [MASTER] [0] [27831] Worker #44, PID 27682 died SIGABRT.
[INFO] [MASTER] [0] [27831] Restarting worker of type ACL-SERVER.

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.