The MID server upgrade fails with an the error:

"Gobbling stderr: cmd.exe /C bin\glide-dist-upgrade.bat start Gobbled: ERROR | wrapper | The ServiceNow Platform Distribution Upgrade service was launched, but failed to start".

1. Install a MID server (normally using Linux but it is not known to matter).
2. Identify at what time of the hour auto upgrades occurs.
3. Start/restart SystemCommand on the MID just few seconds before that time.

If the problem is recreated, you will see warnings in the logs as below:

Agent logs:
10/15/19 10:21:35 (734) Gobbling stderr: cmd.exe /C bin\glide-dist-upgrade.bat start Gobbled: ERROR | wrapper | 2019/10/15 10:21:30 | The ServiceNow Platform Distribution Upgrade (sfdphdev-ldap) service was launched, but failed to start.


Wrapper logs:
2019/10/15 15:03:08 | Launching a JVM...
2019/10/15 15:03:40 | Startup failed: Timed out waiting for a signal from the JVM.
2019/10/15 15:03:40 | JVM did not exit on request, termination requested.
2019/10/15 15:03:55 | JVM exited after being requested to terminate.
2019/10/15 15:04:00 | Launching a JVM...
2019/10/15 15:04:32 | Startup failed: Timed out waiting for a signal from the JVM.
2019/10/15 15:04:32 | JVM did not exit on request, termination requested.
2019/10/15 15:04:47 | JVM exited after being requested to terminate.
2019/10/15 15:04:48 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
2019/10/15 15:04:48 | There may be a configuration problem: please check the logs.


1. Depending on the operating system:
   • Windows: From the Services control panel, 'Start' the 'ServiceNow Platform Distribution Upgrade  (...)' Service.
   • Linux: The temp folder (see below) will contain a script that can be re-run with "sudo ./glide-dist-upgrade.sh start"
2. Wait for a few minutes, and see if the MID Server is Up in the instance. 
3. If it still doesn't work, you may need to go through the manual upgrade process.