Linux MID server auto-upgrade can fail even on Tanuki wrapper version 3.5.36 if MID service is not reinstalled - similar symptoms with PRB1312206DescriptionLinux MID Servers can fail to upgrade automatically if the MID Server was manually upgraded from Madrid to New York. In that case, the MID Server automatic upgrade will fail even though the MID Server is using Tanuki 3.5.36. The Tanuki wrapper was upgraded from 3.5.34 to 3.5.36. The Tanuki Wrapper 3.5.34 parameter SYSTEMD_KILLMODE=control-group was changed to SYSTEMD_KILLMODE=process in 3.5.36. If the MID Server was installed before NY (Tanuki 3.5.36) the parameter value is “control-group” and will not update in NY because the service isn't re-installed during the upgrade. Usually the wrapper log under the temp folder will have the “TERM trapped. Shutting down” message. The following is an example: INFO | jvm 1 | 2020/02/09 18:00:25.051 | INFO: /MyMid/mid/agent/bin/wrapper-linux-x86-64 cannot be deleted: /MyMid/mid/agent/bin/wrapper-linux-x86-64 (Text file busy)INFO | jvm 1 | 2020/02/09 18:00:25.051 | Retrying in 1000ms...INFO | jvm 1 | 2020/02/09 18:00:26.053 | Feb 09, 2020 6:00:25 PM com.snc.dist.mid_upgrade.UpgradeMain missingOrCanDeleteINFO | jvm 1 | 2020/02/09 18:00:26.053 | INFO: /MyMid/mid/agent/bin/wrapper-linux-x86-64 cannot be deleted: /MyMid/mid/agent/bin/wrapper-linux-x86-64 (Text file busy)INFO | jvm 1 | 2020/02/09 18:00:26.053 | Retrying in 1000ms...STATUS | wrapper | 2020/02/09 18:00:26.547 | TERM trapped. Shutting down.Steps to Reproduce 1. Upgrade a Linux MID server from Madrid to New York (might need a manual upgrade).2. Check agent logs to confirm that wrapper service version is 3.5.36 "Java Service Wrapper Standard Edition 64-bit 3.5.36"3. Cat /agent/bin/mid.sh and confirm that SYSTEMD_KILLMODE=process 4. Force upgrade the MID server to another patch in New York release (download the installer of a lower patch using KB0565184).5. Notice that autoupgrade fails with "TERM trapped. Shutting down" (in wrapper log or glide-dist-upgrade logs).WorkaroundTo resolve the issue, re-install New York once on any Linux MID Server whose service was installed in Madrid. After re-installing the service in New York, SYSTEMD_KILLMODE is set to "process" and the service will not have issues with further upgrades. To re-install the service: Using mid.sh on the command line under agent folder: Stop the MID Server: ./bin/mid.sh stopRemove the daemon : ./bin/mid.sh removeInstall the daemon with NY configuration: ./bin/mid.sh installStart the MID Server: ./bin/mid.sh start OR Stop the MID Server: ./bin/mid.sh stopRemove the daemon: Go to /etc/systemd/system and remove your mid server daemonInstall the daemon: under agent folder run ./bin/mid.sh installStart the MID Server: under agent folder run ./bin/mid.sh startRelated Problem: PRB1394171