starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Netbox service crashes if traceparent header is provided #10669

New Issue
Closed
opened 2025-12-29 21:34:30 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:34:30 +01:00
Owner
Copy Link

Originally created by @mikemrm on GitHub (Jan 19, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.2.2

Python Version

3.12

Steps to Reproduce

This was originally discovered while deploying the netbox-chart in kubernetes, behind an ingress which has otel tracing enabled. Every request resulted in the service crashing and restarting, however accessing the service directly using port-forwarding worked without issue.

I was able to replicate using the default netbox-docker deployment with the latest version.

# clone netbox-docker for a simple deployment
$ git clone https://github.com/netbox-community/netbox-docker.git
$ cd netbox-docker

# start latest version and expose the service
$ VERSION=v4.2.2-3.1.0 docker compose -f docker-compose.yml -f docker-compose.test.override.yml up -d

# test to ensure service is responding
$ curl -s 127.0.0.1:8000/login/ | grep '<title>'
    <title>Home | NetBox</title>

# test with traceparent set
$ curl 127.0.0.1:8000/login/ -H 'traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01'
curl: (52) Empty reply from server

Expected Behavior

Request should succeed and return a login page.

Observed Behavior

Process exits and restarts.

...
netbox-1  | 127.0.0.1 - - [19/Jan/2025:06:04:51 +0000] "GET /login/ HTTP/1.1" 200 3270 "-" "curl/8.5.0"
netbox-1  | 2025/01/19 06:04:58 [alert] 7#7 process 260 exited on signal 11 (core dumped)
netbox-1  | 2025/01/19 06:04:58 [alert] 7#7 sendmsg(10, -1, -1, 1) failed (32: Broken pipe)
netbox-1  | 2025/01/19 06:04:58 [alert] 7#7 sendmsg(11, -1, -1, 1) failed (32: Broken pipe)
netbox-1  | 2025/01/19 06:04:58 [info] 549#549 router started
netbox-1  | 🧬 loaded config '/etc/netbox/config/configuration.py'
...
Originally created by @mikemrm on GitHub (Jan 19, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.2.2 ### Python Version 3.12 ### Steps to Reproduce This was originally discovered while deploying the netbox-chart in kubernetes, behind an ingress which has otel tracing enabled. Every request resulted in the service crashing and restarting, however accessing the service directly using port-forwarding worked without issue. I was able to replicate using the default netbox-docker deployment with the latest version. ```shell # clone netbox-docker for a simple deployment $ git clone https://github.com/netbox-community/netbox-docker.git $ cd netbox-docker # start latest version and expose the service $ VERSION=v4.2.2-3.1.0 docker compose -f docker-compose.yml -f docker-compose.test.override.yml up -d # test to ensure service is responding $ curl -s 127.0.0.1:8000/login/ | grep '<title>' <title>Home | NetBox</title> # test with traceparent set $ curl 127.0.0.1:8000/login/ -H 'traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01' curl: (52) Empty reply from server ``` ### Expected Behavior Request should succeed and return a login page. ### Observed Behavior Process exits and restarts. ``` ... netbox-1 | 127.0.0.1 - - [19/Jan/2025:06:04:51 +0000] "GET /login/ HTTP/1.1" 200 3270 "-" "curl/8.5.0" netbox-1 | 2025/01/19 06:04:58 [alert] 7#7 process 260 exited on signal 11 (core dumped) netbox-1 | 2025/01/19 06:04:58 [alert] 7#7 sendmsg(10, -1, -1, 1) failed (32: Broken pipe) netbox-1 | 2025/01/19 06:04:58 [alert] 7#7 sendmsg(11, -1, -1, 1) failed (32: Broken pipe) netbox-1 | 2025/01/19 06:04:58 [info] 549#549 router started netbox-1 | 🧬 loaded config '/etc/netbox/config/configuration.py' ... ```
adam closed this issue 2025-12-29 21:34:30 +01:00
adam commented 2025-12-29 21:34:31 +01:00
Author
Owner
Copy Link

@mikemrm commented on GitHub (Jan 19, 2025):

After further digging. I've discovered this to be an issue with nginx unit v1.34.0 used within the docker container. Running the test server worked just fine. I've confirmed this issue has been fixed in nginx unit v1.34.1. Apologies for the mix up.

Related issue: https://github.com/nginx/unit/issues/1523

@mikemrm commented on GitHub (Jan 19, 2025): After further digging. I've discovered this to be an issue with nginx unit v1.34.0 used within the docker container. Running the test server worked just fine. I've confirmed this issue has been fixed in nginx unit v1.34.1. Apologies for the mix up. Related issue: https://github.com/nginx/unit/issues/1523
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10669
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?