Opened 8 years ago

Last modified 7 months ago

#8667 assigned enhancement

Distinguish between permanent and temporary Onionoo errors

Reported by: karsten Owned by: metrics-team
Priority: Low Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords: metrics-2018
Cc: gsathya, nusenu@… Actual Points:
Parent ID: Points: 0.2
Reviewer: Sponsor:


As of now, Onionoo has a "maintenance mode" that I'm planning to use very rarely. But sometimes it's necessary to shut down Onionoo to support new features or fix bugs. During this time, Onionoo responds to all requests with a 503 Service Unavailable status code. Atlas should respect this code and display a different warning than:

"Backend error! The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted it may mean that there is an issue with your browser/add-ons. Please report which browser/addons/etc. you're using to the bug tracker."

How about this warning?

"Backend temporarily unavailable! The backend server is temporarily unavailable. If this issue persists for more than a few hours, please report it using the <a href="">bug tracker</a>."

Child Tickets

Change History (11)

comment:1 Changed 8 years ago by karsten

On a related note, should Atlas also distinguish between 400 Bad Request and 500 Internal Server Error (or 4xx and 5xx codes) by telling the user that the issue can more likely be found in the front-end or back-end? That would make for slightly better bug reports, I guess.

comment:2 Changed 7 years ago by karsten now lists HTTP response codes and suggests actions. Pasting here for simplicity:

Response codes: Clients should handle response codes by distinguishing between client and server errors, and if there's a problem, informing their users about the kind of problem. The following response codes are used:

  • 200 OK: The request was processed successfully.
  • 304 Not Modified: Server data has not changed since the "If-Modified-Since" header included in the request.
  • 400 Bad Request: The request could not be processed either because the requested resource could not be found or because of bad syntax. This is most likely a client problem.
  • 500 Internal Server Error: There is an unspecific problem with the server which the service operator may not yet be aware of. Please check if there's already a bug report for this problem, and if not, file one.
  • 503 Service Unavailable: The server is temporarily down for maintenance, or there is a temporary problem with the server that the service operator is already aware of. Only file a bug report if this problem persists.

comment:3 Changed 6 years ago by tyseom

Cc: nusenu@… added

comment:4 Changed 3 years ago by karsten

Keywords: metrics-2018 added

comment:5 Changed 3 years ago by karsten

Owner: changed from hellais to metrics-team
Status: newassigned

comment:6 Changed 3 years ago by irl

Owner: changed from metrics-team to irl
Status: assignedaccepted

Moving these into my queue.

comment:7 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:8 Changed 3 years ago by irl

Owner: changed from irl to metrics-team
Status: acceptedassigned

Removing these tickets from my queue due to time constraints, and to let others have a go if they wish.

Guidelines for contributing to Relay Search can be found at:

comment:9 Changed 3 years ago by irl

Points: 0.2

comment:10 Changed 3 years ago by iwakeh

Please be aware of the start for RS into Metrics-Web integration and also refer to the branch in this comment of the parent ticket.

comment:11 Changed 7 months ago by karsten

We just resolved #32683 which is related to this ticket.

Note: See TracTickets for help on using tickets.