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#61604 - [unbound] won't start through systemd

Attached to Project: Community Packages
Opened by Laura Hild (quartsize) - Friday, 01 February 2019, 21:09 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 February 2019, 21:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The unit file /usr/lib/systemd/system/unbound.service included in the
Arch package does not specify service unit Type, so it defaults to
`simple` and when unbound forks systemd sees that what it considers the
main process has died and repeatedly restarts it until giving up.

Adding Type=forking to the [Service] section of the unit file allows the
service to start successfully. Upstream has a more complex unit file in
contrib/unbound.service.in that specifies Type=notify but I haven't
tried it.


> pacman -Q unbound
unbound 1.8.3-1
> systemctl start unbound
> systemctl status unbound
‚óŹ unbound.service - Unbound DNS Resolver
Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since Fri 2019-02-01 15:48:55 EST; 3s ago
Process: 3853 ExecStart=/usr/bin/unbound (code=exited, status=0/SUCCESS)
Main PID: 3853 (code=exited, status=0/SUCCESS)

Feb 01 15:48:55 ... systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart.
Feb 01 15:48:55 ... systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5.
Feb 01 15:48:55 ... systemd[1]: Stopped Unbound DNS Resolver.
Feb 01 15:48:55 ... systemd[1]: unbound.service: Start request repeated too quickly.
Feb 01 15:48:55 ... systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
Feb 01 15:48:55 ... systemd[1]: Failed to start Unbound DNS Resolver.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 01 February 2019, 21:14 GMT
Reason for closing:  Duplicate
Additional comments about closing:  Bad config

Loading...