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

Housekeeping task output triggers emails via anacron #11201

New Issue
Closed
opened 2025-12-29 21:41:52 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:41:52 +01:00
Owner
Copy Link

Originally created by @aseques on GitHub (May 20, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.0

Python Version

3.10

Steps to Reproduce

With the housekeeping script that's default to netbox install, the script is echoing text to stdout, since all cron's output is redirected to email, I am getting a daily mail with the result of the housekeeping (because I have a mailer configured to my address)

88565e8f68/contrib/netbox-housekeeping.sh (L2)

If the script was outputting to /dev/null it would only sent emails when something is throwing errors, otherwise discard them

/opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py housekeeping >dev/null

Another option would be to write the output to a log file:

/opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py housekeeping >/var/log/netbox/housekeeping.log

Expected Behavior

There should be only emails when there are errors, otherwise the output should be logged or discarded only.

Observed Behavior

A mail is being sent every time the script is run through crontab

Originally created by @aseques on GitHub (May 20, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.0 ### Python Version 3.10 ### Steps to Reproduce With the housekeeping script that's default to netbox install, the script is echoing text to stdout, since all cron's output is redirected to email, I am getting a daily mail with the result of the housekeeping (because I have a mailer configured to my address) https://github.com/netbox-community/netbox/blob/88565e8f680a5b64f1a22b67f007f15acf8f1373/contrib/netbox-housekeeping.sh#L2 If the script was outputting to /dev/null it would only sent emails when something is throwing errors, otherwise discard them > /opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py housekeeping >dev/null Another option would be to write the output to a log file: > /opt/netbox/venv/bin/python /opt/netbox/netbox/manage.py housekeeping >/var/log/netbox/housekeeping.log ### Expected Behavior There should be only emails when there are errors, otherwise the output should be logged or discarded only. ### Observed Behavior A mail is being sent every time the script is run through crontab
adam added the type: bug label 2025-12-29 21:41:52 +01:00
adam closed this issue 2025-12-29 21:41:52 +01:00
adam commented 2025-12-29 21:41:52 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (May 28, 2025):

I'd be happy to contribute this!

@pheus commented on GitHub (May 28, 2025): I'd be happy to contribute this!
adam commented 2025-12-29 21:41:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 5, 2025):

This isn't a NetBox bug: The behavior of cron is entirely dependent on how it's configured. The shell script which ships with NetBox is minimal implementation intended to be used by system administrators as a reference. Customization of the task itself it outside the scope of NetBox's documentation.

@jeremystretch commented on GitHub (Jun 5, 2025): This isn't a NetBox bug: The behavior of cron is entirely dependent on how it's configured. The [shell script](https://github.com/netbox-community/netbox/blob/main/contrib/netbox-housekeeping.sh) which ships with NetBox is minimal implementation intended to be used by system administrators as a reference. Customization of the task itself it outside the scope of NetBox's documentation.
adam commented 2025-12-29 21:41:53 +01:00
Author
Owner
Copy Link

@aseques commented on GitHub (Jun 5, 2025):

Hi @jeremystretch it's more about having a sensible default (that doesn't trigger unnecessary noise), than a bug per se.
Since it's part of the upgrade documentation it get ovewritten on every new release (see here)

@aseques commented on GitHub (Jun 5, 2025): Hi @jeremystretch it's more about having a sensible default (that doesn't trigger unnecessary noise), than a bug per se. Since it's part of the upgrade documentation it get ovewritten on every new release (see [here](https://netboxlabs.com/docs/netbox/installation/upgrading/#6-verify-housekeeping-scheduling))
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 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#11201
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?