-
Notifications
You must be signed in to change notification settings - Fork 164
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
500 Error with Physical Interface List on 6.3.0 #820
Comments
Hey @ichilton - It looks like you have an interface without a customer? I.e. the bug may be more the data than the code. Not sure how you could find this situation via the UI tbh - maybe manual database editing? Try running the following SQL: SELECT
pi.id AS piid,
vi.id AS viid,
c.id AS cid
FROM
physicalinterface AS pi
LEFT JOIN virtualinterface AS vi ON vi.id = pi.virtualinterfaceid
LEFT JOIN cust AS c ON c.id = vi.custid
WHERE
c.id IS NULL If you get results, that's the issue. If you don't pare it back to: SELECT
pi.id AS piid
FROM
physicalinterface AS pi
WHERE
pi.virtualinterfaceid IS NULL and any results there will be the problem (physical interface without a virtualinterface). If this doesn't solve it, can you post the storage/logs/laravel.log snippet that will be generated which you trigger this? If it does solve it, we'll look about implementing FKs on these fields in the DB. There should be there really and would be if we were starting fresh rather than working on the core of a schema that is now about 20 years old (but proven and robust like its creator, @nickhilliard). |
Hi, Thanks for that - There was one match:
Looking at historical data from the dev copy, and that date and time in our support tickets, it looks like this occurred when we deleted a resold customer. I think the customer resold port was on virtual interface 633, with the switchportid of 2182. The fanout port was on virtual interface 634, physical interface 1032 with the switchportid of 2186. (From dev copy of database):
So I'm guessing that for some reason the associated fanout port wasn't cleaned up correctly when we deleted the resold customer port. |
ISSUE TYPE
Bug Report
OS
Ubuntu focal
VERSION
ENVIRONMENT
SUMMARY
After upgrading to 6.3.0, we see the following error when going to:
https://portal.ourdomain.net/interfaces/physical/list
The page gets partially rendered and fails with a 500 error:
Thanks,
Ian
The text was updated successfully, but these errors were encountered: