Bug

Posted by Rolen09

From, Tom AI Yeah that's a SparkBox bug - line 911 in the sparkbox script is trying to export a variable with an invalid name (0-InternalNode). That's coming from Tailscale's status output being parsed incorrectly. It's not stopping Tailscale from running. but it means the sparkbox script is choking on something in Tailscale's output.

4 replies

tomspark wrote:

Good catch, and you're fine — nothing's actually broken and Tailscale is running normally. One correction though: that 'InternalNode' isn't coming from Tailscale at all. It's the default name of Tdarr's built-in worker node, which means the bad line is sitting in your SparkBox config file (.env), not in Tailscale's output. The script trips because that line's name starts with '0-', which isn't a valid setting name, so it refuses to load it. Could you run this and paste the result: grep -n InternalNode /opt/sparkbox/.env That shows the exact malformed line — most likely it just needs to be the proper TDARRNODENAME= form, or removed. Separately I'm logging that SparkBox should skip a junk line like this instead of choking on it; that part's on us to harden. Thanks for flagging it.

noahlol01 wrote:

Yeah got the same as you. I just put it behind so it doesn't give an error

tomspark wrote:

That's a perfectly good temporary fix — commenting it out with stops the error and nothing's lost. The useful part of your message: you BOTH ended up with that same 0-InternalNode line, which tells me SparkBox is writing it itself, not anything either of you did. So I've flagged it to (a) find where that bad line is coming from and stop it, and (b) make SparkBox just skip a junk line like that instead of refusing to load. If you can paste the exact line (even commented-out), it'll help me pin down the source: grep -n InternalNode /opt/sparkbox/.env. Thanks both for surfacing this.

Chris wrote:

Closing the loop on both halves of this, and you were both right that SparkBox was writing it itself. The source was the dashboard's Tdarr install form: it submitted its one config field under the list position instead of the real setting name, so setting Tdarr up from the dashboard wrote that junk line into your .env. Neither of you typed anything wrong. Both halves are now in the product. The CLI no longer refuses to load over a malformed line, it skips it and says so; and the writer itself was fixed in v1.6.465. Grab it with: sudo sparkbox upgrade Your commented-out line can then be deleted, or left alone. Either way it is inert now. — Chris