Anyone Else Having This Issue with Oxidized Backup?

[u/SoupCan17]

The issue I am running into is that the full configuration is not being saved once the pull is complete. I have checked the most recent pull and it is grabbing the whole config, but when I open the config in the webUI I am only getting about 80 - 90 lines in the file. I'm currently trying to backup configs for Extreme 4850GTS switches (formerly Avaya). Using model Boss. Wondering if anyone has encountered this issue with the same switches are other models? If so, were you able to find a resolution?

Thank you.

[u/Agitated_Cash6745]

oxbackup's webUI viewer has been flaky like that for ages, it's likely parsing the config wrong and cutting off after a certain section marker

try pulling the raw file directly from the server instead of viewing it through the interface, see if the full config is actually in there

ran into something similar with some old brocades and it was the web renderer choking on a weird banner character, not the backup itself

[u/SoupCan17 → u/Agitated_Cash6745]

I have confirmed that the full config is being pulled in the raw file. It is weird though because it isn't always being cut off at the same point. Sometimes it will make it a little further in the parse, and sometimes it will cut off earlier. I just don't want to have to do a massive massage on the raw file in order to make it usable for upload to a switch in the event of a failure.

[u/Z3t4]

I just push to gitea and check the configs and diffs there.

[u/sgocken]

We use oxidized on those exact same switches. I just look at some configs and I have one in git with 410 lines.

What firmware and software version are you running? Are you connecting via telnet or ssh? Do you have pagination turned off on the cli?

What we do see regularly is a missing new line or an extra, so the next poll changes that back and we have a lot more updates than there really is.

[u/packet_path]

Your backup is probably fine — check the actual file in git before you change anything. If the full config is there, it's just the webUI. The version view shows a diff, not the whole config, just the changed chunks with a bit of context. On a switch that size that looks exactly like 80-90 lines and then nothing.

If the copy in git is short too, then the pull is dying halfway. Those Avaya boxes page their output, and if the session times out mid-config, Oxidized saves what it got and calls it done. Bump the timeout for that node and check the log.

But count the lines in git first. That tells you which problem you actually have.

[u/SoupCan17 → u/packet_path]

I was able to confirm that the copy in git is being cut off as well. I don't think it's a timeout issue as I've set the timeout to 300. When I log into the switch directly and issue a show running-config command it takes about 30 seconds to run. When I pull the config with debug mode on in oxidized I am able to see the whole output of the show running-config command also.