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

Report that timed out is shown as running #6134

New Issue
Closed
opened 2025-12-29 19:37:09 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:37:09 +01:00
Owner
Copy Link

Originally created by @seros1521 on GitHub (Feb 22, 2022).

NetBox version

v3.1.8

Python version

3.9

Steps to Reproduce

Run any report that runs longer than the RQ_DEFAULT_TIMEOUT timeout.

Expected Behavior

The report should be in the 'Errored' state after the timeout has expired.

Observed Behavior

Report in the 'running' state (both in the main UI and in the administrative UI).

Originally created by @seros1521 on GitHub (Feb 22, 2022). ### NetBox version v3.1.8 ### Python version 3.9 ### Steps to Reproduce Run any report that runs longer than the RQ_DEFAULT_TIMEOUT timeout. ### Expected Behavior The report should be in the 'Errored' state after the timeout has expired. ### Observed Behavior Report in the 'running' state (both in the main UI and in the administrative UI).
adam added the type: bugstatus: needs owner labels 2025-12-29 19:37:09 +01:00
adam closed this issue 2025-12-29 19:37:09 +01:00
adam commented 2025-12-29 19:37:10 +01:00
Author
Owner
Copy Link

@minitriga commented on GitHub (Feb 23, 2022):

Unfortunately I was not able to replicate this error on v3.1.8 every time the report ran longer than the RQ_DEFAULT_TIMEOUT variable.

Both the Reports and Admin UI's reported an errored state.

image

image

image

@minitriga commented on GitHub (Feb 23, 2022): Unfortunately I was not able to replicate this error on `v3.1.8` every time the report ran longer than the `RQ_DEFAULT_TIMEOUT` variable. Both the Reports and Admin UI's reported an `errored` state. ![image](https://user-images.githubusercontent.com/26367336/155376664-c9afc759-88fb-410a-8136-16fc44f9d3f3.png) ![image](https://user-images.githubusercontent.com/26367336/155376709-659e7a11-1b6a-4b66-abb2-db2e83563c40.png) ![image](https://user-images.githubusercontent.com/26367336/155376789-dd13c3e6-9524-4b22-a7af-61e97f7cc12b.png)
adam commented 2025-12-29 19:37:10 +01:00
Author
Owner
Copy Link

@seros1521 commented on GitHub (Feb 24, 2022):

I get different results on different instances. On the test - correct, on the production - no. According to the netbox code, everything seems to be normal. The timeout exception is correctly logged, but the result is not saved. There might be an error in the process of saving the result of the task. Maybe a large size of the report results? But there is nothing in the logs to indicate this. I will investigate the issue further.

@seros1521 commented on GitHub (Feb 24, 2022): I get different results on different instances. On the test - correct, on the production - no. According to the netbox code, everything seems to be normal. The timeout exception is correctly logged, but the result is not saved. There might be an error in the process of saving the result of the task. Maybe a large size of the report results? But there is nothing in the logs to indicate this. I will investigate the issue further.
adam commented 2025-12-29 19:37:10 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 2, 2022):

Most likely what is happening is whatever report you are running is trying to Serialize a raw object (Prefix, etc) from what was successful and this will normally fail. You should convert the object to json first. I had this exact problem when writing scripts and it is because the Serializer for serializing the data cannot handle the raw object

@DanSheps commented on GitHub (Mar 2, 2022): Most likely what is happening is whatever report you are running is trying to Serialize a raw object (Prefix, etc) from what was successful and this will normally fail. You should convert the object to json first. I had this exact problem when writing scripts and it is because the Serializer for serializing the data cannot handle the raw object
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 status: needs owner type: bug
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#6134
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?