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.

Sign up for GitHub

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

Jump to bottom

Create Status Page for Dataverse #131

Closed
eaquigley opened this issue Jul 9, 2014 · 7 comments
Closed

Create Status Page for Dataverse #131

eaquigley opened this issue Jul 9, 2014 · 7 comments
Labels
Feature: Performance & Stability Type: Feature a feature request

Comments

@eaquigley
Copy link
Contributor

eaquigley commented Jul 9, 2014 •
edited by djbrooke
Loading

Author Name: Elizabeth Quigley (@eaquigley)
Original Redmine Issue: 3540, https://redmine.hmdc.harvard.edu/issues/3540
Original Date: 2014-02-07

If there is an issue (i.e. Solr is down, Rserve is down) a message should appear on the page to inform the user what is going on with a link to this status page where they can get more information. Examples: http://services.huit.harvard.edu/status-dashboard or https://status.github.com
@eaquigley eaquigley added this to the Dataverse 4.0: In Review milestone Jul 9, 2014
@eaquigley eaquigley mentioned this issue Jul 9, 2014
Closed
@eaquigley eaquigley modified the milestones: Dataverse 4.0: Final, Dataverse 4.0: In Review, Dataverse 4.0: Beta 5 Jul 15, 2014
@eaquigley
Copy link
Contributor Author

@pdurbin I'm assigning this to you for the beta push in which search is supposed to be done. wasn't sure if @mheppler should be the one creating this or not so wanted to get confirmation from you.

@pdurbin pdurbin modified the milestones: Beta 9 - Dataverse 4.0, In Review - Dataverse 4.0 Nov 12, 2014
@pdurbin pdurbin mentioned this issue Nov 12, 2014
Closed
@pdurbin
Copy link
Member

pdurbin commented Nov 12, 2014

@mheppler can you please comment on if you have a mockup or ideas for a status page? Would you be able to add some xhtml to the repo? See also #1042 and https://docs.google.com/a/harvard.edu/document/d/1JhxVn4caKlxm7l4jLCmwuvFIhIJXGULHfKE2Isr-Oxc/edit?usp=sharing

@pdurbin pdurbin assigned mheppler and unassigned pdurbin Nov 12, 2014
@mheppler mheppler modified the milestones: 4.1, Beta 9 - Dataverse 4.0 Nov 18, 2014
@mheppler mheppler assigned pdurbin and unassigned mheppler Nov 18, 2014
@pdurbin pdurbin mentioned this issue Feb 6, 2015
Closed
@scolapasta scolapasta modified the milestones: In Review - Long Term, In Review - Short Term May 8, 2015
pdurbin added a commit that referenced this issue Oct 8, 2015
@pdurbin
configure Vagrant to use custom 503 error page #131
aba7cd2
@pdurbin
Copy link
Member

pdurbin commented Oct 8, 2015

It seems that in practice the most common need we have for a status page is one that's served up by Apache when Dataverse is slow to respond. This is the dreaded "503 Service Temporarily Unavailable" page that says, "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." Basically, Apache is trying to serve up content from Glassfish (the Dataverse app) but it isn't returning in a timely manner. Rather than returning the default page used by Apache (screenshot below) we could configure Apache to serve up a friendlier page. In
aba7cd2 I just pushed a proof of concept in the Vagrant config. The HTML file I added is currently very basic but it say whatever we want and be styled however we want. The idea is for the custom HTML page to be an improvement over this:

503_service_temporarily_unavailable_-_2015-10-09_09 06 52

@pdurbin pdurbin removed their assignment Jan 21, 2016
@pdurbin
Copy link
Member

pdurbin commented Jan 28, 2016

Since GitHub went down yesterday it seems like a good time to grab some screenshots from https://status.github.com since the data is "interesting" instead of showing that they are always up:

github_system_status_-_2016-01-28_10 24 19
github_system_status_-_2016-01-28_10 24 37

We love you GitHub! Great recovery!

@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@kcondon
Copy link
Contributor

kcondon commented May 2, 2016

We are working toward having better error pages to let users know what's going on.

@kcondon kcondon closed this as completed May 2, 2016
@pdurbin pdurbin mentioned this issue Jun 27, 2017
Closed
mderuijter added a commit to mderuijter/dataverse that referenced this issue Oct 28, 2021
@mderuijter
DD-647 fixed/refactored exception handling (IQSS#131)
a55304c 
* fixed/refactored exception handling

* organized imports

* Revert "organized imports"

This reverts commit 87af77c.

* fixed import-diffs
@pdurbin
Copy link
Member

pdurbin commented Dec 7, 2021

Related:

@pdurbin
Copy link
Member

pdurbin commented Sep 9, 2022

Related:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature: Performance & Stability Type: Feature a feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pdurbin @mheppler @scolapasta @kcondon @eaquigley