MID Server fails after patch update – systemctl shows failed, but wrapper and java are running
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2025 09:47 PM
Hello Team,
After applying a recent patch automatically to multiple Linux-based MID Servers, we have noticed a recurring issue:
systemctl status snow.service shows FAILED
But processes like wrapper-linux-x86-64 and java are still running in the background
manual kill -9 <PID> followed by systemctl restart snow resolves the issue
This is happening when ever the SNOW mid-servers are Upgraded automatically !!
Note - We have deployed a shell script, which use to check the status of the service for every 15 minutes. if its failed state it will restart it. When it tried to restart through shell script we got the below error.
Job for snow.service failed because the control process exited with error code.
See "systemctl status snow.service" and "journalctl -xeu snow.service" for details.
Manual kill -9 <PID> followed by systemctl restart snow resolves the issue
Questions:
Is this a known issue with the MID Server patching process?
Are there official recommendations from ServiceNow to handle this reported issue ?
Has anyone implemented a better/cleaner workaround?
Looking for inputs from those who faced similar issues and please share the workaround adapted for the same. Thanks in advance!
