|
|
|
|
|
by sgarland
134 days ago
|
|
I have little to no experience with Windows Server, but at least on Linux, this shouldn’t take hours. Find the last log entries for the system before the reboot; if they point to a specific application, look at its logs, otherwise just check all of them around that time, filtering by log level. Check metrics as well - did the application[s] stop handling requests prior to the restart (keeping in mind that metrics are aggregations), or was it fine up until it wasn’t? If there are no smoking guns, a hardware issue is possible, in which case any decent server should have logged that. > I just want to know what to do to fix it if it can be fixed. Serious question: how do you plan on training juniors if troubleshooting consists of asking an AI what to do? |
|