Is there any way to get the time when the Mid Server was down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2022 06:48 AM
Hello everyone
We are facing an issue with the some of the mid servers - It get's down frequently. As soon as we login to the mid server, status changes to up.
We are trying to figure out what is causing this issue. So, we need to get the timeframe and how frequent the mid server goes down.
Can we fetch it from any of the logs?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2022 06:57 AM
Hi,
you can configure email notification as soon as mid server goes down.
This will notify the users you configure and they can debug it
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2022 07:19 AM
The quickest option is to activate the MID Server Down emails.
Beyond that your only option would be to login to the MID host and search through the log entries; which is time consuming. However, going through the logs can be very informative as it could reveal the reason why your MID's are going down.
Also, be aware that when a MID is "down" it doesn't mean the MID is down/stopped/host rebooted; just that the heartbeat probe did not get a response to the probe request. So this may come down to a firewall issue or other networking issue that is blocking traffic.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2022 12:33 AM
Arathi,
Assuming when you say 'As soon as we login to the mid server, status changes to up.' you mean logging on to the server where the MID is hosted?
If this is the case I would be looking at how service is configured on the host. If the system it is hosted on is Windows, you should check the windows logs. I would also be checking the agent and wrapper logs for the MID server to see if the process is actually being stopped or if there is a pause for some reason.
Other thing I would be asking is if these MID servers have recently had this problem or if they have always had this problem; if it is a recent problem I would be asking what infrastructure changes have occurred to potentially cause this.
At this time, I think the agent and wrapper logs for the MID will give you the most clues.
Hope this helps,
Richard

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2022 05:29 PM