Bug #4513
closedTechnical reports timeout when no reports are available
Description
Checking the "technical reports" for a node that never had the chance to send some, will lead to the infamous popup "Couldn't connect to server"
A popup saying that no reports exists would be nicer.
Updated by François ARMAND about 10 years ago
- Assignee set to Nicolas CHARLES
I remember that we dealt with something like that... The problem was that some index was done on an irrelevant variable in the case when no report was ever sent.
Nicolas, does it rings a bell ?
Updated by François ARMAND about 10 years ago
- Status changed from New to Discussion
Updated by Nicolas CHARLES about 10 years ago
It does ring a bell; it was when a node didn't answer for a long time, then the index was irrelevant because heavily used on recent data, not older
We circumvented this by having an index on (node,executiontime), but it seems it is not enough
However, I'm not sure I can have a solution
Updated by Nicolas CHARLES almost 10 years ago
We do have an index on (nodeId, executionTimestamp) so it should not be that big an issue. I'm still trying to figure out what is happening
Updated by Benoît PECCATTE almost 9 years ago
- Category set to Web - Nodes & inventories
Updated by François ARMAND about 7 years ago
- Status changed from Discussion to Rejected
- Priority set to 0
This is not happening anymore with 3.1.x.
Updated by François ARMAND about 7 years ago
- Status changed from Rejected to New
- Assignee deleted (
Nicolas CHARLES)
So, we have reports that it is still happening in 3.1.15. I'm double checking and try to reproduce with last 3.1.x to be sure.
Updated by François ARMAND about 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
Updated by François ARMAND about 7 years ago
- Translation missing: en.field_tag_list set to Sponsored
Updated by François ARMAND about 7 years ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- User visibility changed from Getting started - demo | first install | level 1 Techniques to Operational - other Techniques | Technique editor | Rudder settings
So, it is not happening because there is no technical logs.
It may be only reproduced:
- if there is a lot of technical logs, since a long time,
- indexes are big and inefficient,
- the node has only old technical logs.
Updated by François ARMAND almost 7 years ago
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
- Priority changed from 0 to 36
Updated by François ARMAND over 5 years ago
- Status changed from New to Rejected
- Priority changed from 52 to 0
Cannot reproduced it anymore. Perhaps postres got better or something.