Issues with my platform - Due a Recovery

[luisgo1411]

Hi recently I have to do a full recovery of the platform and in under this section mynetboxcompany.net/extras/config-contexts/148/edit/ when i try to save any change also the description i got this error:

<class 'RecursionError'>

maximum recursion depth exceeded in comparison

Python version: 3.9.17

NetBox version: 3.5.9
Plugins:
netbox_bgp: 0.10.2

Any help would be very appreciated!

[pheus]

Hi there!
Sorry you’re running into this after a full recovery. A RecursionError like this is usually a symptom of something specific in the data being processed, but to narrow it down we’ll need a bit more context.

Could you share a little more detail?

• How did you perform the recovery (DB restore only, full VM restore, fresh install + DB restore, etc.)?
• Are the OS / Python / NetBox / plugin versions exactly the same as they were before the recovery?
• Does the error happen for all Config Contexts, or only this specific one (ID 148)?
• If it’s only ID 148: did it work before, and can you share the (sanitized) Config Context data/content? Deeply nested structures or certain patterns can sometimes trigger recursion issues.
• Can you paste the full traceback from the NetBox logs? (The UI often only shows the exception type, but the logs usually point to the exact code path.)

Since you’re running netbox_bgp, I’d also suggest a quick isolation test:

• Temporarily disable the plugin (or start NetBox without it) and try saving the Config Context again. If the error disappears, it strongly suggests a plugin interaction or compatibility issue.

As a last resort, if that single Config Context is corrupted and blocking progress, I’d avoid editing the database directly if possible. Instead:

• Take a database backup first, then remove/update the object via the NetBox API or Django shell (safer than manual SQL).

If you can provide the traceback and confirm whether it’s only happening for ID 148, we can usually pinpoint the cause pretty quickly.

Out of curiosity:
Why are you using this very old version of NetBox?

[luisgo1411]

• Was a full VM restore.

• Yes the plugins are exactly as they were.

• Yes they happen for most of them.

• I already make some querys in the DB and I dont find any recursion issues, this is an example for /extras/config-contexts/147/edit/
  Name: Catalyst 2960, 2960C, 2960CX, 2960S, 2960G
  Data: {
  "softwareVersions": {
  "description": "15.2(2)E9 required for 2960S, 2960G. 15.2.7E11 required for 2960CX, 2960C",
  "n-1": [
  "15.2.7E7 for 2960CX",
  "15.2(2)E9 for 2960C"
  ],
  "patches": [],
  "standard": [
  "15.2(2)E9",
  "15.2.7E11"
  ],
  "stdReleaseDate": "2025-02-28"
  }
  }
  Device Types: Catalyst 2960-12PC, Catalyst 2960CX-8TC, Catalyst 2960G-48TC

• This was the relevant log finded: Unable to delete object. 2 dependent objects were found:

• I already try to deactivate the plugin and didnt work.

• For the last resort can you provide me the detail steps to make the backup of the database, and the the delete and restore of the data?

• And for the last question, we have a legacy architecture with patroni (unsupported by you) I only have 1 year here and Im working in a migration plan to remove it, and take away the db from the same box, and make a safe upgrade of the platform.

[luisgo1411]

When I create a new one without device types works good, but when I create a new one with the device types send me the same error. @pheus

[pheus]

Hi! Thanks for the additional details.

Since this was a full VM restore, it’s very unlikely that the restore itself “introduced” a new recursion problem in the database.

What you’re hitting matches a NetBox core bug that can throw:

RecursionError: maximum recursion depth exceeded in comparison

…specifically when a Config Context is assigned to one or more Device Types (the Config Context scoping/assignment).

This is tracked upstream here:

• GitHub issue: Config Context Fails to assign to "Device types" #13757

And it was fixed in NetBox v3.6.2 (see the release notes / the v3.6.2 tag):

• Release notes (v3.6.2): https://netboxlabs.com/docs/netbox/release-notes/version-3.6#v362-2023-09-20
  (Under v3.6.2, look for: “Fix RecursionError exception when assigning config context to a device type” / Config Context Fails to assign to "Device types" #13757)
• GitHub release tag: https://github.com/netbox-community/netbox/releases/tag/v3.6.2

Recommendation: upgrade to ≥ 3.6.2 (or ideally a newer supported release), after confirming plugin compatibility and following the version-specific upgrade steps.

Regarding Patroni: I don’t have hands-on experience with Patroni, so I’m not comfortable giving Patroni-specific operational advice. For general PostgreSQL backup/restore guidance (pg_dump / pg_restore and other approaches), the official documentation is here:

• Backup & Restore overview: https://www.postgresql.org/docs/current/backup.html
• pg_dump: https://www.postgresql.org/docs/current/app-pgdump.html
• pg_restore: https://www.postgresql.org/docs/current/app-pgrestore.html

[moseisleydk]

The recursive seems to be:

/opt/netbox/venv/lib/python3.12/site-packages/debug_toolbar/panels/cache.py, line 40, in wrapper

this is repeated 40 times in the Error Debug:

/opt/netbox/venv/lib/python3.12/site-packages/django/core/handlers/exception.py, line 55, in inner
/opt/netbox/netbox/netbox/middleware.py, line 221, in call
/opt/netbox/netbox/netbox/config/init.py, line 28, in get_config
/opt/netbox/netbox/netbox/config/init.py, line 48, in init
/opt/netbox/netbox/netbox/config/init.py, line 71, in _populate_from_cache

/opt/netbox/venv/lib/python3.12/site-packages/debug_toolbar/panels/cache.py, line 40, in wrapper
/opt/netbox/venv/lib/python3.12/site-packages/debug_toolbar/panels/cache.py, line 40, in wrapper
/opt/netbox/venv/lib/python3.12/site-packages/debug_toolbar/panels/cache.py, line 40, in wrapper

40 x

[moseisleydk]

ok, I have added some redis changes from https://github.com/netbox-community/netbox-docker/blob/release/docker-compose.yml to my own docker compose. I will be back..