Is there any way to get the time when the Mid Server was down.

Arathi B Raj
Mega Contributor

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?

 

 

4 REPLIES 4

Ankur Bawiskar
Tera Patron
Tera Patron

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

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Ian Mildon
Tera Guru

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.

Richard Hine
Tera Guru
Tera Guru

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

Rahul Priyadars
Giga Sage
Giga Sage
Apart from strps suggested by Richard , you can start monitoring of mid server service and mid server vm host. These are standard monitoring parameters for a host n any service. In our environment we use Solarwinds to monitor mid server vm host n services. Monitoring tool can give u historical data also of its availability. Regards RP