JonD

Hi, It seems the network settings I had with 7.0 are no longer working with 7.2.2. For testing purpose i have disable bonding and rebooted but i still get a different static IP than what is assigned on my router (eero). Unraid is set to IPv4 only and IPv4 is set to automatic like it's always been. Unraid gets IPv4 address: 192.168.0.109 but should use 192.168.0.112 as defined in the router. Mac address matches, there was no change but i double checked just in case. I have not changed any unraid setting and there was a firmware upgrade on the eero side that I am trying to get more information on. I see similar issues with 7.2.2 that may be related? https://forums.unraid.net/topic/195682-unraid-722-unraid-server-randomly-dropping-off-network/ https://forums.unraid.net/topic/195681-intermittent-connection-dropouts-after-update-to-722/ I went through the changelog but nothing stands out as a potential root cause although: 7.1.0: "Fix various issues with DHCP." 7.1.2: "Fix: Allow static IP assignments to co-exist with wireless" (though i dont use wireless) I have submitted feedback with diagnostics and logs in the UI but have no reference or anything to check status. Was there any change related to DCHP / static IP? Update: I changed IPv4 from automatic to static to force .112 and it seems to work but that behavior is a breaking change

Ah thanks! that works better than killing it and i can cron this every day or so until it is fixed PS: After one day, its up to 191.9 MB (from 145MB)

Hi, Unraid RAM showed 90% while I typically sit around 55%. Executed the command below and the biggest entry was > ps aux | awk '{print $6/1024 " MB\t\t" $11}' | sort -n [...] 2459.91 MB /usr/local/bin/unraid-api/unraid-api I killed the process and restarted it using the UI and its back to normal usage (~145.051 MB) unraid version: 6.11.3 My servers version: 2022.11.29.0742