Jump to content

ER Samson

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by ER Samson

  1. Currently using Armbian as a PiHole DNS server, it seems that after a few days the server just shuts itself down (Armbian 25.5.1 Noble 6.12). Not sure if it is a hardware related issue, I'll do some more tests and revert back to 25.2.2 Bookworm for now and see if the issue is replicated. Please note that my primary Armbian PiHole DNS does not encounter the same issue, though the version of it is Noble v25.2.3 / 6.12.30.
  2. Yup, the newest Armbian 24.5.1 release is really good, Seems like all issues may have been resolved. I'll mark this thread as solved.
  3. Just so add, so far so good (10 hrs and counting, no CPU spikes). Armbian 24.5.1 with 6.6.31 Linux Kernel is super stable so far.
  4. hi @Stephen Graf No worries, all good. I am currently trying out the newest freshly installed Armbian (24.5.1) on the primary instance (still on Pihole + DNSCrypt). One good thing I'm seeing is that using "ps -ef" the vncstats is not visible. Let's see how it holds. Will report back.
  5. Using DNScrypt does reduce the instabilities with Linux 6.6.16-current-sunxians higher, though it still did have slowdowns/high CPU usage after 2-3 days. I had to move the back up instance to legacy kernel and so my network has a functioning DNS when the other conks up. Legacy has been rock stable.
  6. I may have found the culprit after monitoring htop. "vnstat -n" process eats up CPU cycles, sometimes reaching up to "6+" load-average (even if this OrangePi is quad-core equipped) This only happens intermittently and I can't seem to find the pattern. Sharing my observations here: Only affects Linux 6.6.16-current-sunxi and higher (such as edge), legacy firmware is not affected (stable for more than a week) Installing Pihole with cloudflared DoH package seems to trigger high CPU usage of vnstat Reboot fixes it (or a power cycle) Having PiHole with dnscrypt-proxy does not trigger the issue (so far, this test instance is already at the 16-hr mark, will keep on updating uptime) Since it was stable overnight I now have two instances with this configuration, hoping for the best! Not sure if helpful, but this is all that I have for now. Thanks!
  7. Seems like the OS "malfunctions" after a few hours to a couple of days. The server is still responding to Pings, but services are all down, such as SSH. Doing a power cycle would make the system available back online, until it becomes non-responsive again. Moving back to 23.11.1 solves the stability issue. To add, I'm using a couple of instances for primary and secondary PiHole DNS servers. Probably similar issue on this thread - I'm a bit of a noob, if someone can redirect me to pasting logs. Can those be found on /var/logs as I haven't explored much. I have downgraded both my OPiOnes to 23.11.1 and Frozen the Armbian firmware updates, so I can't provide logs for now at least until I try to update one of the instances.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines