0

Segmentation Fault

I'm getting a segmentation fault when trying to start/issue commands to NextDNS on Asus-Merlin.

 

It seemed fine until after a reboot. Now all I get is segmentation fault. Even after reboots.

 

Therion87@RT-AX86U-2978:/tmp/home/root# nextdns
Segmentation fault
Therion87@RT-AX86U-2978:/tmp/home/root#

4 replies

null
    • Pro Subscriber ✅
    • Jorgen_A
    • 3 yrs agoTue, June 8, 2021 at 5:19 PM UTC
    • Reported - view

    I'm also using AX86U with Merlin and can confirm the "symlink/path" have never survived a reboot even though it should according to NextDNS team.  I have to enter the full path each time and have done so for 2 years now 😉

    Does it work if you enter the full path like this:
    /jffs/nextdns/nextdns <command>

    • Robert_Allen
    • 3 yrs agoTue, June 8, 2021 at 5:22 PM UTC
    • Reported - view

    I am also on an AX86U. It does not work with the full path.

     

    Therion87@RT-AX86U-2978:/tmp/home/root# /jffs/nextdns/nextdns
Segmentation fault
Therion87@RT-AX86U-2978:/tmp/home/root# cd /jffs/
Therion87@RT-AX86U-2978:/jffs# ls
addons          ca_files        nextdns         nvram           scripts         syslog.log-1    wglst.1
asd             cert.tgz        nmp_cl_json.js  nvram_war       signature       usericon        zoneinfo
asd.log         configs         nmp_vc_json.js  openvpn         syslog.log      wglst
Therion87@RT-AX86U-2978:/jffs# cd nextdns/
Therion87@RT-AX86U-2978:/jffs/nextdns# ls
nextdns       nextdns.conf  nextdns.init
Therion87@RT-AX86U-2978:/jffs/nextdns# nextdns
Segmentation fault
Therion87@RT-AX86U-2978:/jffs/nextdns#
    • Pro Subscriber ✅
    • Jorgen_A
    • 3 yrs agoTue, June 8, 2021 at 6:01 PM UTC
    • Reported - view

    Strange... Does any command work at all, like "nextdns config"?

    Did you use the default settings during install? Are you maybe low on RAM? Have you tried to uninstall and install it again?

    • Robert_Allen
    • 3 yrs agoTue, June 8, 2021 at 6:21 PM UTC
    • Reported - view

    So, no commands worked.

    Restarting didn't fix it. There wasn't a low memory issue.

    I manually deleted the installation path and reinstalled. Seems working for now. I will attempt to replicate it later.

Login to reply

Content aside

  • 3 yrs agoTue, June 8, 2021 at 6:21 PM UTCLast active
  • 4Replies
  • 54Views
  • 2 Following