Bug 1898067

Summary:	SIGSEGV: notice: sendto failed: Address family not supported by protocol
Product:	Red Hat Enterprise Linux 8	Reporter:	Graham Leggett <minfrin>
Component:	unbound	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.4
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-16 07:27:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Graham Leggett 2020-11-16 10:17:29 UTC

Description of problem:

Unbound crashes during normal operation without warning.

Version-Release number of selected component (if applicable):

unbound-1.7.3-11.el8_2

How reproducible:

Sometimes.

Steps to Reproduce:
1. Deploy unbound as a local resolving nameserver.
2. Wait.
3.

Actual results:

Crash as follows:

[root@host ~]# systemctl status unbound | more
● unbound.service - Unbound recursive Domain Name Server
   Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor preset: disabled)
   Active: failed (Result: signal) since Sat 2020-11-14 10:15:46 SAST; 1 day 23h ago
  Process: 2090 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS (code=killed, signal=SEGV)
  Process: 1123 ExecStartPre=/usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem -f /etc/resolv.conf -R (code=exite
d, status=0/SUCCESS)
  Process: 1089 ExecStartPre=/usr/sbin/unbound-checkconf (code=exited, status=0/SUCCESS)
 Main PID: 2090 (code=killed, signal=SEGV)

Nov 13 05:14:15 host.example.com unbound[2090]: [2090:0] error: can't bind socket: Permission denied for ::
Nov 13 08:13:44 host.example.com unbound[2090]: [2090:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
Nov 14 06:36:49 host.example.com unbound[2090]: [2090:0] info: generate keytag query _ta-4a5c-4f66. NULL IN
Nov 14 07:16:46 host.example.com unbound[2090]: [2090:0] error: can't bind socket: Permission denied for ::
Nov 14 10:15:46 host.example.com unbound[2090]: [2090:0] notice: sendto failed: Address family not supported by protocol
Nov 14 10:15:46 host.example.com unbound[2090]: [2090:0] notice: remote address is (inet_ntop error) port 57990
Nov 14 10:15:46 host.example.com unbound[2090]: [2090:0] notice: sendto failed: Invalid argument
Nov 14 10:15:46 host.example.com unbound[2090]: [2090:0] notice: remote address is (inet_ntop error) port 57990
Nov 14 10:15:46 host.example.com systemd[1]: unbound.service: Main process exited, code=killed, status=11/SEGV
Nov 14 10:15:46 host.example.com systemd[1]: unbound.service: Failed with result 'signal'.

Expected results:

No crash.

Additional info:

Various reports have been raised, none yet with RHEL8.

Comment 1 Anna Khaitovich 2020-11-24 08:21:37 UTC

Hello, Graham,

Thank you for reporting this issue. I have problems with reproducing it, could you please provide more info? (for example your unbound.conf, resolv.conf) Also, how much time did it take until unbound crashed?

Thanks in advance

Comment 2 Graham Leggett 2020-11-25 12:07:12 UTC

There is more info in the logfile of the crash:

Nov 14 10:15:46 host unbound[2090]: [2090:0] notice: sendto failed: Address family not supported by protocol
Nov 14 10:15:46 host unbound[2090]: [2090:0] notice: remote address is (inet_ntop error) port 57990
Nov 14 10:15:46 host unbound[2090]: [2090:0] notice: sendto failed: Invalid argument
Nov 14 10:15:46 host unbound[2090]: [2090:0] notice: remote address is (inet_ntop error) port 57990
Nov 14 10:15:46 host kernel: unbound[2090]: segfault at 726602d7 ip 000055e6848fbf79 sp 00007ffebf54f9f0 error 4 in unbound[55e684875000+135000]
Nov 14 10:15:46 host kernel: Code: db 0f 84 82 01 00 00 8b 6b 20 85 ed 0f 85 8d 01 00 00 8b 53 18 85 d2 0f 85 3a 01 00 00 48 8b 70 38 48 85 f6 0f 84 cf 01 00 00 <8b> 96 88 00 00 00 48 8d 44 24 40 48 83 c6 08 b9 80 00 00 00 48 89

The machine had been up for days at the point of the crash.

Unbound isn't configured by default to dump core, so var/crash is empty.

[root@ host ~]# cat /etc/resolv.conf 
nameserver ::1
options edns0

unbound.conf is the unmodified default (rpm -Va unbound shows no changes).

Comment 6 RHEL Program Management 2022-05-16 07:27:38 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.