Project

General

Profile

Actions
Copy link

Bug #15888

closed

Batch which cleans log reports should not start if LDAP is unavailable

Added by François ARMAND about 5 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
old 6.1 issues to relocate
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

Today, we got that in log: 

[2019-10-07 15:34:29] ERROR scheduledJob - Error when trying to get maximun run interval, defaulting to  5 minutes. Error was:

This is a problem since we don't have the cause of the error. It was most likely because the LDAP access was not possible.
But that show an other problem: as we don't reevaluate run interval once the batch started, we should really not start without knowing what are the run interval.

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #15890: Batch which deletes log reports displays an error when default run interval is not definedReleasedNicolas CHARLESActions
Related to Rudder - Bug #15802: Clean up reports with log_* types more than once a dayReleasedNicolas CHARLESActions
Actions
Copy link

Also available in: Atom PDF