Stale connection not removed after cable update #12930
Unanswered
tfboy
asked this question in
Help Wanted!
Replies: 1 comment 1 reply
-
I don't know if this is a possible problem but the cable traces are cached, maybe this has gotten out of sync somehow. Does running netbox/manage.py trace_paths make any change to the behavior? If this fixes it then you can troubleshoot how the update trigger didn't get fired or failed, and if this doesn't fix it the issue lies elsewhere.
sudo -u netbox /opt/netbox/current/venv-py3/bin/python /opt/netbox/current/netbox/manage.py trace_paths --no-input
—
Mark Tinberg ***@***.***>
Division of Information Technology-Network Services
University of Wisconsin-Madison
…________________________________
From: tfboy ***@***.***>
Sent: Monday, June 19, 2023 4:33 AM
To: netbox-community/netbox ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [netbox-community/netbox] Stale connection not removed after cable update (Discussion #12930)
First time I've seen this in a long time.
Running Netbox 3.5.1
I had a cable connecting one device to the other (server NIC to a network switch port).
I edited the cable as I needed to move the port it's connected to on the switch side.
The switch now shows the new port number with the cable number and the "S" trace button enabled.
But the old port still shows the "connection data". Cable and trace functions are gone.
[image]<https://user-images.githubusercontent.com/6972726/246788996-0d7c25f2-5245-4a03-b812-bdf41eabf661.png>
I've tried a reboot and run a mange.py healthcheck and I think everything is OK.
python3 netbox/manage.py housekeeping
[*] Clearing expired authentication sessions
Sessions cleared.
[*] Checking for expired changelog records
No expired records found.
[*] Checking for expired jobs
No expired records found.
[*] Checking for latest release
Skipping: RELEASE_CHECK_URL not set
Finished.
I did recently play around with this switch as it's part of a virtual chassis. I don't know if the updates have caused some kind of corruption or not cleared a field meaning this connection seems to remain.
I can't figure out how to clear it!
Any ideas?
—
Reply to this email directly, view it on GitHub<#12930>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAS7UM4UI5I47OD34C6UUKDXMAMHFANCNFSM6AAAAAAZLVGTAA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First time I've seen this in a long time.

Running Netbox 3.5.1
I had a cable connecting one device to the other (server NIC to a network switch port).
I edited the cable as I needed to move the port it's connected to on the switch side.
The switch now shows the new port number with the cable number and the "S" trace button enabled.
But the old port still shows the "connection data". Cable and trace functions are gone.
I've tried a reboot and run a mange.py healthcheck and I think everything is OK.
I did recently play around with this switch as it's part of a virtual chassis. I don't know if the updates have caused some kind of corruption or not cleared a field meaning this connection seems to remain.
I can't figure out how to clear it!
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions