Freender

Script: https://github.com/freender/mover_tunning_daysold/blob/main/calculate_daysold.sh

I decided to set global "Move files that are greater than this many days old" = 1 "Only move at this threshold of used cache space" = 0% and override it for media share as "Move files that are greater than this many days old" = 60 20 minutes before mover runs, I dynamically calculate daysold and update corresponding daysold parameter in /boot/config/plugins/ca.mover.tuning/shareOverrideConfig/media.cfg Script starts with 60 days and decreases by 5 (55, 50, 45 ... ) if target cache free space criteria is not met ( In my case it's 370GB). I will keep it running for couple of days, if stable might share if somebody is interested

Thanks for reporting an issue. I can confirm SLAAC IPv6 auto assignment doesn’t work as well

Per container exclusions never worked for me. Am I missing something?

I use UDMP, - removed all old macvlan static IPs - In my 192.168.86.0/24 I changed DHCP range to 192.168.86.2 - 192.168.86.172 - moved all ipvlan containers to new address space 192.168.86.173 - 192.168.86.253 (not managed by DHCP) However this made 0 effect, still having connectivity issues =(

1) Docker custom network type: ipvlan, Host access to custom networks: Disabled In this configuration I don't have any issues 2) Docker custom network type: ipvlan Host access to custom networks: Enabled After a couple of minutes I cannot ping 8.8.8.8 from unraid SSH. I think there is something wrong with ipvlan + shim interface configuration

Upgrading from rc4 - there are no issues

Memory test was successful, might also run it again overnight. Cache pool looks healthy after rebooting Topic can be closed UUID: 2dd181dd-c2fb-4c7f-b9e7-af5b707f89f2 Scrub started: Thu May 5 15:57:19 2022 Status: finished Duration: 0:03:08 Total to scrub: 580.62GiB Rate: 3.09GiB/s Error summary: no errors found

The RAM was running on not standard timings, reverted to auto and started Memtest. Thanks for your tips

May 5 07:03:52 Tower root: /var/lib/docker: 3.6 GiB (3892211712 bytes) trimmed on /dev/loop2 May 5 07:03:52 Tower root: /mnt/cache: 121 GiB (129878523904 bytes) trimmed on /dev/nvme0n1p1 May 5 07:55:12 Tower kernel: BTRFS critical (device nvme0n1p1): corrupt leaf: root=10 block=2644209385472 slot=296, unexpected item end, have 2140948741 expect 16259 May 5 07:55:12 Tower kernel: BTRFS info (device nvme0n1p1): leaf 2644209385472 gen 635469 total ptrs 590 free space 1493 owner 10 May 5 07:55:12 Tower kernel: item 0 key (2493317468160 199 167936) itemoff 16283 itemsize 0 May 5 07:55:12 Tower kernel: item 1 key (2493317644288 198 1073741824) itemoff 16275 itemsize 8 May 5 07:55:12 Tower kernel: item 2 key (2493330280448 199 4096) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 3 key (2493330288640 199 4096) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 4 key (2493330300928 199 4096) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 5 key (2493330849792 199 114688) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 6 key (2493339525120 199 24576) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 7 key (2493339557888 199 49152) itemoff 16275 itemsize 0 May 5 07:55:12 Tower kernel: item 8 key (2493339623424 199 40960) itemoff 16275 itemsize 0 ... May 5 07:55:12 Tower kernel: item 586 key (2498537791488 199 49152) itemoff 16243 itemsize 0 May 5 07:55:12 Tower kernel: item 587 key (2498546405376 199 135168) itemoff 16243 itemsize 0 May 5 07:55:12 Tower kernel: item 588 key (2498671570944 199 12288) itemoff 16243 itemsize 0 May 5 07:55:12 Tower kernel: item 589 key (2498671603712 199 4096) itemoff 16243 itemsize 0 May 5 07:55:12 Tower kernel: BTRFS error (device nvme0n1p1): block=2644209385472 write time tree block corruption detected May 5 07:55:12 Tower kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2438: errno=-5 IO failure (Error while writing out transaction) May 5 07:55:12 Tower kernel: BTRFS info (device nvme0n1p1): forced readonly Hi All, do we have any guide I can follow for similar type of issues? Diagnostics attached tower-diagnostics-20220505-1235.zip

What I did: 1) Stop all docker containers 2) Go to Settings -> Docker 3) Set Enable Docker: No Preserve user defined networks: No Host access to custom networks: Disables 4) Install RC5 5) Reboot 6) Go to Settings -> Docker 7) Set Enable Docker: Yes Preserve user defined networks: Yes Host access to custom networks: Enabled

I decided to give rc5 another try: deleted all custom docker networks and upgraded to RC5 - no issues so far.

Upgraded from rc4 to rc5 - a few hours later unraid was not available over ssh. I did hard reset and rollbacked to rc4. I managed to pull syslog from the Graylog, see attached (let me know if something needs to be obfuscated) Might be related to this issue - https://lore.kernel.org/netdev/YfQMQWsFqCIPBBqO@boxer/T/ Docker config: Docker custom network type: macvlan Host access to custom networks: Enabled I also use IPv6 Network Cards: IOMMU group 16:[8086:10fb] 01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) IOMMU group 17:[8086:10fb] 01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) syslog_rc5.csv

See resolution here - https://www.reddit.com/r/unRAID/comments/n4gium/how_to_fix_system_logs_for_unraid_behind_reverse/ The topic can be closed

Seems like we should be ready to implement InfluxDB 2.0 support to this container:

Please let me know if any additional information is required Thanks, Michael

TC: 1. Install NGINX proxy manager 2. Add HTTPS proxy host with Websockets Support + Force SSL + HTTP/2 (see automatically generated config in previous comment) 3. Login to Unraid over proxy host 4. In right top corner click on [log] button *Expected Result:* Unraid shows logs in popup window *Actual Result:* Unraid shows blank popup window which is continuously loading. After 1.5 minutes NGINX closes connection. 2021/02/04 04:36:53 [error] 10035#10035: *35593 upstream timed out (110: Operation timed out) while reading upstream, client: **, server: tower.**, request: "POST /logging.htm HTTP/2.0", upstream: "https://192.168.86. 173:1443/logging.htm", host: "tower.**", referrer: "https://tower.**/Main"

I am using Version: 6.9.0-rc2, Browser - Chrome and Vivaldi. Ad blocker is disabled for both browsers. For direct connection by local IP it works just fine. However it doesn't work over reverse proxy (NGINX) See NGINX config attached 16.conf.txt

Really weird issue. I believe browser shows ERR_HTTP2_PROTOCOL_ERROR due to call rejected by NGINX. The rejection is caused by 1.5 minute timeout. I can confirm the issue is reproducible: 2021/02/04 04:36:53 [error] 10035#10035: *35593 upstream timed out (110: Operation timed out) while reading upstream, client: **, server: tower.**, request: "POST /logging.htm HTTP/2.0", upstream: "https://192.168.86. 173:1443/logging.htm", host: "tower.**", referrer: "https://tower.**/Main"

Thanks Brian! This is exactly what I was looking for. I have added a couple of screenshots in case somebody like me is strangling to make it work with grafana:

Unraid -> Settings -> Nerd Pack -> Search by libffi and install latest version