further update

it does not need to be reset to default

it simply stopped and then started

@EDACerton

with the logs i supplied

this further lines up with the app/plugin simply starting too soon

please add a delayed start up of X seconds

even better if it simply verifies the availability of disks.ini

and only starts after it is available and readable instead of giving up

Thanks. I’ll dig into it more later this weekend. Sorry for the delay, had other life stuff going on.

This should be fixed in the latest update.

Thank you

Installed update

rebooted

can confirm functional logging after reboot

was i correct about the delay?

is reboot necessary?

Just now, hollowimage said:

is reboot necessary?

to verify that the issue is no longer present?

yes, as the issue only presented itsself after reboot

i can confirm that it now works after reboots without requiring and reset or restart of the app/plugin

9 hours ago, charettepa said:

Thank you

Installed update

rebooted

can confirm functional logging after reboot

was i correct about the delay?

It wasn't a delay... a while back, I switched the configuration from a .cfg (INI) file to a JSON file. The problem is that the scripts that run on array startup were still looking for the old config file. If that file happened to exist (you had an older version of the plugin installed previously, etc.), it worked fine, but if you didn't have that file, the activity watcher wouldn't start when the array did.

Was the download log button removed? I noticed I wasn't on the v2 update having just updated to unraid 7.2.4, when I updated to v2 though I noticed that the download logs button is no longer there, where would I be able to grab the full logs from now?

Hello, I'm trying to pinpoint what's keeping my drive awake. I have found with your plugin that something is regularly traversing my media folder, so most likely culprit is plex/sonarr/radarr, but all the activity shows as PID 8631 and Process Path/usr/libexec/unraid/shfs

Any way to find the actual PID ?

The plugin isn't showing anything; I've enabled all the flags.

It doesn't show MusicBrainz Picard writing to audio files, nor does it show files being moved between directories in Array.

I'm using Unraid 7.3.

yeah im still at a loss here, ive got no activity whatsoever. i rebooted, upgraded to 7.3.1. plugin on latest, but nothing is logged.

everything turned on, even like show me appdata -- i get nada.

Edited Tuesday at 03:47 PM4 days by hollowimage

@EDACerton anything i can help provide here? this is turning into quite a headache and i really would like this thing working.

the only thing i see here:

cat fileactivity-watcher.log

{"level":"info","tag":"2026.05.03.0212","revision":"5736642995d85081b85daba55fa7c6d4970e483d","git_dirty":"no","time":1783439295,"message":"Build information"}

{"level":"info","time":1783439295,"message":"Starting file activity watcher..."}

{"level":"info","Exclusions":["(?i)appdata","(?i)docker","(?i)system","(?i)syslogs"],"Enable":true,"UnassignedDevices":true,"Cache":false,"SSD":false,"DisplayEvents":1000,"MaxRecords":20000,"time":1783439295,"message":"File Activity Watcher Configuration"}

{"level":"info","array_disks":4,"pool_disks":0,"time":1783439295,"message":"Disk count"}

{"level":"warn","error":"open /var/state/unassigned.devices/unassigned.devices.json: no such file or directory","time":1783439295,"message":"Error reading unassigned devices file"}

{"level":"info","disk":"disk1","mountpoint":"/mnt/disk1","type":"data","filesystem":"zfs","rotational":true,"time":1783439295,"message":"Watching disk"}

{"level":"info","disk":"disk2","mountpoint":"/mnt/disk2","type":"data","filesystem":"zfs","rotational":true,"time":1783439295,"message":"Watching disk"}

{"level":"info","disk":"disk3","mountpoint":"/mnt/disk3","type":"data","filesystem":"zfs","rotational":true,"time":1783439295,"message":"Watching disk"}

{"level":"info","disk":"disk4","mountpoint":"/mnt/disk4","type":"data","filesystem":"zfs","rotational":true,"time":1783439295,"message":"Watching disk"}

{"level":"info","count":4,"time":1783439295,"message":"Watch folders"}

{"level":"info","time":1783439295,"message":"Watcher ready"}

{"level":"info","time":1783439295,"message":"Starting event listener..."}

{"level":"info","filter":"(?i)appdata","time":1783439295,"message":"Adding exclusion filter"}

{"level":"info","filter":"(?i)docker","time":1783439295,"message":"Adding exclusion filter"}

{"level":"info","filter":"(?i)system","time":1783439295,"message":"Adding exclusion filter"}

{"level":"info","filter":"(?i)syslogs","time":1783439295,"message":"Adding exclusion filter"}

{"level":"info","current_lines":0,"time":1783439295,"message":"Current activity records"}

{"level":"info","path":"/mnt/disk1","fsid":"807321a982b18d00","time":1783439295,"message":"Cached mount fsid"}

{"level":"info","path":"/mnt/disk2","fsid":"f7805000dffb8a00","time":1783439295,"message":"Cached mount fsid"}

{"level":"info","path":"/mnt/disk3","fsid":"39bd7812c225f700","time":1783439295,"message":"Cached mount fsid"}

{"level":"info","path":"/mnt/disk4","fsid":"953b1740bde4ac00","time":1783439295,"message":"Cached mount fsid"}

is the
{"level":"warn","error":"open /var/state/unassigned.devices/unassigned.devices.json: no such file or directory","time":1783439295,"message":"Error reading unassigned devices file"}

but this file exists at the different path (ini UD vs json that its lookign for):

root@voyager:/var/log# file /var/state/unassigned.devices/unassigned.devices.ini

/var/state/unassigned.devices/unassigned.devices.ini: ASCII text

i saw your comment about the ini to json but i dont think that applied to UD probably.

root@voyager:/var/log# ls -lsa /var/state/unassigned.devices

total 24

0 drwxr-xr-x 2 root root 160 Jul 7 10:43 ./

0 drwxr-xr-x 6 root root 120 Jul 2 13:49 ../

4 -rw-r--r-- 1 root root 60 Jul 2 13:50 device_hosts.json

4 -rw-r--r-- 1 root root 414 Jul 7 10:43 df_status.json

4 -rw-r--r-- 1 root root 126 Jul 7 10:43 disk_names.json

4 -rw-r--r-- 1 root root 328 Jul 7 08:55 ping_status.json

4 -rw-r--r-- 1 root root 329 Jul 7 10:43 share_names.json

4 -rw-r--r-- 1 root root 3419 Jul 2 13:50 unassigned.devices.ini

it looks like root has rights to read this file, as does everyone, really. Otherwise the logs of the watcher itself look good. and yeah, this is running latest 7.3.1 i rebooted a few weeks ago, plugin is updated and has been re-installed a few times.

Edited Tuesday at 04:21 PM4 days by hollowimage

It's been working perfectly for me since the change on May 4th. Are you sure you didn't have any exceptions that conflict with your setup.

like what?