FFFF min bug cannot show why Minimal's DNS service fails on macOS · Issue #3476 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

min bug cannot show why Minimal's DNS service fails on macOS #3476

Closed

Description

@norrietaylor

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

  1. No version. The bundle does not record the minzoned version. The skew check reported "the minzoned version is not in the bundle". The installed copy was dev.319 and the install shipped dev.527, and no diagnosis could see that.
  2. No service state. The bundle does not record the launchd job dev.gominimal.zone. launchctl print system/dev.gominimal.zone runs without root, and on the failing host it showed runs = 1567, last exit code = 1 and state = spawn scheduled. Each diagnosis had to guess between a crash, an update and a manual unload.
  3. No port holder. The process tree is filtered to Minimal's own processes, and host/net/listening.txt shows only TCP. The bundle cannot show who holds UDP 127.0.0.1:7656. It was launchd, holding the port for the job. The launchctl print output lists the sockets launchd holds for the job.
  4. No logs. minzoned writes no log on macOS. The plist (ANSWERER_PLIST_TEMPLATE in crates/minimal/src/resolver.rs) sets no StandardOutPath or StandardErrorPath, so what minzoned printed 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 --version and the SHA-256 of both the installed copy (/Library/PrivilegedHelperTools/Minimal.app/Contents/MacOS/minzoned on 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 records systemctl status minzoned.socket minzoned.service.
  • minzoned logs where min bug collects it. On macOS, either the plist sets a log path that the job's user can write to, or minzoned writes its own log to ~/.local/state/minimal/logs/minzoned.log. That directory is already collected. On Linux, the bundle adds journalctl -u minzoned.service for the bundle's time window.
  • Optional: on macOS, the bundle adds launchd's exit records for dev.gominimal.zone from the system log, which give exit times even when minzoned printed 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.

Activity

  1. norrietaylor commented on Nov 17, 2026

    @norrietaylor
    MemberAuthor

    Fixed by #3484. One more low edge case is in #3497.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0