-
Notifications
You must be signed in to change notification settings - Fork 918
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
Oxidized is in a loop with a device? #3242
Labels
Comments
Please give more context:
It seems like a configuration flapping to me, oxidized just informs you that the configuration changed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey all,
I believe something weird is going on with this device(s) that Oxidized is pulling. We are getting numerous emails of config changes for a device that seems to be in a loop. For instance, one email for the switch will say this -->
Then, the next email will say this -->
Then, after those 2 being sent, it'll send another email that says this -->
And then it just keeps on going, and it's not just that interface it does this with but the overall switch config. Is there a database that Oxidized is using to hold the pulled configurations of a device that gets used for comparison against newly pulled configs for that device? Maybe if I remove the existing file, the next time it'll pull will be that device's "first time"? But I assume that means I'll lose all configuration iterations that have occurred which can be seen on our Oxidized-Web.
Any ideas or tips?
Thanks!
The text was updated successfully, but these errors were encountered: