You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While rare, it can happen that the sever gets itself into a state where we cannot access it, particularly when mucking about with installations and upgrading the operating system etc. For these cases we currently have to hope that things go south when somebody is in the office at UT who can manually go to the console and reboot the system if necessary.
We should add a remote switch that allows us to reboot remotely.
{
"status": "new",
"changetime": "2019-02-26T14:33:33",
"_ts": "2019-02-26 14:33:33.978637+00:00",
"description": "While rare, it can happen that the sever gets itself into a state where we cannot access it, particularly when mucking about with installations and upgrading the operating system etc. For these cases we currently have to hope that things go south when somebody is in the office at UT who can manually go to the console and reboot the system if necessary.\n\nWe should add a remote switch that allows us to reboot remotely.",
"reporter": "butler",
"cc": "",
"resolution": "",
"workpackage": "Support Infrastructure",
"time": "2017-11-12T01:15:10",
"component": "SasView",
"summary": "Add remote power switch to UTK server",
"priority": "major",
"keywords": "",
"milestone": "Admin Tasks",
"owner": "",
"type": "enhancement"
}
The text was updated successfully, but these errors were encountered:
While rare, it can happen that the sever gets itself into a state where we cannot access it, particularly when mucking about with installations and upgrading the operating system etc. For these cases we currently have to hope that things go south when somebody is in the office at UT who can manually go to the console and reboot the system if necessary.
We should add a remote switch that allows us to reboot remotely.
Migrated from http://trac.sasview.org/ticket/1034
The text was updated successfully, but these errors were encountered: