Error upgrading from 3.4.8 to 3.5.0 #12411
-
Hello, after i upgraded my netbox-docker version from 3.4.8 to 3.5.0 i have this error Server Error The complete exception is provided below: <class 'http.client.RemoteDisconnected'> Remote end closed connection without response Python version: 3.10.6 and impossible to connect to my nextbox anymore |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 1 reply
-
I did a small try, downgrading back to version 3.4.8 and everything is working fine again, so i would really know from where the probleme is comming from, any ideas ? any one ? Thanks in advance for your help |
Beta Was this translation helpful? Give feedback.
-
I could upgrade to the 3.4.9 with no probleme, but i can not upgrade to the 3.5.0 |
Beta Was this translation helpful? Give feedback.
-
Please can you provide a full backtrace: set ADMINS and EMAIL in configuration.py, and/or set DEBUG=True. Given that this is a HTTP client request, I wondered if perhaps you were caught by new census feature in 3.4.9:
However, since you say 3.4.9 works, that's probably not it - unless there's an intermittent problem with connectivity to the census server. A backtrace will make it clear one way or the other; and/or you could try setting CENSUS_REPORTING_ENABLED=False |
Beta Was this translation helpful? Give feedback.
-
Hello, thank you for your response, i tried to set but that does not change, the probleme is still there, i provide you my full backtrace as asked Template error: 34 : {% render_widget widget %} 35 : 36 : 37 : 38 : Traceback (most recent call last): Exception Type: RemoteDisconnected at / |
Beta Was this translation helpful? Give feedback.
-
In v3.5.0, a new configurable dashboard with widgets was introduced. It looks like one of the default widgets tries to make Internet connections, and is raising exceptions for you. I see that your traceback is within RSSFeedWidget:
There is a similar problem at #12384 and #12421. v3.5.1 will include a fix with a 3-second timeout, and it looks like it also catches There is a suggested solution here to change your DEFAULT_DASHBOARD setting (however I don't have a v3.5 instance here to test with). |
Beta Was this translation helpful? Give feedback.
-
thank you very much for your answer, my server (that hold the netbox docker) as no connection over the internet, it is probably that |
Beta Was this translation helpful? Give feedback.
-
I did a lot of new test, there are my results... I tried this #12384 but that does not solve the probleme it makes an error still in the rss.feed even if i am not using it in the I tried to create a fresh new installation of netbox into my portainer using a stack with a docker-compose file if i comment the line 34 in the widget.html file like this {#% render_widget widget %#} and then recreate the whole stack everything is working fine, netbox open up and display a screen with the new interface of the 3.5.0 with all the widgets empty, but all my datas are there So for me, i think, but i am not sur at all, the probleme is not comming from an internet connection, but really comming from the new dasboard of the 3.5.0 when netbox is trying to render the widgets |
Beta Was this translation helpful? Give feedback.
-
That is what i did, thank for your support |
Beta Was this translation helpful? Give feedback.
-
Upgraded to V3.5.1 and every things is working fine now |
Beta Was this translation helpful? Give feedback.
In v3.5.0, a new configurable dashboard with widgets was introduced. It looks like one of the default widgets tries to make Internet connections, and is raising exceptions for you. I see that your traceback is within RSSFeedWidget:
There is a similar problem at #12384 and #12421. v3.5.1 will include a fix with a 3-second timeout, and it looks like it also catches
requests.exceptions.RequestException
; however this might not fix it for you since I don't know if the exception you see (RemoteDisconnected) is a subclass of RequestException. I think OSError and RuntimeError should be caught.There…