FS#59561 - No PIDFile causes service start failure
Attached to Project:
Community Packages
Opened by DYSEQTA (DYSEQTA) - Wednesday, 08 August 2018, 02:43 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 08 August 2018, 04:46 GMT
Opened by DYSEQTA (DYSEQTA) - Wednesday, 08 August 2018, 02:43 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 08 August 2018, 04:46 GMT
|
Details
Description:
Installing 1.7.3-3 results in service failing to start Reintroducing the line "PIDFile=/run/unbound.pid" under [Service] fixes the problem Additional info: Version affected: 1.7.3-3 Files involved: /usr/lib/systemd/system/unbound.service Steps to reproduce: install 1.7.3-3 and attempt to start service Result: Aug 08 12:21:48 mcp systemd[1]: Started Unbound DNS Resolver. -- Subject: Unit unbound.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit unbound.service has finished starting up. -- -- The start-up result is RESULT. Aug 08 12:21:48 mcp unbound[1713]: [1713:0] notice: init module 0: validator Aug 08 12:21:48 mcp unbound[1713]: [1713:0] notice: init module 1: iterator Aug 08 12:21:48 mcp unbound[1713]: [1713:0] info: start of service (unbound 1.7.3). Aug 08 12:21:48 mcp unbound[1713]: [1713:0] info: service stopped (unbound 1.7.3). Aug 08 12:21:48 mcp unbound[1713]: [1713:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting Aug 08 12:21:48 mcp unbound[1713]: [1713:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0 Aug 08 12:21:49 mcp systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart. Aug 08 12:21:49 mcp systemd[1]: unbound.service: Scheduled restart job, restart counter is at 5. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit unbound.service has been scheduled, as the result for -- the configured Restart= setting for the unit. Aug 08 12:21:49 mcp systemd[1]: Stopped Unbound DNS Resolver. -- Subject: Unit unbound.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit unbound.service has finished shutting down. Aug 08 12:21:49 mcp systemd[1]: unbound.service: Start request repeated too quickly. Aug 08 12:21:49 mcp systemd[1]: unbound.service: Failed with result 'start-limit-hit'. Aug 08 12:21:49 mcp systemd[1]: Failed to start Unbound DNS Resolver. -- Subject: Unit unbound.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit unbound.service has failed. Fix: Reintroducing the line "PIDFile=/run/unbound.pid" under [Service] in /usr/lib/systemd/system/unbound.service |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 08 August 2018, 04:46 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#59503
Wednesday, 08 August 2018, 04:46 GMT
Reason for closing: Duplicate
Additional comments about closing: