RHEL MID Server does not start after ServiceNow Patch or Upgrade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2026 09:43 AM
We are running SELinux. systemd is managing the start/stop.
After the MID Server upgrades, it shuts down because killterm sent to PIDs
Getting a recommendation from ServiceNow to set KillMode=process, but the RHEL admin team does not want to do this because it is not best practice/recommended.
Not too big of a deal, just need to manually run sh start.sh after upgrades. .service file restarts fine after RHEL server patching. Usually patch/upgrades are managed.
Any suggestions other than setting KillMode=proces?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2026 09:50 AM
Hi @Jeff Boltz1
Refer:
KB2934327 Linux MID Server fails to restart when using non-root user during upgrade
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Thanks I will check with RHEL team
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
https://www.servicenow.com/community/upgrades-and-patching-forum/mid-server-fails-after-patch-updat…
probably the only one thats relevant, but mid.pid is created on a regular OS patching with reboot and it works fine. Its only on the MidServer upgrade that it fails.
