Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. vaboro

    BACKUPMON BACKUPMON v1.5.10 -Mar 1, 2024- Backup/Restore your Router: JFFS + NVRAM + External USB Drive! (**Thread closed due to age**)

    Is the vers=2.1 option crucial for proper script operation? I have Asuswrt-Merlin gt-ac2900 386.12_0 at the moment and running # mount with vers=2.1 results in: Whereas if I omit "vers=2.1" the share mounts successfully with vers=1.0: The maximum vers I could use to mount the share...
  2. vaboro

    RT-AC86U: "PCP MAP: failed to add mapping TCP" error every 15 minutes

    @Uluqat, I've been ignoring "PCP MAP: failed to add mapping TCP 9" for years. Luckily @RMerlin provides a simple way to solve it with custom config files. If you find it still useful I added the following upnp.postconf file to /jffs/scripts folder: The IP/mask and the exact location of the line...
  3. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Thank you for your advice. However, except from these regular tokio-runtime crashes I haven't noticed any unusual traffic or processor loads. Skynet is running pretty well too. If reconfiguring AdGuardHome doesn't help, I will probably follow your advice.
  4. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Can you recommend an updated version or variant, please?
  5. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    I suspect AdGuardHome. It has an option of redirecting all DNS queries via AdGuardHome as well as choosing AdGuardHome for DNS caching.
  6. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    If it were there would be no other way for it to get to the router but via the packages installed by me from opkg sources or delivered by Asus.
  7. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    This is what I presumed as well. Interestingly, the tokio-runtime warnings are trigged by dnsmasq restart. And the warnings servived both firmware upgrade and factory default reset with settings reinitalization. I recovered all the settings from nsru script backup after reset though.
  8. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    I supposed you had a glimpse on one of my htop screenshots and identified some PIDs corresponding to statsd and tokio-rs/tokio-tls. As far as statsd is concerned I see its PID clearly myself. Yet, I can't discern the PIDs pertaining to tokio runtime.
  9. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    On the box that shows tokio-runtime warning I have syslog, nginx, transmission and adguardhome: The following entware packages are installed on this machine: Most of them were installed as dependencies of other packages or scripts. What PIDs have you identified as tokio-rs/tokio-tls?
  10. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Yes, I have asterisk. But it's installed on another identical box that hasn't showed any tokio-runtime warnings ever yet. But the box with asterisk it's running dnsmasq though. It's in AP mode. asterisk-app-statsd package is NOT installed.
  11. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Thanks for advice, haha:)
  12. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Well, I'm pretty sure it's not malware. Thanks.
  13. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Do you know what statsd is? It's on line 2 of /jffs/scripts/dnsmasq: #!/bin/sh (sleep 10 && /jffs/statsd) & /usr/sbin/dnsmasq $@ wait Warnings appear regularly. Last time moments ago. I omitted some of the repeating lines. I couldn't find PID 63949 in the process list. Maybe it couldn't...
  14. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    @ColinTaylor thank you for your prompt reply. My thinking was that tokio runtime might be part of dnsmasq. But I will look into the other software I have installed as well.
  15. vaboro

    restarting dnsmasq triggers a flood of tokio-runtime warnings

    Is there a known way to fix this?
  16. vaboro

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Have you tried @StarkWiz 's hack? I have and my Asterisk installation became again operational.
  17. vaboro

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Will go give it a try. My asterisk doesn't work at all... SUCCESS Asterisk is again operational. Moreover, scribe doesn't compain any more. I presume it got what it wanted:D
  18. vaboro

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    I see that quite a few packages depend on openssl in my environment: # opkg whatdepends libopenssl Root set: libopenssl What depends on root set syslog-ng 3.38.1-1a depends on libopenssl openssh-sftp-server 9.2p1-1 depends on libopenssl libcurl 7.86.0-1 depends on...
  19. vaboro

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    Which essentially means libhttp.so should be recompiled against OpenSSL3, and since it's included in syslog-ng, an upgrade to syslog-ng is needed, right?
  20. vaboro

    Scribe error='libssl.so.1.1: wrong ELF class: ELFCLASS32'

    I upgraded via amtm. Perhaps the @thelonelycoder can take this into accout in the next version.
Top