FreeMan

Members
  • Posts

    1513
  • Joined

  • Last visited

Posts posted by FreeMan

  1. 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.

  2. 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.

    image.png.b5dcfc8bac683427d76ca2114b9ea781.png

    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:

    image.png.16a5c32044142f7663e91a7858615268.png

    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:

    image.thumb.png.e44057d2f7e381224290b3e883916c39.png

     

    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.

  3. 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.

  4. 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:

    image.thumb.png.7e10fadd74bf055b4315f4b1f19bcd79.png

     

    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

     

  5. 12 hours ago, JorgeB said:

    Easiest fix is to change to docker network to ipvlan: (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

    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.

  6. 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

    Quote

    switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan.

    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?

    Quote

    Settings > Network Settings > eth0 > Enable Bonding = Yes or No, either work with this solution

    Settings > Network Settings > eth0 > Enable Bridging = No (this will automatically enable macvlan)

    Settings > Docker > Host access to custom networks = Enabled

    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

  7. On 11/27/2023 at 10:05 PM, digiblur said:

    Remove the use ping maybe? 

    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!

  8. 1 minute ago, digiblur said:

    Can you hit the logs on the devices and do they show?

     

    No dice:

     

    Quote

    INFO ESPHome 2023.11.4

    INFO Reading configuration /config/ambient-humidity.yaml...

    INFO Starting log output from ambient-humidity.local using esphome API

    WARNING Can't connect to ESPHome API for ambient-humidity: Error resolving IP address: [Errno -2] Name or service not known (APIConnectionError)

    INFO Trying to connect to ambient-humidity in the background

     

  9. That was all Greek to me, so I'm gonna say "no". The only time I've changed Host to Bridge or vice versa is on direct instructions from someone trying to help me fix something. No VLANs MDNSs or anything else fancy. All devices (except internal dockers) have a 192.168.*.* IP address.

     

    Took a look at the ESPHome config page and don't see a Ping option. Is that something that needs to be manually added?

     

    UPDATE: Yes, sorry, I do see the use ping and it is set to 'true'. I set that a week or so ago, and things remain offline.

  10. For the first time in forever (or longer) I've had an issue upgrading my UNRAID server.

     

    I upgraded from 6.12.2 to 6.12.3. The reboot screen counted to more than 400 (which is much longer than usual). I got impatient (probably my mistake) and powered down the server. After a minute I restarted.

     

    Now I cannot get to the webUI via https://nas.local or 192.168.1.5, nor can I Telnet in via an SSH connection to 192.168.1.5 as I always have in the past. I also cannot access drives on the server via my Windows machines. I do know that the server is actually up and running, since my dockers are responding, and my Kodi box can talk to the Emby docker on the server and stream movies/TV shows. I have even had family remotely connect to Emby.

     

    I'm continuing to get server notifications via Pushover, however the server name has changed from NAS to Tower. I attempted to connect to https://tower.local and got no joy. However I can connect to http://tower.local. After resetting the server name back to NAS, I now cannot connect on http://nas.local, https://nas.local, https://tower.local  or http://tower.local. I can, however, access it on http://192.168.1.5.

     

    Even after starting the array (which I realize shouldn't make a lick of difference) I still cannot access the WebUI via nas.local.

     

    I hope someone can identify from the nas-diagnostics-20230718-1907.zip what the heck has happened.

     

     

  11. On 3/30/2023 at 3:10 PM, olehj said:

    Now, there's reason why it had to be like this - this time around. To prevent my plugin from being blocked (which it actually was for some days) due to major changes in the Dashboard for Unraid 6.12, I had to fix and release a new update.

     

    I'm not sure I follow why you had to release an update to production to support 6.12 while 6.11.x is still in production, but again, your plugin, do as you wish.

     

    Obviously, some folks are throwing their toys out of the pram over it, I'll just double check the weekly FCP warning that it's incompatible until 6.12 is released, then I'll update. I think I'll then get an FCP warning that my current version of DL isn't compatible, and I'll go manually update it.

     

    Life goes on.

  12. On 3/11/2023 at 10:56 AM, FreeMan said:

     

    Could you give some directions on how to do this, please?

     

    It's been ages since I've messed with a bare metal Unix system (HP-UX anybody? Like last century...). I've only installed plugins & dockers on my unraid box.

     

    Managed to get it set up & working. Now, if I could only figure out why my backup server keeps crashing... :(

  13. olehj is the maintainer and it's his choice to do with the plugin what he sees fit.

     

    It is, however, unusual to release to production a version that requires a beta OS release, instead of releasing the plugin as a beta/test/dev release until the OS release that requires the breaking change is into production.

     

    Those who are on 6.12 beta would, I'm sure, be most happy to install the beta version of disklocation to test it out, while the rest of us who are happy to sit on an OS release until the next one is in production (no matter how stable the latest beta might be) are confused by a notification saying our plugin is only compatible with an OS release that doesn't (and won't) exist and come here asking 20 dozen questions about it.

    • Upvote 5
  14. On 11/29/2020 at 1:30 PM, binhex said:

     

    what about the urbackup linux client?, it has statically built dependencies, my unraid server pops up as a client in the urbackup web ui for me, check it out:--https://www.urbackup.org/download.html#linux_all_binary

     

    edit - ran a backup of /tmp for a test and it worked a treat!.

     

    On 11/29/2020 at 1:43 PM, binhex said:

    you can try that, i simply downloaded the script, ran it natively on unraid and voila!, it popped up in urbackup, i could then select a path to backup using the urbackup web ui and run the backup and i could see the files it backed up 🙂 it was pretty much painless tbh.

    Could you give some directions on how to do this, please?

     

    It's been ages since I've messed with a bare metal Unix system (HP-UX anybody? Like last century...). I've only installed plugins & dockers on my unraid box.