<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Linux Colorado</title><link>https://www.linuxcolorado.com/tags/debugging/</link><description>Recent content in Debugging on Linux Colorado</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxcolorado.com/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>My Smart Meter Went Quiet for Ten Days: a 1,094-Day Client Certificate and IEEE 2030.5</title><link>https://www.linuxcolorado.com/post/2026-11-03-smart-meter-cert-expired-home-assistant/</link><pubDate>Tue, 03 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.linuxcolorado.com/post/2026-11-03-smart-meter-cert-expired-home-assistant/</guid><description>&lt;p&gt;Two sensors in Home Assistant had polled my electricity meter every five seconds for two years. One afternoon they both went &lt;code&gt;unknown&lt;/code&gt; and stayed that way for ten days before I noticed. Nothing had changed on my side: no update, no restart, no config edit. The meter was still answering other hosts on the LAN. And yet it had quietly stopped talking to me.&lt;/p&gt;
&lt;p&gt;The culprit was a client certificate I generated in 2023 with a script that handed it exactly three years of life. When it expired, the meter rejected every poll with a TLS alert, and Home Assistant just logged &lt;code&gt;Command failed (with return code 1)&lt;/code&gt; every five seconds until it ran out of curiosity. This post is the post mortem: how the meter&amp;rsquo;s local IEEE 2030.5 interface actually authenticates, why a cumulative register quietly books ten days of power into a single hour, and what I&amp;rsquo;d check first next time.&lt;/p&gt;</description></item><item><title>One Song Wouldn't Play. 231 Files Were Broken. Lidarr's Ogg Tag Writer Was the Culprit.</title><link>https://www.linuxcolorado.com/post/2026-11-02-lidarr-ogg-vorbis-corruption-repair/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.linuxcolorado.com/post/2026-11-02-lidarr-ogg-vorbis-corruption-repair/</guid><description>&lt;p&gt;On September 11, 2026, one song would not play. The client just retried it, in a loop, forever. Not a silence, not an error dialog — a little spinner that never resolved. I&amp;rsquo;d seen that behavior before, and I&amp;rsquo;d always blamed the server. This time the server was fine, and the truth was stranger: &lt;strong&gt;Lidarr had been quietly corrupting my Ogg Vorbis files for months, nightly, one byte at a time.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The setup is a normal homelab. Music lives on the NAS (&lt;code&gt;.12&lt;/code&gt;, ZFS) and is served by &lt;strong&gt;&lt;a href="https://www.navidrome.org"&gt;Navidrome&lt;/a&gt;&lt;/strong&gt; on &lt;code&gt;.21&lt;/code&gt;, which streams the raw file — transcoding is off — to a desktop client called &lt;strong&gt;Supersonic&lt;/strong&gt;. &lt;strong&gt;&lt;a href="https://lidarr.audio"&gt;Lidarr&lt;/a&gt; 3.1.0.4875&lt;/strong&gt;, also on &lt;code&gt;.21&lt;/code&gt;, manages the library. Somewhere along the way I&amp;rsquo;d set &amp;ldquo;Write Metadata to Audio Files&amp;rdquo; to &lt;strong&gt;Sync&lt;/strong&gt; (&lt;code&gt;writeaudiotags = Sync&lt;/code&gt;, &lt;code&gt;scrubaudiotags = True&lt;/code&gt;), which means every nightly Refresh Artist rewrites tags and embeds cover art directly into the files themselves.&lt;/p&gt;
&lt;p&gt;That setting is the whole story. It turned a metadata tool into a corruption machine.&lt;/p&gt;</description></item></channel></rss>