-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing on hyde.cyverse.org #2
Comments
For the moment, have added
to the service definition on hyde. |
That seemed to cause it to get killed immediately. Had to remove it. |
Actually, it seems to still happen regardless of whether the |
|
So it is a problem with running |
Going to table the investigation for now, there is an easy workaround. |
Note that the crash happened again over the weekend, I still don't know what is up with it. |
I've been experimenting with some signal handlers and shutdown events, and can see this locally with the additional debug logging in place:
I'm tempted to see if we can get any more information using something like this deployed out to hyde. |
Unfortunately it is only the last step in the shutdown process, but it at least registers that something is happening. |
On thinking about this a bit more (and remembering that the service wasn't working to begin with), I decided to correlate the outage times with hyde restart times and see if they are happening at the same time. Last outage reported time (check happens once an hour): Last hyde reboot time: So I think rather than a crash this just might be a symptom of the linux service not coming up after reboot. |
I manually killed the container then restarted and it came up. This was the service file that seemed to work:
|
The two changes I made recently were: (1) Updated description to include Will keep an eye on it, but it is working for now. |
So I think the reason there were no logs when inspecting the crashed Docker container was that it just never started. |
There have been a couple times where the Docker container has mysteriously crashed on hyde.cyverse.org. It is unclear what is causing the issue. On log inspection, there isn't really any smoking gun.
The text was updated successfully, but these errors were encountered: