Skip to content
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

COR ont service is down #52

Closed
graybeal opened this issue Jul 26, 2018 · 3 comments
Closed

COR ont service is down #52

graybeal opened this issue Jul 26, 2018 · 3 comments

Comments

@graybeal
Copy link
Contributor

The ont service is not responsive:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /ont.
Reason: Error reading from remote server

The page at cor.esipfed.org is responsive, and the AWS instance is up.

@graybeal
Copy link
Contributor Author

I've contacted Annie (Carlos is out) and we'll look at this in the morning.

@carueda
Copy link
Member

carueda commented Jul 26, 2018

Seems like it was Allegrograph the container that started misbehaving, that is, not responding to some request from the ORR container.

I just restarted Allegrograph and all seems back up.

To make sure the triple store is up to date, I also jsut ran the "reload triple store" function using the Admin UI at http://cor.esipfed.org/ont#/ts

Sorry, not much time now or tomorrow to do a more thorough investigation ... but two quick ideas to keep in mind:

  • upgrade allegrograph (as already suggested elsewhere)
  • include some timeout in requests from ORR to more gracefully handle the case where allegrograph stops responding.

-carlos

@graybeal
Copy link
Contributor Author

Created mmisw/orr-ont#65 and mmisw/orr-ont#66 to capture those ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants