Project

General

Profile

Actions

Bug #15713

closed

[Controller] Internal error not logged

Added by Peter Amstutz over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Release relationship:
Auto

Description

During development, I introduced an error that caused controller to return a 503 error.

However, the logging is confusing:

  • nginx turns the 503 error from controller into a 500 error, so searching the controller logs for a 500 status error comes up empty
  • The error message that is returned to the client is not emitted in the log.

This is similar to #15606, another situation (in keep-web) where the error message is returned to the client but missing from the log.

Proposed fix:

  • Tweak nginx so it doesn't change the status code and/or return a different status code so that what is seen by the client and what is logged are consistent.
  • Ensure that error messages are always emitted in the request log

Subtasks 1 (0 open1 closed)

Task #15746: Review 15713-controller-error-logResolvedTom Clegg10/24/2019Actions

Related issues

Related to Arvados - Bug #15606: [keep-web] logging doesn't include error messagesResolvedTom Clegg10/29/2019Actions
Related to Arvados - Bug #15521: [keepstore] error reporting improvementsResolvedTom Clegg10/31/2019Actions
Actions

Also available in: Atom PDF