fix: service template crashes on empty AURORA_EXTRA_ARGS#8
Merged
Neo23x0 merged 1 commit intoNextron-Labs:masterfrom Mar 16, 2026
Merged
Conversation
Two bugs in the systemd service template:
1. Empty AURORA_EXTRA_ARGS causes Aurora to crash on startup.
systemd passes ${AURORA_EXTRA_ARGS} as a literal empty string
argument, which cobra interprets as an unknown subcommand:
error: unknown command "" for "aurora"
Fix: wrap ExecStart in bash -c with unquoted $AURORA_EXTRA_ARGS
so empty vars expand to nothing (standard shell word splitting).
2. Wrong default rules path: the unit file had
/opt/aurora-linux/sigma-rules/rules/linux but the install script
places rules at /opt/aurora-linux/sigma-rules/linux.
The EnvironmentFile override masked this, but fresh installs
without a custom env file would fail.
Tested: Aurora starts cleanly with empty AURORA_EXTRA_ARGS and
loads 194 Sigma rules from the correct path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bug 1: Empty env var crashes Aurora
systemd's
${AURORA_EXTRA_ARGS}passes a literal empty string when the variable is empty. Cobra interprets this as an unknown subcommand and exits immediately. Every fresh install with default config hits this.Fix: Wrap
ExecStartinbash -cwith unquoted$AURORA_EXTRA_ARGS— standard shell word splitting drops empty vars instead of passing them as arguments.Bug 2: Wrong default rules path
The unit file hardcoded
/opt/aurora-linux/sigma-rules/rules/linuxbut the install script places rules at/opt/aurora-linux/sigma-rules/linux. TheEnvironmentFileoverride masked this on systems with a custom env file, but fresh installs without one would fail to find rules.Tested
Aurora starts cleanly on Fedora 43 (kernel 6.18), loads 194 Sigma rules, and the eBPF listener initializes: