MID Server status stopped and started due to "Machine is shutting down"Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } We often see issues were MID server is restarted and customer suspect this is happening because of upgrade to new release. Hence, the good practice is to grab MID server logs from the affected MID server and find root cause. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Open affected MID Server record from the instance.Under Related Links, Click Grab MID Logs.Navigated to ECC queue and add following filter: Topic [is] [SystemCommand]Source [is] [grabLog]Agent [is] [your MID Server name] Search for the Agent0.log.0 and wrapper.log entries in the list view. These logs are also accessible in the \agent\logs\ file path. Wrapper Log:2019/12/15 00:33:17 | Machine is shutting down. 2019/12/15 00:35:29 | --> Wrapper Started as Service 2019/12/15 00:35:34 | Java Service Wrapper Standard Edition 64-bit 3.5.36 2019/12/15 00:35:34 | Copyright (C) 1999-2018 Tanuki Software, Ltd. All Rights Reserved. 2019/12/15 00:35:34 | http://wrapper.tanukisoftware.com 2019/12/15 00:35:34 | Licensed to ServiceNow, Inc. for MID 2019/12/15 00:35:34 | 2019/12/15 00:35:47 | Child process: Java version: timed out 2019/12/15 00:35:47 | Failed to retrieve the version of Java. Resolving to the lowest supported version (1.4). 2019/12/15 00:35:58 | Wrapper Process has not received any CPU time for 21 seconds. Extending timeouts. 2019/12/15 00:35:58 | Launching a JVM... 2019/12/15 00:35:58 | Wrapper Process has not received any CPU time for 21 seconds. Extending timeouts. 2019/12/15 00:35:58 | Launching a JVM... 2019/12/15 00:37:24 | WrapperManager: Initializing... 2019/12/15 00:37:24 | Wrapper Process has not received any CPU time for 57 seconds. Extending timeouts. 2019/12/15 00:37:34 | Startup failed: Timed out waiting for a signal from the JVM. Agent Log:12/15/19 00:33:18 (649) WrapperListener_stop_runner Running under Java version: 1.8.0_181-sncmid1, java PID: 7616, args: stop 12/15/19 00:33:18 (650) WrapperListener_stop_runner Stopping MID server 12/15/19 00:33:18 (650) WrapperListener_stop_runner Main.handleStop() before shutdown, OperationalState=UP 12/15/19 00:33:18 (919) WrapperListener_stop_runner Setting mid status to Down 12/15/19 00:33:18 (919) WrapperListener_stop_runner Instance.updateAgentRecordStopped(), OperationalState=UP 12/15/19 00:33:19 (138) WrapperListener_stop_runner interrupting thread IdleConnectionMonitor.5 12/15/19 00:33:19 (310) WrapperListener_stop_runner interrupting thread AutoUpgrade.3600 12/15/19 00:33:19 (466) WrapperListener_stop_runner interrupting thread PatternAttributeFileMonitor.3600 12/15/19 00:33:19 (622) WrapperListener_stop_runner interrupting thread StatusMonitor.600 12/15/19 00:33:19 (778) WrapperListener_stop_runner interrupting thread RefreshMonitor.65 12/15/19 00:33:19 (935) WrapperListener_stop_runner interrupting thread LogStatusMonitor.60 12/15/19 00:33:20 (091) WrapperListener_stop_runner interrupting thread ECCQueueMonitor.40 12/15/19 00:33:20 (247) WrapperListener_stop_runner interrupting thread FileSyncer.1 12/15/19 00:33:20 (403) WrapperListener_stop_runner interrupting thread ECCSender.1 12/15/19 00:33:20 (997) WrapperListener_stop_runner Destroying injector... 12/15/19 00:33:21 (341) WrapperListener_stop_runner Closing com.service_now.mid.amb.AMBClientProvider 12/15/19 00:33:22 (325) WrapperListener_stop_runner Closing com.service_now.monitor.PriorityThreadPoolProvider 12/15/19 00:33:22 (325) WrapperListener_stop_runner Shutting down ThreadPool-Standard 12/15/19 00:33:22 (325) WrapperListener_stop_runner Shutting down ThreadPool-Expedited 12/15/19 00:33:22 (325) WrapperListener_stop_runner Shutting down ThreadPool-Interactive 12/15/19 00:33:22 (356) WrapperListener_stop_runner ThreadPool-Standard terminated 12/15/19 00:33:22 (356) WrapperListener_stop_runner ThreadPool-Expedited terminated 12/15/19 00:33:22 (356) WrapperListener_stop_runner ThreadPool-Interactive terminated 12/15/19 00:33:22 (372) WrapperListener_stop_runner Closing com.service_now.mid.extension.container.ExtensionContainer 12/15/19 00:33:22 (372) WrapperListener_stop_runner ExtensionContainer is shutting down... 12/15/19 00:33:22 (372) WrapperListener_stop_runner ...waiting a maximum shutdown time of 1000ms 12/15/19 00:33:22 (372) WrapperListener_stop_runner ExtensionContainer is cleanly shut down 12/15/19 00:33:22 (372) WrapperListener_stop_runner Closing com.service_now.mid.probe.event.SNEventBulkSender 12/15/19 00:33:22 (513) EventBulkSenderThread-1 the event sender was stopped after sending 0 events in 0 bulks. 12/15/19 00:33:22 (513) WrapperListener_stop_runner Closing com.service_now.mid.cluster.ignite.IgniteClusterManager 12/15/19 00:33:22 (513) WrapperListener_stop_runner Main.handleStop() after shutdown, OperationalState=UP 12/15/19 00:33:22 (606) MIDServer MID Server stopping 12/15/19 00:33:23 (013) MIDServer Stoping LDAP Listener for: LDAP SBMOffshore 12/15/19 00:33:23 (903) MIDServer MID Server stopped Observation:Found in logs the MID server service stopped because the "Machine is shutting down" triggered. Hence, due to host machine shut down the MID server service stopped.Further customer to check internally to find out the reason for Machine shut down with the time stamp available in the agent logs. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This is one cause which we identified for MID server restarted in Agent logs. There might be more reasons for the MID server getting restarted. Hence, review MID Server agent logs for more details."Machine is shutting down" explanationhttps://wrapper.tanukisoftware.com/doc/english/qna-shutdown.html