Unbound fails to start with setsockopt(2) error
I’ve not seen this elsewhere. It seems to be specific to alpine.
I’m running edge.
Unbound fails to start; testing it with -dvvvvvvv reports:
[1425817029] unbound[9193:0] notice: Start of unbound 1.5.1.
[1425817029] unbound[9193:0] debug: increased limit(open files) from
1024 to 4140
[1425817029] unbound[9193:0] debug: creating udp4 socket 192.168.1.4
53
[1425817029] unbound[9193:0] error: setsockopt(…, IP_MTU_DISCOVER,
IP_PMTUDISC_OMIT…) failed: Invalid argument
[1425817029] unbound[9193:0] fatal error: could not open ports
Ahh. Searching further I found this patch:
https://www.nlnetlabs.nl/bugs-script/attachment.cgi?id=269
and a note suggesting that 1.5.2 does not need the patch, so upgrading edge from 1.5.1 to 1.5.2 also should fix this.
I haven’t delved into you packaging enough to find which needs a diff to fix this….
(from redmine: issue id 3964, created on 2015-03-08, closed on 2015-05-25)