Unbound seems to start 3 times



  • I stopped unbound from Status->Services (10:11:12 in the log below), then started it at 10:12:08 (after applying pull request https://github.com/pfsense/pfsense/pull/1347 which makes the start actaully happen).
    But the Resolver log has 3 sets of messages about it, all from the same PID.
    Is there some good reason that it is starting the process then sending it a few stop/start messages in quick succession?

    When I see stuff like this, I begin to suspect there might be something not quite right, and thus there might be edge cases where something will break.

    Nov 24 10:12:10 	unbound: [93477:0] info: start of service (unbound 1.4.22).
    Nov 24 10:12:10 	unbound: [93477:0] notice: init module 0: iterator
    Nov 24 10:12:10 	unbound: [93477:0] notice: Restart of unbound 1.4.22.
    Nov 24 10:12:10 	unbound: [93477:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:10 	unbound: [93477:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:10 	unbound: [93477:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:10 	unbound: [93477:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:10 	unbound: [93477:0] info: service stopped (unbound 1.4.22).
    Nov 24 10:12:09 	unbound: [93477:0] info: start of service (unbound 1.4.22).
    Nov 24 10:12:09 	unbound: [93477:0] notice: init module 0: iterator
    Nov 24 10:12:09 	unbound: [93477:0] notice: Restart of unbound 1.4.22.
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:09 	unbound: [93477:0] info: service stopped (unbound 1.4.22).
    Nov 24 10:12:09 	unbound: [93477:0] info: start of service (unbound 1.4.22).
    Nov 24 10:12:09 	unbound: [93477:0] notice: init module 0: iterator
    Nov 24 10:12:09 	unbound: [93477:0] notice: Restart of unbound 1.4.22.
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:09 	unbound: [93477:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:08 	unbound: [93477:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:12:08 	unbound: [93477:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:12:08 	unbound: [93477:0] info: service stopped (unbound 1.4.22).
    Nov 24 10:12:08 	unbound: [93477:0] info: start of service (unbound 1.4.22).
    Nov 24 10:12:08 	unbound: [93477:0] notice: init module 0: iterator
    Nov 24 10:11:12 	unbound: [20064:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:11:12 	unbound: [20064:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:11:12 	unbound: [20064:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
    Nov 24 10:11:12 	unbound: [20064:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
    Nov 24 10:11:12 	unbound: [20064:0] info: service stopped (unbound 1.4.22).