Project

General

Profile

Actions

Bug #11037

closed

Missing agent reports after Rudder server restart

Added by Dmitry Svyatogorov almost 4 years ago. Updated over 3 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
93
Tags:

Description

Rudder 4.1.3
After doing restart ("service rudder-jetty restart"), last reports received before restart looks to be missed.
All listed nodes are shown in "No report"|"Missing reports" state until new report will be processed.
Expect to store|retrieve the last versions from db.


Related issues

Related to Rudder - Bug #10456: Several core features don't work anymore with more than 1000 nodesReleasedAlexis MOUSSETActions
Has duplicate Rudder - Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3RejectedActions
Actions #1

Updated by François ARMAND almost 4 years ago

  • Related to Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3 added
Actions #2

Updated by François ARMAND almost 4 years ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 70

Thanks for reporting. It may be an other occurence of #10881.
In #10881, we thought it was because the expected configuration was archived (and so the compliance wasn't able to find it back and so it was takin an other one at random), but if it happens after a restart, it can't be just that.

Actions #3

Updated by Nicolas CHARLES almost 4 years ago

I had a similar one, when after restart, I got a random id identified as last run (which was wrong)

Actions #4

Updated by Alexis MOUSSET almost 4 years ago

  • Subject changed from Missing agent reports after Ruder server restart to Missing agent reports after Rudder server restart
Actions #5

Updated by François ARMAND almost 4 years ago

  • Assignee set to François ARMAND
Actions #6

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 70 to 69
Actions #7

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 4.1.6 to 4.1.7
Actions #8

Updated by François ARMAND over 3 years ago

  • Tags set to Sponsored
  • Priority changed from 69 to 93

We have now several users who reported that, and even if not really "critical", it is scary and extremelly visible.

Actions #9

Updated by François ARMAND over 3 years ago

  • Status changed from New to In progress
Actions #10

Updated by Nicolas CHARLES over 3 years ago

  • Related to Bug #10456: Several core features don't work anymore with more than 1000 nodes added
Actions #11

Updated by Nicolas CHARLES over 3 years ago

  • Assignee changed from François ARMAND to Nicolas CHARLES
Actions #12

Updated by François ARMAND over 3 years ago

  • Related to deleted (Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3)
Actions #13

Updated by François ARMAND over 3 years ago

  • Has duplicate Bug #10881: Almost nodes become in "red state" after upgrading from 4.0.2 to 4.1.3 added
Actions #14

Updated by Nicolas CHARLES over 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1730
Actions #15

Updated by Nicolas CHARLES over 3 years ago

  • Status changed from Pending technical review to Pending release
Actions #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.7 and 4.2.0~rc1 which were released today.

Actions

Also available in: Atom PDF