Dear Maintainer,

Unbound fails to start when the system is booted. I have unbound
running on Debian 13 and on a Raspberry Pi also running Trixie,
and the same happens at every boot on both platforms.

After the system comes up, I need to use systemctl to manually
restart unbound, then it comes up and works without problems.

In the log, journalctl only says this:


 The unit unbound.service has entered the 'failed' state with result 'exit-code'.
░░ Automatic restarting of the unit unbound.service has been schedul>
░░ the configured Restart= setting for the unit.
Jun 24 22:00:12 ghost systemd[1]: unbound.service: Start request rep>
Jun 24 22:00:12 ghost systemd[1]: unbound.service: Failed with resul>
░░ Subject: Unit failed
░░ Defined-By: systemd

Control: tag -1 unreproducible moreinfo

I have multiple, numerous systems running unbound in various contexts
and configurations, and all of them works just fine.

Please see which error message unbound produces.

Thanks,

/mjt

Control: tag -1 unreproducible moreinfo

I have multiple, numerous systems running unbound in various contexts
and configurations, and all of them works just fine.

Please see which error message unbound produces.

Thanks,

/mjt