BlueXP Services

Cloud Sync Issues with Linux Data Broker

FlorinDP
2,502 Views

Hello,

 

I am getting the following errors on in the data-broker.log. Any idea on how to troubleshoot this?

 

1|data-broker  | [2021-03-04T17:02:58.392] [INFO] [MASTER] [0] [1827] Restarting worker of type ACL-SERVER.
1|data-broker | [2021-03-04T17:02:58.392] [INFO] [MASTER] [0] [1827] Forking file: /opt/netapp/databroker/acl-server.js
1|data-broker | [2021-03-04T17:02:58.918] [WARN] [MASTER] [0] [1827] Worker #1073471, PID 20311 died SIGABRT.
1|data-broker | [2021-03-04T17:02:58.919] [INFO] [MASTER] [0] [1827] Restarting worker of type ACL-SERVER.
1|data-broker | [2021-03-04T17:02:58.919] [INFO] [MASTER] [0] [1827] Forking file: /opt/netapp/databroker/acl-server.js
1|data-broker | [2021-03-04T17:02:59.448] [WARN] [MASTER] [0] [1827] Worker #1073472, PID 21046 died SIGABRT.
1|data-broker | [2021-03-04T17:02:59.450] [INFO] [MASTER] [0] [1827] Restarting worker of type ACL-SERVER.
1|data-broker | [2021-03-04T17:02:59.451] [INFO] [MASTER] [0] [1827] Forking file: /opt/netapp/databroker/acl-server.js
1|data-broker | [2021-03-04T17:03:00.002] [WARN] [MASTER] [0] [1827] Worker #1073473, PID 21782 died SIGABRT.
1|data-broker | [2021-03-04T17:03:00.002] [INFO] [MASTER] [0] [1827] Restarting worker of type ACL-SERVER.
1|data-broker | [2021-03-04T17:03:00.003] [INFO] [MASTER] [0] [1827] Forking file: /opt/netapp/databroker/acl-server.js
1|data-broker | [2021-03-04T17:03:00.532] [WARN] [MASTER] [0] [1827] Worker #1073474, PID 22518 died SIGABRT.
1|data-broker | [2021-03-04T17:03:00.532] [INFO] [MASTER] [0] [1827] Restarting worker of type ACL-SERVER.
1|data-broker | [2021-03-04T17:03:00.533] [INFO] [MASTER] [0] [1827] Forking file: /opt/netapp/databroker/acl-server.js

 

2 REPLIES 2

RamiB
2,404 Views

Hi,

 

As you see , this are warning but they don't indicate of a real issue.

what is the impact you have because of this warnings in usability of the product?

can you attach the complete log?

 

Thanks 

RosivaldoCorrea
2,151 Views

Hi RamiB,

 

our concern here is about this weird behavior.  the process is always restarting and dying right after. We don't think it could be normal.
---

[2021-04-19T18:46:06.199] [INFO] [MASTER] [0] [8700] Restarting worker of type ACL-SERVER.
[2021-04-19T18:46:06.200] [INFO] [MASTER] [0] [8700] Forking file: /opt/netapp/databroker/acl-server.js
[2021-04-19T18:46:06.778] [WARN] [MASTER] [0] [8700] Worker #1120137, PID 22667 died SIGABRT.

---

 

But we are trying to find why in our dashboard the info about the synchronization is not working. Our investigation began here. If you have any idea to help us I will appreciate that.

RosivaldoCorrea_0-1618858435503.png

 

 

Note: We are seeing this from data-broker.log too.

--

[2021-04-19T18:57:02.350] [ERROR] [MASTER] [0] [8700] Got uncaught exception Error: read ENOTCONN
at tryReadStart (net.js:571:20)
at Socket._read (net.js:582:5)
at Socket.Readable.read (_stream_readable.js:474:10)
at Socket.read (net.js:622:39)
at new Socket (net.js:374:12)
at Object.Socket (net.js:265:41)
at createSocket (internal/child_process.js:313:14)
at ChildProcess.spawn (internal/child_process.js:436:23)
at spawn (child_process.js:548:9)
at Object.execFile (child_process.js:232:17)
at exec (child_process.js:153:25)
at /opt/netapp/databroker/node_modules/systeminformation/lib/network.js:1104:13
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
errno: -107,
code: 'ENOTCONN',
syscall: 'read'
}
[2021-04-19T18:57:02.351] [ERROR] [MASTER] [0] [8700] Got uncaught exception Error: read ENOTCONN
at tryReadStart (net.js:571:20)
at Socket._read (net.js:582:5)
at Socket.Readable.read (_stream_readable.js:474:10)
at Socket.read (net.js:622:39)
at new Socket (net.js:374:12)
at Object.Socket (net.js:265:41)
at createSocket (internal/child_process.js:313:14)
at ChildProcess.spawn (internal/child_process.js:436:23)
at spawn (child_process.js:548:9)
at Object.execFile (child_process.js:232:17)
at exec (child_process.js:153:25)
at /opt/netapp/databroker/node_modules/systeminformation/lib/network.js:1104:13
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
errno: -107,
code: 'ENOTCONN',
syscall: 'read'
}
[2021-04-19T18:57:02.352] [ERROR] [MASTER] [0] [8700] Got uncaught exception Error: read ENOTCONN
at tryReadStart (net.js:571:20)
at Socket._read (net.js:582:5)
at Socket.Readable.read (_stream_readable.js:474:10)
at Socket.read (net.js:622:39)
at new Socket (net.js:374:12)
at Object.Socket (net.js:265:41)
at createSocket (internal/child_process.js:313:14)
at ChildProcess.spawn (internal/child_process.js:436:23)
at spawn (child_process.js:548:9)
at Object.execFile (child_process.js:232:17)
at exec (child_process.js:153:25)
at /opt/netapp/databroker/node_modules/systeminformation/lib/network.js:1104:13
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
errno: -107,
code: 'ENOTCONN',
syscall: 'read'
}
[2021-04-19T18:57:02.353] [ERROR] [MASTER] [0] [8700] Got uncaught exception Error: read ENOTCONN
at tryReadStart (net.js:571:20)
at Socket._read (net.js:582:5)
at Socket.Readable.read (_stream_readable.js:474:10)
at Socket.read (net.js:622:39)
at new Socket (net.js:374:12)
at Object.Socket (net.js:265:41)
at createSocket (internal/child_process.js:313:14)
at ChildProcess.spawn (internal/child_process.js:436:23)
at spawn (child_process.js:548:9)
at Object.execFile (child_process.js:232:17)
at exec (child_process.js:153:25)
at /opt/netapp/databroker/node_modules/systeminformation/lib/network.js:1104:13
at processTicksAndRejections (internal/process/task_queues.js:79:11) {
errno: -107,
code: 'ENOTCONN',
syscall: 'read'

--

Public