Waddoo

Did you resolve your issue? I am seeing this on the latest Unraid version myself. Been removing custom themes and other dynamixs items like crazy. Replaced my flash drive, and currently uninstalled (and will re-install) the NVIDIA driver plugin.

I cannot find this when searching, however I cannot determine why this is occurring my paperless-ngx stack. When creating the compose file, environment, etc. in the Unraid GUI and selecting compose up, I do not get an output when running docker compose ps Any reasoning or ideas as to why? Image showing that paperless-ngx is running by the Unraid GUI, but not appearing when running the docker compose ps command.

Chiming in as I am seeing the same consistent log on my htop running Unraid 7.0.1 with various dockers though many unchanged from previous 6.9.X versions. /usr/bin/dockerd -p /var/run/dockerd.pid --log-opt max-size=50M --log-opt max-file=2 --log-level=fatal --storage-driver=btrfs Running an integrity check seems to also be affected: Build Finished - added 4 files. Duration: 00:02:24. Average speed: 100 B/s

Unfortunately I am not familiar with that command and likewise unsure if Unraid's docker compose implementation is playing a role. Reach out to their discord, they are helpful there as well. Be sure to search first! Unfortunately, I have stopped using Authentik, it became too much to maintain and connect all of my services with the amount of time I have in my day.

Remember to replace username with the username for the user you want to create. Also this command is ment for docker compose, if you are not using docker compose this will not work. Lastly, the docker compose command should be run in Urnaids console not Authentiks.

Any reason why my other Unraid PC cannot mount this NFS share? ``` Jan 1 11:19:50 Server_Main unassigned.devices: NFS mount failed: 'mount.nfs4: access denied by server while mounting OFFSITEBACKUP.LOCAL:/mnt/bigdrive'. Jan 1 11:19:50 Server_Main unassigned.devices: Remote Share 'OFFSITEBACKUP.LOCAL:/mnt/bigdrive' failed to mount. ```

Was this the culprit? My Unraid running 6.12.10, I can ssh and access other dockers, but not the webgui.

Would that mean I would need to pass these arguments as logic into an rclone script? For context, I have the backup run at 0245 and then have a rclone script to push the backups into the cloud at 0600. I tried putting the third flag in an if statement and still not running: # Check if the third argument is "true" if [ "$3" = "true" ]; then echo "Deleting previous log" rm /mnt/user/backups/BackBlaze_Logs/backups_log.txt echo "Running RClone Sync of backups Share to B2 backups Bucket" rclone sync \ --progress \ --stats-one-line-date \ --transfers 4 \ --verbose \ --exclude ".Recycle.Bin/**" \ --exclude "UniFi_Protect/**" \ --links \ --log-file /mnt/user/backups/BackBlaze_Logs/backups_log.txt \ /mnt/user/backups/ \ b2_buckets:my_bucket echo "Updating permissions of log file" chmod 755 /mnt/user/backups/BackBlaze_Logs/backups_log.txt else echo "Skipping backup operation as the third argument is not 'true'" fi

Highly doubt it. Checksum relies on a single file to have a checksum against. I think the only way of generating a single checksum of your files is to zip/tar/compress them and checksum that each time.

Ran verification last night, same results where I continue to get emails of updated .nfo files from the media and Nextcloud shares. Likewise, exclusion rules do not seem to be respected. Will there be upcoming updates to the app to not have updated hashes email and only include those that are corrupted?

I am currently trying to iron out my file integrity plugin's settings however, I currently have multiple excluded shares and custom files that continue to appear on my verification's logs. Namely Nextcloud and media. Linux ISOs. and *.log files appearing in the logs results. Is there something I am not selecting correctly in the checkbox for excluded shares? What is the proper format to exclude multiple custom files? It reads: However I am finding that `*.nfo, *.log` files continue to appear in the logs, even for modifications? I am running Unraid 6.11.5 and have attached a screenshot of my settings and a snippet of the verification log. Thanks and any help would be greatly appreciated. Event: unRAID file corruption Subject: Notice [ALEXANDRIA] - bunker verify command Description: Found 2 files with MD5 hash key corruption Importance: alert MD5 hash key mismatch, /mnt/disk2/backups/Unraid/CA_Backup/Appdata_Backup/[email protected]/CA_backup.tar is corrupted MD5 hash key mismatch, /mnt/disk2/backups/Unraid/CA_Backup/Appdata_Backup/[email protected]/backup.log is corrupted MD5 hash key mismatch (updated), /mnt/disk2/media/LINUXISO/mint.nfo was modified

So turns out, in Unraid version 6.10, there is a change/update to this. I am running unraid 6.9.X for context. The Unraid version after what I am currently running [link](https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Docker): > The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require reconfiguring anything on the Docker level, internally everything is being taken care of. Sigh, maybe it's time to upgrade sooner than later.

Yes, in-fact it just crashed recently... Apr 25 12:04:41 Alexandria kernel: WARNING: CPU: 9 PID: 20303 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Apr 25 12:04:41 Alexandria kernel: Modules linked in: nvidia_uvm(PO) xt_mark macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs nfsd lockd grace sunrpc md_mod nvidia_drm(PO) nvidia_modeset(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(PO) drm backlight agpgart iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables mlx4_en mlx4_core r8169 realtek edac_mce_amd kvm_amd kvm mpt3sas crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd wmi_bmof i2c_piix4 glue_helper i2c_core wmi raid_class scsi_transport_sas k10temp Apr 25 12:04:41 Alexandria kernel: ccp ahci rapl libahci button acpi_cpufreq [last unloaded: mlx4_core] Apr 25 12:04:41 Alexandria kernel: CPU: 9 PID: 20303 Comm: kworker/9:2 Tainted: P S O 5.10.28-Unraid #1 Apr 25 12:04:41 Alexandria kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B79/X470 GAMING PLUS MAX (MS-7B79), BIOS H.60 06/11/2020 Apr 25 12:04:41 Alexandria kernel: Workqueue: events macvlan_process_broadcast [macvlan] Apr 25 12:04:41 Alexandria kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Unsure what to do next about this issue, we aren't even running similar hardware based on your logs.

All of my"public" containers remain accessible through my domain on nginx. I'm not sure if that is because I do not hard code IPs but unsure of y'all's setup.

Will the changing of the network type affect my driver network as it is? Or nginx for example?