Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Earlier versions of RRDTool do not correctly ignore previous updates #4321

Closed
TheWitness opened this issue Jun 25, 2021 · 0 comments
Closed
Labels
bug Undesired behaviour resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

TheWitness commented Jun 25, 2021

Describe the bug

RRDtool versions less than 1.5 do not have the 'skip' option to silently ignore previous updates. This can cause a gap in graphs somewhat randomly.

To Reproduce

It's not easy to reproduce, but in Cacti 1.2.17, we/I inadvertently removed the Data Source locking function that prevented this type of behavior. Though we recommend you get off old RRDtool version 1.4 and earlier versions, we will make a fix to re-introduce that locking functionality.

Expected behavior

Cacti needs to work.

@TheWitness TheWitness added the bug Undesired behaviour label Jun 25, 2021
@TheWitness TheWitness added this to the 1.2.18 milestone Jun 25, 2021
TheWitness added a commit that referenced this issue Jun 25, 2021
RRDtool Updates might cause gaps due to lock of locking during RRDTOOL updates when using RRDtool 1.4 or Less
@TheWitness TheWitness added the resolved A fixed issue label Jun 25, 2021
@netniV netniV closed this as completed Jun 30, 2021
@netniV netniV changed the title RRDtool Updates might cause gaps due to lock of locking during RRDTOOL updates when using RRDtool 1.4 or Less Earlier versions of RRDTool do not correctly ignore previous updates Jul 4, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants