[NAS-2643] When H3 remote access is no longer possible, don't show a status 500 error page Created: 16/May/17 Updated: 20/Jul/18 |
|
| Status: | Reopened |
| Project: | NetarchiveSuite |
| Component/s: | GUI, H3-extensions |
| Affects Version/s: | 5.2 |
| Fix Version/s: | 5.5.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Søren Vejrup Carlsen (Inactive) | Assignee: | Nicholas Clarke (Inactive) |
| Resolution: | Unresolved | ||
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Organization: |
BNF
|
| Verification: | Tricky. Should be doable by trying all the possible H3 monitor urls for at job that is not running. |
| Description |
|
When H3 remote access is no longer possible, don't show a status 500 error page |
| Comments |
| Comment by Colin Rosenthal [ 12/Apr/18 ] |
|
Seems to be working now, except that some old jobs never disappear from the "H3 Remote Access" page. Depending on the job, I get
Job 3 is not currently monitored. Maybe Heritric 3 is not running at this point in time.
Or
NAS Job 5 is in state DONE.
Or
a message offering to mark a job as failed.
The latter seems to come up for new jobs where Heritrix isn't running yet, so the message is misleading. This probably needs some tidying up, but is not blocking for NAS 5.4 |
| Comment by Colin Rosenthal [ 02/Feb/18 ] |
|
Does this need a review? Otherwise please close. |
| Comment by Nicholas Clarke (Inactive) [ 31/May/17 ] |
|
Should be fixed now. But will be in the next planned release because of the current code freeze/release test. |
| Comment by Nicholas Clarke (Inactive) [ 31/May/17 ] |
|
So it used to work before the BnF pull requests. |