stubby Succeeds in starting roughly 10% of the time, usually enters a crash loop, ignoring log level

Package Name

stubby 0.4.3:

Maintainer

NONE

OpenWrt Version

24.10.1

OpenWrt Target/Subtarget

ramips/mt7621

Steps to Reproduce

1. Install stubby
2. attempt to start stubby with uci or yml config

Actual Behaviour

stubby will enter a crash loop if started through uci, but sometimes rarely succeed.
if started from the command line, it will have a slightly higher rate of success, while usually halting here:

root@OpenWrt:~# stubby
[14:11:46.923581] STUBBY: Read config from file /etc/stubby/stubby.yml[14:11:46.932892] STUBBY: Stubby version: Stubby 0.4.3
[14:11:46.938661] STUBBY: DNSSEC Validation is OFF
[14:11:46.938820] STUBBY: Transport list is:
[14:11:46.938870] STUBBY:   - TLS
[14:11:46.938977] STUBBY: Privacy Usage Profile is Strict (Authentication required)
[14:11:46.939082] STUBBY: (NOTE a Strict Profile only applies when TLS is the ONLY transport!!)
[14:11:46.939172] STUBBY: Starting DAEMON....

log level is always ignored, so there is no output in logread, except the crash loop warning when started with uci.

Confirmation Checklist

• The package is maintained in this repository.
• I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
• I am reporting an issue for OpenWrt, not an unsupported fork.

Start by reproducing stubby 0.4.3 on OpenWrt 24.10.1 for ramips/mt7621 through UCI, the YAML configuration, and the command line. Compare the crash-loop behavior and missing logread output; done means the startup failure is identified and corrected with useful logging for the failing path.