FreeMan

Members
  • Posts

    1513
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    Indiana

Recent Profile Visitors

3754 profile views

FreeMan's Achievements

Community Regular

Community Regular (8/14)

88

Reputation

  1. 52°C is at the upper end of the range I've ever _noticed_. Doesn't mean it hasn't been hotter, that's just the hottest I've seen...
  2. Fair enough, @MAM59. I've had ongoing issues with this over the last couple of years and have never managed to figure out the cause. I don't have the fastest server, MoBo, drives or controllers, so this isn't a totally unreasonable suggestion. If you'll note in the screen shots, though, CPU temp was 51 & 52°C when it was reporting 100% CPU and had dropped to 39°C at 77% total CPU load, so I'd say the CPU was actually busy doing something, not just waiting for I/O. Also, the web interface of several dockers was running slowly, as though the CPU was highly stressed and my requests to the various dockers were in queue waiting for some CPU attention. If you've got any other suggestions on how to determine what's actually going on, I'm more than open to listening.
  3. Just spiked again. This time, I know that my Sonarr docker is renaming a lot of files to fix up their naming, but, how do I determine what is actually happening when I haven't just kicked off some sort of process that I know may cause high CPU. during the CPU spike: nas-diagnostics-20240308-1534.zip
  4. My CPU has been like this for the past couple of hours and it will peak like this every now and then. I have no idea what causes this. I've looked at docker usage and they're usually 1% or less (I currently have 2 dockers running around 15% each, but that still only accounts for 30% total, not the 100% being shown.) This is one of the very few times top has shown my anything running above 10% or so, so this does seem almost reasonable: the tdarr_server I'd expect, since I'm doing a lot of file transcodes (but none are actually transcoding on the UNRAID server itself - all nodes are running on Win machines). How do I determine what the smbd processes are that are at 21% and 11%? Obviously shfs was running very high, how do I determine what was causing that? CPU utilization has just dropped off, but this is the first time all afternoon it's been at a reasonable level: Again, how do I go about figuring out what causes this high CPU? Is there a way to log from top? Is there something else that'll show and log what's using CPU? How do I determine what's causing SHFS and SMBD to use so much CPU? Under the assumption that it's usually helpful: nas-diagnostics-20240308-1526.zip These were taken after CPU utilization dropped back down, though.
  5. Interesting. I didn't see anything in the change log that would point to this, but it does, in fact, seem to have solved the issue. I did see that it updated last night (thanks, CA!), but I didn't wait until tonight to let it autoupdate again.
  6. Yesterday, all was good, this evening, the Dashboard will not display. I've tried in my normal FireFox, and also in Brave and Chrome. It spins forever (at least 30 seconds), then displays the header but nothing else. Here's a screenshot from Brave, but all 3 browsers show the same: All the other tabs will display info as expected. In FireFox (my primary browser) I've cleared cache and cookies and did a ctrl-F5 to do a hard refresh and still the same thing. Tips, tricks & suggestions more than welcome! nas-diagnostics-20240306-1738.zip
  7. Held the power button til the server turned off, then turned it back on. It's up & running now. Whew!
  8. Hrm... I rebooted and the server didn't come back up. Can't get to <ip>/main. Don't even get to the login page. The counter was at 25xx something... Suggestions?
  9. Thank you sir! I've made the config change and am rebooting. Can you point me to a basic primer on what the difference is? I don't need all the nitty gritty details, I'm just curious, at a high level, what this really means.
  10. I've been getting reports from Fix Common Problems about "Macvlan and bridging found" for several weeks. It's time to sit down and figure this out. Unfortunately, I clicked the "More Information" link in FCP, and it's mostly Greek to me. Most of my dockers are set up with bridge networking. Do I simply According to the release notes in the "More Info" link? I'm currently set to macvlan, but honestly don't know enough about networking to know what difference that would make. I'm reasonably certain I've never changed it from the day I set up my first docker. I do have a Ubiquiti router, so should I follow that up with these steps? Since I've only got one NIC in the machine, I'd presume Bonding should be NO. AIUI, it's kinda pointless either way with only one NIC. Any advice is greatly appreciated. nas-diagnostics-20240221-1909.zip
  11. Winner, winner, chicken dinner! Amazingly, that fixed it. I must have, for some odd reason, initially installed this in bridge mode and just never realized it. I've never had this ESPHome docker recognize any of my ESP devices. I'd built a couple, used this to edit the YAML, but then installed it through an ESPHome installed on my desktop... TYVM!
  12. Unbelievably, I had it set to `bridge`. Changing it to `Host`, however, hasn't fixed the issues.
  13. From my UniFi's default network config page, I've had MDNS enabled, and I just enabled IGMP Snooping based on a suggestion from the vendor of my latest ESP based device. Neither have made a difference.
  14. This post: https://community.home-assistant.io/t/esphome-devices-offline-but-only-for-dashboard-status/403141/25 indicates that attaching dbus and avahi sockets worked. Thoughts on doing so, and tips on how to translate that into the UNRAID docker config if you think it'll help? Several other comments on that thread mention mDNS as well...