Hi All,
I have installed the MID Server on my local machine 192.168.89.156/23
and set up an API call using the MID server
However, when I test the API call, it returns the error: 'No response for ECC message request with sysid=xxx after waiting for 30 seconds in ECC Queue
ECC Queue:
Check the logs in the MID server:
2024-10-04T09:11:15.178-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:11:15.176Z, stats threads: 98, memory max: 910.0mb, allocated: 298.0mb, used: 81.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
2024-10-04T09:12:03.807-0400 INFO (Worker-Interactive:HeartbeatProbe-404274e1c3cd5a109c471a2ed40131be) [AWorker:137] Worker starting: HeartbeatProbe
2024-10-04T09:12:03.807-0400 INFO (Worker-Interactive:HeartbeatProbe-404274e1c3cd5a109c471a2ed40131be) [HeartbeatProbe:46] Probing heartbeatprobe
2024-10-04T09:12:03.808-0400 INFO (Worker-Interactive:HeartbeatProbe-404274e1c3cd5a109c471a2ed40131be) [HeartbeatProbe:51] Finished firing the heartbeatprobe
2024-10-04T09:12:03.810-0400 INFO (Worker-Interactive:HeartbeatProbe-404274e1c3cd5a109c471a2ed40131be) [ECCSender:219] Enqueuing: /opt/servicenow/mid/agent/work/monitors/ECCSender/output_0/ecc_queue.404274e1c3cd5a109c471a2ed40131be.xml
2024-10-04T09:12:03.812-0400 INFO (Worker-Interactive:HeartbeatProbe-404274e1c3cd5a109c471a2ed40131be) [AWorker:145] Worker completed: HeartbeatProbe time: 0:00:00.001
2024-10-04T09:12:03.813-0400 INFO (ECCQueueMonitor.1) [ECCQueueMonitor:389] Received message with timestamp: 2024-10-04 13:12:03. Existing Query window is : 2024-10-04 11:07:03, Updated the query window to: 2024-10-04 11:12:03
2024-10-04T09:12:03.813-0400 INFO (ECCQueueMonitor.1) [FileReadWrite:75] Time being written to the file : 1728040323000
2024-10-04T09:12:03.994-0400 INFO (ECCSender.1) [ECCSenderCache:414] Sending ecc_queue.404274e1c3cd5a109c471a2ed40131be.xml
2024-10-04T09:12:15.085-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:12:15.085Z, stats threads: 99, memory max: 910.0mb, allocated: 298.0mb, used: 80.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
2024-10-04T09:13:10.275-0400 DEBUG (SecurityPolicySyncer.1) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:13:15.088-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:13:15.088Z, stats threads: 98, memory max: 910.0mb, allocated: 298.0mb, used: 80.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
2024-10-04T09:13:50.434-0400 DEBUG (SecurityPolicySyncer.1) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:14:15.138-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:14:15.138Z, stats threads: 98, memory max: 910.0mb, allocated: 298.0mb, used: 81.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
2024-10-04T09:14:30.481-0400 DEBUG (SecurityPolicySyncer.1) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:15:10.420-0400 DEBUG (SecurityPolicySyncer.1) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:15:15.081-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:15:15.079Z, stats threads: 98, memory max: 910.0mb, allocated: 298.0mb, used: 80.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
2024-10-04T09:15:49.479-0400 DEBUG (SignatureValidationMonitor.1200) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:15:50.263-0400 DEBUG (SecurityPolicySyncer.1) [OutboundHTTPClientGCFInvoker:29] OutboundHTTPClientGCFInvoker - GCF Collector not set
2024-10-04T09:16:15.090-0400 INFO (LogStatusMonitor.60) [LogStatusMonitor:54] 2024-10-04T13:16:15.090Z, stats threads: 98, memory max: 910.0mb, allocated: 298.0mb, used: 80.0mb, standard.queued: 0 probes, standard.processing: 0 probes, expedited.queued: 0 probes, expedited.processing: 0 probes, interactive.queued: 0 probes, interactive.processing: 0 probes
I have enabled debugging on the endpoint, but it doesn't seem to be called. I tested calling an online API, and it worked fine. Do you know how to fix this error?
Any help would be greatly appreciated!
Thanks,
Phong Huynh
