Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
When Minimal's DNS service for box names fails on macOS, a min bug bundle cannot show why. Three diagnoses of one failure, on min 0.8.0-dev.527, each listed the same gaps as caveats. The failure itself is in #3472.
What happens
- No version. The bundle does not record the
minzonedversion. The skew check reported "theminzonedversion is not in the bundle". The installed copy was dev.319 and the install shipped dev.527, and no diagnosis could see that. - No service state. The bundle does not record the launchd job
dev.gominimal.zone.launchctl print system/dev.gominimal.zoneruns without root, and on the failing host it showedruns = 1567,last exit code = 1andstate = spawn scheduled. Each diagnosis had to guess between a crash, an update and a manual unload. - No port holder. The process tree is filtered to Minimal's own processes, and
host/net/listening.txtshows only TCP. The bundle cannot show who holds UDP127.0.0.1:7656. It was launchd, holding the port for the job. Thelaunchctl printoutput lists the sockets launchd holds for the job. - No logs.
minzonedwrites no log on macOS. The plist (ANSWERER_PLIST_TEMPLATEincrates/minimal/src/resolver.rs) sets noStandardOutPathorStandardErrorPath, so whatminzonedprinted before it exited with code 1 is lost. On Linux, the service logs to journald, and the bundle does not collect that either.
host/net-naming.json reported the service as Installed throughout, because that step compares only the channel protocol version.
Expected
- The bundle records
minzoned --versionand the SHA-256 of both the installed copy (/Library/PrivilegedHelperTools/Minimal.app/Contents/MacOS/minzonedon macOS) and the copy the install ships (~/.local/bin/Minimal.app/Contents/MacOS/minzoned). The skew check compares them. The resolver already hashes the shipped source (sha256_of). - On macOS, the bundle records
launchctl print system/dev.gominimal.zone. On Linux, it recordssystemctl status minzoned.socket minzoned.service. minzonedlogs wheremin bugcollects it. On macOS, either the plist sets a log path that the job's user can write to, orminzonedwrites its own log to~/.local/state/minimal/logs/minzoned.log. That directory is already collected. On Linux, the bundle addsjournalctl -u minzoned.servicefor the bundle's time window.- Optional: on macOS, the bundle adds launchd's exit records for
dev.gominimal.zonefrom the system log, which give exit times even whenminzonedprinted nothing.
Reproduce
On macOS, make dev.gominimal.zone exit at start (for example, point its plist at a program that exits 1), run min bug, and look for the job's state, the minzoned version and its output in the bundle.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Activity
norrietaylor commentedon Nov 17, 2026
Fixed by #3484. One more low edge case is in #3497.