Need help on finding a full python traceback

[mwobst]

Hello,

because of a major change within our NetBox deployment, I rolled out a test instance with netbox docker. Sadly on some pages errors happens, but in the browser I only see the last line of the Python traceback. With local deployment, these errors do not happen.

In env/netbox.env I have the lines DEBUG=1 and even DEVELOPER = True … but this changes nothing. docker logs shows nothing (accept the access log lines including the one for 500 error), and I have no idea where to search. Has anyone an idea, how to find the actual traceback or what setting I’m missing here?

[sebix]

Have you found a solution? I'm struggling with the same.

All I get from netbox is the error message in the browser:

<class 'django.db.utils.ProgrammingError'>

column extras_customfield_object_types.objecttype_id does not exist
LINE 1: ...ustomfield_object_types"."customfield_id") WHERE ("extras_cu...
                                                             ^

The docker logs only show the 500 and nothing else. Searching the code for the mentioned columns and tables doesn't work either, as the models don't use the names directly.

[NNeujahr]

got the exact same issue, did you find a solution?

[mwobst]

See my answer below, try "DEBUG = True" instead of "DEBUG = 1", I’m pretty sure this changed the behavior.

[mwobst]

Actually … I forgot this issue completely :D
Anyway, in the meantime I had another error to analyze, same problem … but this time I managed to get the full traceback and I believe that "DEBUG = True" is required (changed from "DEBUG=1"). Just looked into the file netbox.env and I don’t see anything else that might be related … pretty sure the code hard-checks for the actual True, so 1 is probably not considered True.

If this works for you too, then please answer. We could close the issue then.