Revan335

Maybe can help the Spaceinvader Scripts: https://github.com/SpaceinvaderOne He create a Script for ZFS like Converting Folder to Datasets, listing, ... Maybe can used this for improved your Plugin.

Ich meine man könnte mit der aktuellen 6.12 den Mover pro Share aktivieren ohne Mover Tuning Plugin. Im jeweiligen Share ist dann ein Move Button.

Can I fix this?

I don't have two Exclusions but the one i have is: Aux SSD/Priority Share/Folder1 In your example. Without ' or ,

Maybe I got it: -i --log=/var/lib/clamav/log.log --max-filesize=2048M --max-scansize=2048M --file-list=/var/lib/clamav/clamavtargets.txt Without the -f I monitoring this. At the next run. Can you update the Template with the new Information's/Parameters?

This is a directory? This is the Entry of scanfiles but than he is a txt file and not a directory? And without the -f Parameter? For example /scan/download/testfolder

SSH klingt aber danach das dem User Root Rechte gewährt werden? Den soweit ich weiß gibt es nur den Root User der irgendwas machen kann.

OK, without that. Its Running longer. This is the actually log: 2024-02-07T17:21:25+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Wed Feb 7 17:21:26 2024 daily database available for update (local version: 27177, remote version: 27178) Testing database: '/var/lib/clamav/tmp.ca29159519/clamav-29d3efd36d02b5b2da1c73d66e4f2cac.tmp-daily.cld' ... Database test passed. daily.cld updated (version: 27178, sigs: 2052470, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory Freshclam updated the DB ClamAV 1.2.1/27178/Wed Feb 7 10:35:39 2024 Scanning /scan But why have my two Servers this Permission Error? With or without the Improved Script from @Masterwishx

Container like PlexRipper are false detected as Plex Media Server.

Wie wurde der den erstellt? Normalerweise startet der direkt wenn von dem gebootet wird. Raspberry Pi muss ja auch irgendeine Art BIOS und Bootmenü haben wo man auswählt von wo man booten möchte. OK, das mit ARM erledigt das Problem.

docker run -d --name='ClamAV' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="***" -e HOST_CONTAINERNAME="ClamAV" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://github.com/tquizzle/clamav-alpine/blob/master/img/clamav.png?raw=1' -v '/mnt/user':'/scan':'ro' -v '/mnt/user/appdata/clamav':'/var/lib/clamav':'rw' 'tquinnelly/clamav-alpine' -i --log=/var/lib/clamav/log.log --max-filesize=2048M --max-scansize=2048M -f --file-list=/scan/appdata/clamav/clamavtargets.txt Yes, its mounted from the Default Template. With this, we became the same error: docker run -d --name='ClamAV' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="***" -e HOST_CONTAINERNAME="ClamAV" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://github.com/tquizzle/clamav-alpine/blob/master/img/clamav.png?raw=1' -v '/mnt/user':'/scan':'ro' -v '/mnt/user/appdata/clamav':'/var/lib/clamav':'rw' 'tquinnelly/clamav-alpine' -i --log=/var/lib/clamav/log.log --max-filesize=2048M --max-scansize=2048M -f --file-list=/var/lib/clamav/clamavtargets.txt WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file --file-list=/var/lib/clamav/clamavtargets.txt 2024-02-06T13:44:10+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Tue Feb 6 13:44:10 2024 daily.cld database is up-to-date (version: 27177, sigs: 2052428, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27177/Tue Feb 6 10:34:50 2024 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8684298 Engine version: 1.2.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 12.888 sec (0 m 12 s) Start Date: 2024:02:06 13:44:10 End Date: 2024:02:06 13:44:23

Read is exist for everyone.

Whats Permissisons are needed?

The Log is not realy full. From the Logs from the appdata Folder. 2024-02-05T18:00:01+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Mon Feb 5 18:00:01 2024 daily database available for update (local version: 27175, remote version: 27176) Testing database: '/var/lib/clamav/tmp.f4fcca8fc9/clamav-c9679ca3d16a35cbd8ef83a889b2effa.tmp-daily.cld' ... Database test passed. daily.cld updated (version: 27176, sigs: 2052336, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27176/Mon Feb 5 10:35:30 2024 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8684206 Engine version: 1.2.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 13.233 sec (0 m 13 s) Start Date: 2024:02:05 18:00:07 End Date: 2024:02:05 18:00:20 The Docker Container Log: WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory LibClamAV Warning: Max file-size was set to 4294967296 bytes. Unfortunately, scanning files greater than 2147483647 bytes (2 GiB - 1) is not supported. WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt LibClamAV Warning: Max file-size was set to 4294967296 bytes. Unfortunately, scanning files greater than 2147483647 bytes (2 GiB - 1) is not supported. WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt WARNING: Clamd was NOT notified: Can't connect to clamd through /run/clamav/clamd.sock: No such file or directory LibClamAV Warning: Max file-size was set to 4294967296 bytes. Unfortunately, scanning files greater than 2147483647 bytes (2 GiB - 1) is not supported. WARNING: Only scanning files from --file-list (files passed at cmdline are ignored) ERROR: --file-list: Can't open file /scan/appdata/clamav/clamavtargets.txt bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27175/Sun Feb 4 10:36:45 2024 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8684116 Engine version: 1.2.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 13.054 sec (0 m 13 s) Start Date: 2024:02:04 12:04:34 End Date: 2024:02:04 12:04:47 2024-02-04T18:00:01+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Sun Feb 4 18:00:01 2024 daily.cld database is up-to-date (version: 27175, sigs: 2052246, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27175/Sun Feb 4 10:36:45 2024 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8684116 Engine version: 1.2.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 12.743 sec (0 m 12 s) Start Date: 2024:02:04 18:00:01 End Date: 2024:02:04 18:00:14 2024-02-05T18:00:01+01:00 ClamAV process starting Unpdating ClamAV scan DB ClamAV update process started at Mon Feb 5 18:00:01 2024 daily database available for update (local version: 27175, remote version: 27176) Testing database: '/var/lib/clamav/tmp.f4fcca8fc9/clamav-c9679ca3d16a35cbd8ef83a889b2effa.tmp-daily.cld' ... Database test passed. daily.cld updated (version: 27176, sigs: 2052336, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg) Freshclam updated the DB ClamAV 1.2.1/27176/Mon Feb 5 10:35:30 2024 Scanning /scan ----------- SCAN SUMMARY ----------- Known viruses: 8684206 Engine version: 1.2.1 Scanned directories: 0 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Data read: 0.00 MB (ratio 0.00:1) Time: 13.233 sec (0 m 13 s) Start Date: 2024:02:05 18:00:07 End Date: 2024:02:05 18:00:20 ** Drücke eine BELIEBIGE TASTE, um dieses Fenster zu schließen ** Apparently something has been changed in the max file size. I change this Parameter to 2 GB. Here the Files from the appdata Folder. # ls -la /mnt/user/appdata/clamav/ total 361649 drwxrwxrwx 2 nobody users 9 Feb 5 22:06 ./ drwxrwxrwx 33 nobody users 33 Nov 3 21:38 ../ -rw-r--r-- 1 100 console 291965 Apr 7 2023 bytecode.cvd -rw-r--r-- 1 root root 990 Feb 5 18:00 clamavloglast.txt -rw-r--r-- 1 root root 895 Feb 5 18:00 clamavmaplog.txt -rw-r--r-- 1 root root 215 Feb 5 18:00 clamavtargets.txt -rw-r--r-- 1 100 console 198986752 Feb 5 18:00 daily.cld -rw-r--r-- 1 100 console 69 Apr 24 2022 freshclam.dat -rw-r--r-- 1 100 console 170479789 Apr 24 2022 main.cvd

A Scan Time from under 1 Minute is very strange. That's to fast! For multiple Folders or generally. Who can I see the reason and fix that?

Can you add the deprecation to fix common problems or Communication Applications to notify all Users that's are using the old Version about the new Version? @Squid

I have problems sometimes? too. ZFS and Datasets on Raid 1. 2x NVMes. Then I must remove this empty Folders/Datasets manually.

Its ZFS or Datasets involved?

Hiermit kann man die Error Mails filtern:

Denke nicht. Hab aber auch da noch keine Erfahrungswerte. War mir nur aufgefallen und musste schon den USB Anschluss wechseln weil der Kühlkörper sonst Kontakt mit den Lötstellen auf des USB Adapters hatte. Die sind auf der Rückseite etwas erhaben. So ähnlich sieht das Teil aus.

Die beiden Einzel Adapter laufen nun im Hauptsystem mit Samsung 980 Pro 1 TB. Somit wären alle Slots bis auf den 1x oder war es ein 4x belegt. Künftig muss dann Bifurkation oder ein 1/4x Karte ran. Da ist kaum Luft (1-2/3 Millimeter vielleicht) zwischen dem unteren Adapter/Kühlkörper und der Platine des USB Adapters im USB Board Anschluss für den Unraid Stick.

Ist sowieso komisch. Da es mit anderen Latenz Stufen in der Vergangenheit auch besser war (weniger Meldungen). Die inzwischen aber nicht mehr gereicht haben. Egal ob nun mit Adapter oder direkt auf dem Mainboard. Besonders das Latenz 0 keinen sichtlichen Effekt brachte wo dieser doch ebenfalls alle Ernergiesparmodi für die NVMes deaktivieren sollte und somit keine Meldungen produzieren sollte. Wurde vielleicht am Kernel/Parametern was geändert? Aber da fällt mir gerade ein, SATA Adapter (für mehr SATA Anschlüsse) produzieren solche Meldungen nicht oder? In den Meldungen wird wird ja klar von nvme gesprochen. Solche Adapter haben ja keine Ernergiesparmodi und Fehlerkorrektur soweit ich weiß.

Ohne Adapter und mit pcie_aspm=off bekomme ich nun keine Meldungen mehr. Echt schade das der Parameter mit Latency 0 nicht gereicht hat.

Yes, after Reboot all Access are revoked and the folder .... is free.

This is mostly a indicated for access from other Sites. For example Docker Container, File Manager, Antivirus, mover, ... that's in the Directory or have a open File in this.