Waiting for MID server to respond

[Pascal P]

Hi,

My mid server suddenly stopped working on DEV instance.

I'm pretty sure it is NOT related to our network connection, because other Mid Server, on the same server, are still working fine.

 I was in the middle of importing data, and the Mid Server stopped responding. And since then, I always get the error "Did not get a response from the MID server".

My MID SERVER is:

Status : UP

Validated: YES

I tried : 

Restart MID

Rekey

Invalidate / Validate

Restart the service on the Server side, with the Services.msc console.

Restart the service on the Server Side using "Stop.bat" and "Start.bat"

I also followed this link (https://community.servicenow.com/community?id=community_blog&sys_id=ad8ce6e1dbd0dbc01dcaf3231f96192c) because I had the same LOG as them, but the workaround did not work in my case. (I don't have an ECC QUEUE stuck in the "ready" state.)

Here is my Log at the exact time it stopped working.

05/14/21 09:01:59 (391) LogStatusMonitor.60 stats threads: 90, memory max: 910.0mb, allocated: 388.0mb, used: 36.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
05/14/21 09:02:21 (171) ECCSender.1 Sending ecc_queue.7c7544f2870c305041b3dd373cbb356d.xml
05/14/21 09:02:21 (600) ECCSender.1 Sending ecc_queue.89e40032a00030107cca1c2220ee596d.xml
05/14/21 09:02:22 (673) ECCSender.1 Sending ecc_queue.1796aec28580000001.xml
05/14/21 09:02:28 (115) ECCSender.1 Sending ecc_queue.1796aec286b0000001.xml
05/14/21 09:02:33 (178) ECCSender.1 Sending ecc_queue.1796aec287d0000001.xml
05/14/21 09:02:35 (412) ECCSender.1 Sending ecc_queue.1796aec28920000001.xml
05/14/21 09:02:38 (018) ECCSender.1 Sending ecc_queue.1796aec28a80000001.xml
05/14/21 09:02:58 (156) ECCQueueMonitor.1 WARNING *** WARNING *** No probe registered to cancel for a given agent correlator 171308fe87c8305041b3dd373cbb3524
05/14/21 09:02:58 (158) Worker-Standard:JDBCProbeError-38568836870c305041b3dd373cbb3579 Worker starting: JDBCProbeError source: JDBC import via Mid server cancelled
05/14/21 09:02:58 (164) Worker-Standard:JDBCProbeError-38568836870c305041b3dd373cbb3579 WARNING *** WARNING *** No probe registered to cancel for a given agent correlator 171308fe87c8305041b3dd373cbb3524
05/14/21 09:02:58 (169) Worker-Standard:JDBCProbeError-38568836870c305041b3dd373cbb3579 Enqueuing: C:\ServiceNow\MID Server1\mid.newyork-06-26-2019__patch2-09-18-2019_09-24-2019_1701.windows.x86-64\agent\work\monitors\ECCSender\output_2\ecc_queue.38568836870c305041b3dd373cbb3579.xml
05/14/21 09:02:58 (170) Worker-Standard:JDBCProbeError-38568836870c305041b3dd373cbb3579 Worker completed: JDBCProbeError source: JDBC import via Mid server cancelled time: 0:00:00.006
05/14/21 09:02:59 (409) LogStatusMonitor.60 stats threads: 90, memory max: 910.0mb, allocated: 388.0mb, used: 37.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

And now, everytime I try to import data via this Mid Server, i get this error in the Log:

05/14/21 10:49:32 (569) Worker-Interactive:HeartbeatProbe-f79e50721b0470d0c39b866ecc4bcbd0 Worker completed: HeartbeatProbe time: 0:00:00.000
05/14/21 10:49:59 (901) LogStatusMonitor.60 stats threads: 90, memory max: 910.0mb, allocated: 396.0mb, used: 66.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
05/14/21 10:50:59 (863) LogStatusMonitor.60 stats threads: 90, memory max: 910.0mb, allocated: 396.0mb, used: 69.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
05/14/21 10:51:55 (072) ECCSender.1 WARNING *** WARNING *** No response from host
05/14/21 10:51:55 (072) ECCSender.1 WARNING *** WARNING *** RemoteGlideRecord failed to send data to https://*********.service-now.com/ with (No response from host)
05/14/21 10:51:55 (072) ECCSender.1 Attempt to send ecc_queue.72bcd0be1bc070d0c39b866ecc4bcb0d.xml failed: file remains enqueued for later sending
05/14/21 10:51:55 (074) ECCSender.1 Sending ecc_queue.66ba1032f90030107ccac150f53ee625.xml

Any ideas??

[Naveen Velagapu]

hi 

Try to login to physical host where you installed mid server and try below 

1. windows +r 

2. services.msc

3. In the services , locate your installed mid server and right click and stop and restart the service. 

Mark "helpful / correct answer" if this is useful.

Thanks,

Naveen

[Pascal P]

Hi Naveen,

Unfortunatly, I already tried this without success.

Thanks anyway

[Pascal P · Accepted solution]

Ok, we managed to solve this.

Basically, we ended up rebooting both servers, the one where the MidServer is installed, and the one with the database from which the MidServer was pulling Data.

And now everything is back to normal.

Hope this helps, even though I'm not 100% sure what happened here.