Project

General

Profile

Actions
Copy link

Bug #1466

closed

Rudder should halt on fatal errors during initialization

Added by Jonathan CLARKE about 13 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
4
Assignee:
-
Category:
Web - Maintenance
Target version:
Ideas (not version specific)
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Currently, logs are very confusing in case an error occurs during startup of the application (ie, the LDAP server could not be contacted) because the error message appears, then many other errors appear, as Rudder does not halt on the first error.

This should be modified so that Rudder halts immediately, and the last log line contains only the real error message.

Related issues 2 (1 open — 1 closed)

Related to Rudder - Architecture #17180: Compliance incorrectly computed with old reports or runs not sent in node chronological orderNewFrançois ARMANDActions
Is duplicate of Rudder - Bug #1974: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayedReleasedNicolas CHARLESActions
Actions
Copy link

Also available in: Atom PDF