Exception when connecting power outlet #1081

Closed
opened 2025-12-29 16:28:38 +01:00 by adam · 1 comment
Owner

Originally created by @jwegner89 on GitHub (Jul 8, 2017).

Issue type: bug report

Python version: 3.4.5
NetBox version: 2.0.8

Updated from release 2.0.4 to 2.0.8. The service started normally, and I was able to perform other tasks without issue, e.g. adding prefixes, etc. I created a PDU from template (so it has the correct number of ports, etc) and clicked on the "connect" button when the exception detailed in power_outlet_exception.txt was thrown.

The system in RHEL 7.3 x86_64, with an NGINX 1.10.2 webserver proxying to a uWSGI 2.0.14 service managed by systemd. See the following attachments for the configuration files:
/etc/nginx/conf.d/netbox.is.depaul.edu.conf
/etc/uwsgi.d/netbox.ini
/etc/systemd/system/uwsgi-app@.socket
/etc/systemd/system/uwsgi-app@.service

The Netbox application uses a virtualenv to manage the packages locally. I know Python 3.4 is not a release that you build against, but it is the only version available through the EPEL repo.

Originally created by @jwegner89 on GitHub (Jul 8, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: bug report <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** 3.4.5 **NetBox version:** 2.0.8 <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> Updated from release 2.0.4 to 2.0.8. The service started normally, and I was able to perform other tasks without issue, e.g. adding prefixes, etc. I created a PDU from template (so it has the correct number of ports, etc) and clicked on the "connect" button when the exception detailed in [power_outlet_exception.txt](https://github.com/digitalocean/netbox/files/1132489/power_outlet_exception.txt) was thrown. The system in RHEL 7.3 x86_64, with an NGINX 1.10.2 webserver proxying to a uWSGI 2.0.14 service managed by systemd. See the following attachments for the configuration files: [/etc/nginx/conf.d/netbox.is.depaul.edu.conf](https://github.com/digitalocean/netbox/files/1132495/nginx_configuration.txt) [/etc/uwsgi.d/netbox.ini](https://github.com/digitalocean/netbox/files/1132498/uwsgi_configuration.txt) [/etc/systemd/system/uwsgi-app@.socket](https://github.com/digitalocean/netbox/files/1132503/systemd_socket.txt) [/etc/systemd/system/uwsgi-app@.service](https://github.com/digitalocean/netbox/files/1132504/systemd_service.txt) The Netbox application uses a virtualenv to manage the packages locally. I know Python 3.4 is not a release that you build against, but it is the only version available through the EPEL repo.
adam added the status: duplicate label 2025-12-29 16:28:38 +01:00
adam closed this issue 2025-12-29 16:28:38 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 10, 2017):

Duplicate of #1319. Will be fixed in v2.0.9.

@jeremystretch commented on GitHub (Jul 10, 2017): Duplicate of #1319. Will be fixed in v2.0.9.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1081