Dnscrypt-proxy SIGSEVG error

Hi there,
Yesterday i faced some problems with dnscrypt-proxy so dns don't work.

The error from syslog is shown below.

Wed Aug 30 14:52:46 2023 kern.info kernel: [ 2665.436503] do_page_fault(): sending SIGSEGV to dnscrypt-proxy for invalid write access to 77e97da0
Wed Aug 30 14:52:46 2023 kern.info kernel: [ 2665.445931] epc = 00a32b3c in dnscrypt-proxy[400000+ad2000]
Wed Aug 30 14:52:46 2023 kern.info kernel: [ 2665.451663] ra  = 00401410 in dnscrypt-proxy[400000+ad2000]
Wed Aug 30 14:52:51 2023 kern.info kernel: [ 2670.477280] do_page_fault(): sending SIGSEGV to dnscrypt-proxy for invalid write access to 77e01da0
Wed Aug 30 14:52:51 2023 kern.info kernel: [ 2670.486536] epc = 00a32b3c in dnscrypt-proxy[400000+ad2000]
Wed Aug 30 14:52:51 2023 kern.info kernel: [ 2670.492249] ra  = 00401410 in dnscrypt-proxy[400000+ad2000]
Wed Aug 30 14:52:56 2023 kern.info kernel: [ 2675.506955] do_page_fault(): sending SIGSEGV to dnscrypt-proxy for invalid write access to 77efbda0
Wed Aug 30 14:52:56 2023 kern.info kernel: [ 2675.516246] epc = 00a32b3c in dnscrypt-proxy[400000+ad2000]
Wed Aug 30 14:52:56 2023 kern.info kernel: [ 2675.522186] ra  = 00401410 in dnscrypt-proxy[400000+ad2000]

Any idea?

Thank you

Well your dnscrypt-proxy instance tried to access an invalid memory location, so the kernel sent a SIGSEGV (signal segmentation violation) to dnscrypt-proxy.

Nothing it would appear has anything to do with adblock blocklist failure.

Why? I don’t know. You’re sparse on your details.

1 Like

Hi,
I haven't provided many details because I'm not sure what might be needed.

For starters, you can edit the topic -- https-dns-proxy is NOT the same as dnscrypt-proxy.

2 Likes

I have modified your subject title to better reflect your issue.

Let’s start with ubus call system board and opkg info dnscrypt*

1 Like

Alright, thank you.

ubus call system board

{
        "kernel": "5.10.176",
        "hostname": "P0LiP0",
        "system": "Atheros AR9344 rev 2",
        "model": "TP-Link TL-WDR3600 v1",
        "board_name": "tplink,tl-wdr3600-v1",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "22.03.5",
                "revision": "r20134-5f15225c1e",
                "target": "ath79/generic",
                "description": "OpenWrt 22.03.5 r20134-5f15225c1e"
        }
}

opkg info dnscrypt*

Package: dnscrypt-proxy2
Version: 2.1.2-1
Depends: libc, ca-bundle
Conflicts: dnscrypt-proxy
Status: install user installed
Architecture: mips_24kc
Conffiles:
 /etc/dnscrypt-proxy2/dnscrypt-proxy.toml 71134f593af3d02a395e0de95b40e8ede33bc79d0e33da1e3ba34ee2206abaa4
Installed-Time: 1690352032

Thanks.

Based on the package install date (Wed Jul 26 02:13:52 EDT 2023), is this a new package install of dnscrypt-proxy2, or an upgrade to a previously working package?

dnscrypt-proxy2 is a hefty package, and running on an 8/128 device would be taxing to say the least.

You might want to read Flash/RAM limitations & Expanding your root fs

Thanks to you for your time.
dnscrypt-proxy2 has been installed, and it's not an update.
I'm aware of the limitations of my hardware, but so far, it has worked excellently.
I have implemented exroot. Do you think a solution like DNS-over-TLS with Unbound and odhcp might be better?