Closed aazaff closed 7 years ago
Fixed with reboot of both REST and app server at 20:30 UTC on 1/25/2017. The cause should be investigated, this has happened twice since original deployment. Will begin by looking into logs.
@jpjenk Just for future reference, did you learn about this problem through this issue or through another means?
Good point, we should have discussed this at the meeting on 1/24 (yesterday). I learned of it through GitHub email when you raised the issue because I'm watching the ChangeLog repo. It worked in this case and thank you very much for alerting me @aazaff but this is probably not the best venue for something that is clearly a server fault. Best policy would be to email me directly (jjenki25 [at] gmu.edu) and cc Michael (mmcclenn [at] geology.wisc.edu). Chances are I will receive the message first and if it really is a system administrator issue, resolve it. I'll follow up with Michael if necessary.
I was actually more curious if we had some sort of automated diagnostic that periodically checks for 500 series errors. I only learned about the problem because I was telegrammed by a random user.
Also, it is down again.
No we don't and yes we should have a automated way of being notified about such things. I will set something up in the very near future.
I've restarted the server process so the system is operational again. I can see what the fault is and will work on a solution, keeping it alive manually until then.
I'll keep this issue open until it is properly resolved.
The download form and login are down, 502 error.