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.

Sign up for GitHub

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

Jump to bottom

When trying to obtain data, cacti should not long Transport Read errors #5199

Closed
TheWitness opened this issue Jan 27, 2023 · 0 comments
Closed

When trying to obtain data, cacti should not long Transport Read errors #5199

TheWitness opened this issue Jan 27, 2023 · 0 comments
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone
v1.2.24

Comments

@TheWitness
Copy link
Member

Describe the bug

When attempting fgets() calls in Cacti that file due to a lack of a response, errors are triggered in the Cacti log.

To Reproduce

Steps to reproduce the behavior:

  1. Install RouterConfigs

  2. Add some Routers or Switches

  3. Attempt to manually download a backup

  4. See error

Expected behavior

These errors should be masked by default.
@TheWitness TheWitness added bug Undesired behaviour confirmed Bug is confirm by dev team labels Jan 27, 2023
@TheWitness TheWitness added this to the v1.2.24 milestone Jan 27, 2023
TheWitness added a commit that referenced this issue Jan 27, 2023
@TheWitness
Fixing #5199 - fgets errors
22d96d0 
Failures to call fgets generate errors in the Cacti.log
@TheWitness TheWitness added resolved A fixed issue porting required Requires porting to develop labels Jan 27, 2023
@netniV netniV changed the title Failures to call fgets generate errors in the Cacti.log When trying to obtain data, cacti should not long Transport Read errors Feb 15, 2023
@TheWitness TheWitness removed the porting required Requires porting to develop label Feb 20, 2023
@TheWitness TheWitness mentioned this issue Feb 20, 2023
Merged
@github-actions github-actions bot locked and limited conversation to collaborators May 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Milestone
v1.2.24
Development

No branches or pull requests
1 participant
@TheWitness