I'm curious to the underlying "cleaning" differences between restarting the entire ArcGIS Server process with stopserver.sh vs. doing a stop through the arcgis/admin console.
Obviously stopserver.sh shuts down the entire process, and admin-stop will keep up the admin/rest APIs and Manager.
I've noticed that the above command shuts down all services and arcsoc.exe processes, but does it keep open states in the background that get resumed on startup, or would this be the equivalent of running stopserver.sh in regards to application server maintenance?
The problem that I am running into is that over time that ArcGIS Server does a poor job of recycling resources, eventually causing issues with services. I'd like to run a scheduled reboot, but currently have a clustered configuration and this would require running stopserver.sh separately on each system.
I would rather create something that is system-independent (In case I migrate), and that works through the web adapter.