Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

unbound (1.13.1-1) on latest raspbian not working, segmentation fault / RPI 4 #241

Open
darkmanlv opened this issue Oct 20, 2022 · 1 comment

Comments

@darkmanlv
Copy link

OS: raspbian arm64 with latest updates
HW: RPi 4

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux

pi@raspberrypi:~ $ sudo unbound -dv -c /etc/unbound/unbound.conf
Segmentation fault

20 20:57:37 raspberrypi systemd[1]: unbound.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 11.
Oct 20 20:57:37 raspberrypi package-helper[2109]: Segmentation fault
Oct 20 20:57:37 raspberrypi systemd[1]: unbound.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit unbound.service has entered the 'failed' state with result 'signal'.

How to fix this?

@XECDesign
Copy link

Works for me and a few other people who have tried, by the looks of it: https://forums.raspberrypi.com/viewtopic.php?p=2047929

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants