Can't start DNS Resolver (SG-2220, 2.4.4_3)

[teampolizei144]

Hi.
Can not seem to get unbound (DNS Resolver) to start after a reboot. It has always started perfectly previously.
I have tried doing a factory reset and have only done the basic setup wizard and it still won't start.
What I can find from the timeframe in the System logs (System->General) is:

"kernel pid 1361 (unbound), uid 59: exited on signal 10"

My system is:
System: Netgate SG-2220
Version: 2.4.4-RELEASE-p3

Anyone that have an idea of what could be wrong/anything I could try to fix it?

/T

[KOM]

Anything in Status - System Logs - DNS Resolver? If not, go to Services - DNS Resolver - Advanced Settings. Change Log Level from Level 1 to Level 2 and then restart Resolver and then check the logs.

[teampolizei144]

I changed to log level 2.
There is nothing in the DNS Resolver log file from the time I pushed the button to enable it.

[KOM]

And nothing new in the System - General log either? Any packages installed?

[teampolizei144]

No packages installed.
After clicking the start button on DNS Resolver I have a single entry:

Aug 10 20:39:48 kernel pid 60703 (unbound), uid 59: exited on signal 10

[KOM]

Signal 10 is a bus error:

In computing, a bus error is a fault raised by hardware, notifying an operating system (OS) that a process is trying to access memory that the CPU cannot physically address: an invalid address for the address bus, hence the name. In modern use on most architectures these are much rarer than segmentation faults, which occur primarily due to memory access violations: problems in the logical address or permissions.

On POSIX-compliant platforms, bus errors usually result in the SIGBUS signal being sent to the process that caused the error. SIGBUS can also be caused by any general device fault that the computer detects, though a bus error rarely means that the computer hardware is physically broken—it is normally caused by a bug in software.[citation needed] Bus errors may also be raised for certain other paging errors; see below.

I've never heard of this being reported before for unbound. If the unit is under support then I would contact Netgate and ask about it.

[teampolizei144]

My Contract type is 'Community Support' so I guess not.

[kiokoman]

try to launch unbound from the terminal with -v flags
unbound -d -vvv

[teampolizei144]

That gives me the following:

SSH:
[1565468819] unbound[88566:0] notice: Start of unbound 1.9.1.
[1565468819] unbound[88566:0] debug: creating udp6 socket ::1 53
[1565468819] unbound[88566:0] debug: creating tcp6 socket ::1 53
[1565468819] unbound[88566:0] debug: creating udp4 socket 127.0.0.1 53
[1565468819] unbound[88566:0] debug: creating tcp4 socket 127.0.0.1 53
[1565468819] unbound[88566:0] debug: switching log to syslog
Bus error

System Logs -> DNS Resolver
Aug 10 22:26:59 unbound 88566:0 debug: drop user privileges, run as unbound
Aug 10 22:26:59 unbound 88566:0 debug: chroot to /usr/local/etc/unbound
Aug 10 22:26:59 unbound 88566:0 debug: chdir to /usr/local/etc/unbound
Aug 10 22:26:59 unbound 88566:0 warning: did not exit gracefully last time (37796)

System Logs -> General
Aug 10 22:26:59 kernel pid 88566 (unbound), uid 59: exited on signal 10

[KOM]

@teampolizei144 said in Can't start DNS Resolver (SG-2220, 2.4.4_3):

unbound[88566:0] debug: switching log to syslog

Do you have a hostname set for the box?

https://forum.netgate.com/topic/77076/unbound-fails-silently

[teampolizei144]

@KOM If you medan under System-General Setup, Then yes there I havet pfSense set as hostname for the SG2220.

[kiokoman]

try to reinstall 2.4.4 or try with 2.5.0 that use unbound 1.9.2

[teampolizei144]

I reinstalled 2.4.4_3 today. It starts correctly now. Fingers crossed that it stays like this.
Thanks for your guidance in this thread.
/T