Project

General

Profile

Actions

Bug #15888

closed

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

Added by François ARMAND over 4 years ago. Updated 7 months ago.

Status:
Resolved
Priority:
N/A
Category:
Web - Compliance & node report
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 open2 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 #1

Updated by François ARMAND over 4 years ago

  • Related to Bug #15890: Batch which deletes log reports displays an error when default run interval is not defined added
Actions #2

Updated by François ARMAND over 4 years ago

  • Related to Bug #15802: Clean up reports with log_* types more than once a day added
Actions #3

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions #4

Updated by Alexis Mousset about 4 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions #5

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions #6

Updated by François ARMAND almost 4 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 28

It does not seems too grave since it just means that that run will not proceed.

Actions #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions #8

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.19 to 5.0.20
  • Priority changed from 28 to 27
Actions #9

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 5.0.20 to 797
Actions #10

Updated by Benoît PECCATTE almost 3 years ago

  • Target version changed from 797 to 6.1.14
Actions #11

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #12

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #13

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #16

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #17

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #18

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #19

Updated by François ARMAND 7 months ago

  • Status changed from New to Resolved
  • Priority changed from 27 to 0
  • Regression set to No

That batch is now delayed to star after LDAP connection was checked.

Actions

Also available in: Atom PDF