Diagnostics never finishes due to huge # of files

The command being run is "sed -i" as per the attached image:

The GUI execution has now hung here.  There is no file attempting to download.

However a completed file named "unraid-diagnostics-20240408-1001.zip" now exists in /boot/log.

I am unable to refresh the browser tab with the Diagnostics page, nor even change the URL to, say, the Dashboard.  The tab has to be closed and a new unraid tab opened to access the Web GUI again.

I just moved all files off the cache:

 

However when I run the Diagnostics command in the WebGUI agian it is still referring to these files??
 

I have no idea what all this "syslog-previous" stuff is for.

WebGUI just died with this message:

Array stop and reboot is working at this point, after performing the mover.  Will run diagnostics interactively after reboot to see if the mover has all the weird sed commands on non-existent files still.

Post reboot and the GUI diagnostics is still waffling on about these files that just don't exist on the cache drive.

OK, I had to delete the file /boot/logs/syslog-previous to remove the constant banging on about these non-existent files.

Edited April 8 by Kaldek

Changed Priority to Minor

The root cause here appears to be entries in the file /boot/logs/syslog-previous related to the previous execution of the Mover when Mover Logging is enabled.

 

The diagnostics script sees these, and runs the "sed -i" command for every entry found in the syslog-previous file.   Deleting the syslog-previous file stops this issue from occurring, as would not having Mover Logging enabled I suspect.  

I do not recall a warning for Mover logging about it impacting Diagnostics. I know it mentions potentially filling up log files, but not an impact to the diagnostics script.

Mover logging is only supposed to be used to diagnose a mover problem.

Not to be enabled full-time.

18 hours ago, ChatNoir said:

Mover logging is only supposed to be used to diagnose a mover problem.

Not to be enabled full-time.

 

I get that - it's more that this should be a call-out about impact to reboots.  Like, I was utterly confused by this as there was no warning *what* was delaying the reboot.  Lots of unRAID users out there less technical than me.