Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#49708 - [unbound] Systemd startup fails.

Attached to Project: Community Packages
Opened by Simon Nagl (simonnagl) - Tuesday, 14 June 2016, 10:07 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 15 June 2016, 06:32 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am using unbound 1.5.9

On my bananapi unbound fails during boot when enabled with
systemctl enable unbound

Starting after boot works. Here is the log:

Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Unit entered failed state.
Jun 14 11:56:53 BananaPi systemd[1]: Failed to start Unbound DNS Resolver.
Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Start request repeated too quickly.
Jun 14 11:56:53 BananaPi systemd[1]: Stopped Unbound DNS Resolver.
Jun 14 11:56:53 BananaPi systemd[1]: Starting Unbound DNS Resolver...
Jun 14 11:56:53 BananaPi systemd[1]: Stopped Unbound DNS Resolver.
Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jun 14 11:56:53 BananaPi systemd[1]: unbound.service: Unit entered failed state.
Jun 14 11:56:52 BananaPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 11:56:52 BananaPi unbound[297]: [1465898212] unbound[297:0] fatal error: could not open ports
Jun 14 11:56:52 BananaPi unbound[297]: [1465898212] unbound[297:0] error: can't bind socket: Cannot assign requested address for
Jun 14 11:56:52 BananaPi systemd[1]: Started Unbound DNS Resolver.
Jun 14 11:56:52 BananaPi systemd[1]: Starting Unbound DNS Resolver...
Jun 14 11:56:52 BananaPi systemd[1]: Stopped Unbound DNS Resolver.
Jun 14 11:56:52 BananaPi systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
Jun 14 11:56:52 BananaPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jun 14 11:56:52 BananaPi systemd[1]: unbound.service: Unit entered failed state.
Jun 14 11:56:52 BananaPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 11:56:52 BananaPi unbound[253]: [1465898211] unbound[253:0] fatal error: could not open ports
Jun 14 11:56:51 BananaPi unbound[253]: [1465898211] unbound[253:0] error: can't bind socket: Cannot assign requested address for
Jun 14 11:56:51 BananaPi systemd[1]: Started Unbound DNS Resolver.
Jun 14 11:56:51 BananaPi systemd[1]: Starting Unbound DNS Resolver...
Jun 14 11:56:51 BananaPi systemd[1]: Stopped Unbound DNS Resolver.
Jun 14 11:56:51 BananaPi systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
Jun 14 11:56:51 BananaPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jun 14 11:56:51 BananaPi systemd[1]: unbound.service: Unit entered failed state.
Jun 14 11:56:51 BananaPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 11:56:51 BananaPi unbound[206]: [1465898211] unbound[206:0] fatal error: could not open ports
Jun 14 11:56:51 BananaPi unbound[206]: [1465898211] unbound[206:0] error: can't bind socket: Cannot assign requested address for
Jun 14 11:56:50 BananaPi systemd[1]: Started Unbound DNS Resolver.
Jun 14 11:56:50 BananaPi systemd[1]: Starting Unbound DNS Resolver...
Jun 14 11:56:50 BananaPi systemd[1]: Stopped Unbound DNS Resolver.
Jun 14 11:56:50 BananaPi systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
Jun 14 11:56:50 BananaPi systemd[1]: unbound.service: Failed with result 'exit-code'.
Jun 14 11:56:50 BananaPi systemd[1]: unbound.service: Unit entered failed state.
Jun 14 11:56:49 BananaPi systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 11:56:49 BananaPi unbound[178]: [1465898209] unbound[178:0] fatal error: could not open ports
Jun 14 11:56:49 BananaPi unbound[178]: [1465898209] unbound[178:0] error: can't bind socket: Cannot assign requested address for
Jun 14 11:56:49 BananaPi systemd[1]: Started Unbound DNS Resolver.
Jun 14 11:56:49 BananaPi systemd[1]: Starting Unbound DNS Resolver...


Adding After=network-online.target to unbound.service works if network-online.target is used. If not I get the same error.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Wednesday, 15 June 2016, 06:32 GMT
Reason for closing:  Not a bug
Comment by Gaetan Bisson (vesath) - Tuesday, 14 June 2016, 18:06 GMT
By default unbound listens to localhost so After=network.target should be more than enough. This works fine for me in Arch and I have no idea why it doesn't for you in Arch ARM.
Comment by Simon Nagl (simonnagl) - Wednesday, 15 June 2016, 06:10 GMT
I tested with the default configuration. It works.

If I use interface=192.168.2.XXX the start does not work.
Comment by Gaetan Bisson (vesath) - Wednesday, 15 June 2016, 06:32 GMT
Well, obviously...

Loading...