9 minutes ago, hugenbdd said:

Mover Logging : Enabled. (Up top, schedule area)

 

You can see in your last pic the "mover started.      Mover Finished". at the bottom.  That will expand to a lot more.

 

You will need to browse the individual cache drive or use the console and issue ls commands on the cache.

https://www.tecmint.com/15-basic-ls-command-examples-in-linux/

 

also

https://www.techrepublic.com/article/linux-directory-navigation-tips-and-tricks/#:~:text=To change to your home,and then press [Enter].

ok cool i am trying to figure this out 

thank you 

On 3/16/2021 at 9:33 AM, hugenbdd said:

It's because I left ECHO statements in the script.  These help me catch bugs for the new release.

 

I will release a new version in the next few days that will comment out the echo statements.

 

Hello! Has this happened again? I'm getting emails when the daily cron job runs that say "Mover not Needed." I don't get one every day, I guess only when the mover is not needed.😃

 

Thanks

 

Hey there! I have this plugin installed and set to run the mover at 60% cache utilization with a run frequency of every 3 hours. However, my cache keeps getting over 60% and failing to move. If I run the mover manually it works fine so I changed the 'move now button follows plugin fliters’ option to ‘yes’ and ran it again. Here’s my output:

 

Sep 27 19:05:59 unRaid root: mvlogger: *********************************MOVER START*******************************
Sep 27 19:05:59 unRaid root: mvlogger: Age supplied
Sep 27 19:05:59 unRaid root: mvlogger: Size supplied
Sep 27 19:05:59 unRaid root: mvlogger: Sparness supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Before Script Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No After Script Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: CTIME Argument: no
Sep 27 19:05:59 unRaid root: mvlogger: CACHE THRESH to Move all Cache-Yes shares to array: 65
Sep 27 19:05:59 unRaid root: mvlogger: No Test Mode Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Ignore Hidden Files Argument Supplied
Sep 27 19:05:59 unRaid root: mover: started
Sep 27 19:05:59 unRaid root: mvlogger: No Script to Run.
Sep 27 19:05:59 unRaid root: mvlogger: CACHETHRESH: 65
Sep 27 19:05:59 unRaid root: mvlogger: Checking to see if we should all files from share.
Sep 27 19:05:59 unRaid root: mvlogger: Move All Cache Threshold: 65
Sep 27 19:05:59 unRaid root: mvlogger: /mnt/cache PCT USED: 85
Sep 27 19:05:59 unRaid root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array
Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode
Sep 27 19:05:59 unRaid root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1'
Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find /mnt/cache/media -depth
Sep 27 19:05:59 unRaid root: mvlogger: Done checking Move All from Share
Sep 27 19:05:59 unRaid root: mvlogger: Share Name Only: Media
Sep 27 19:05:59 unRaid root: mvlogger: Cache Pool Name: cache 
Sep 27 19:05:59 unRaid root: mvlogger: cache Threshold Pct: 
Sep 27 19:05:59 unRaid root: mvlogger: OVERALL Threshold: 60
Sep 27 19:05:59 unRaid root: mvlogger: Share Path: /mnt/cache/Media
Sep 27 19:05:59 unRaid root: mvlogger: Pool Pct Used: 85 %
Sep 27 19:05:59 unRaid root: mvlogger: DFTPCT LIMIT USED FOR SETTING: 60
Sep 27 19:05:59 unRaid root: mvlogger: Threshold Used: 60
Sep 27 19:05:59 unRaid root: mvlogger: Adding Age
Sep 27 19:05:59 unRaid root: mvlogger: Age 1
Sep 27 19:05:59 unRaid root: mvlogger: Skipfiletypes string: find "/mnt/cache/Media" -depth -mtime +1
Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode
Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find "/mnt/cache/Media" -depth -mtime +1
Sep 27 19:05:59 unRaid root: find: '/mnt/cache/Media': No such file or directory
Sep 27 19:05:59 unRaid root: mover: finished
Sep 27 19:05:59 unRaid root: mvlogger: No After Script to Run.

 

and some settings for reference:
 

 

Any thoughts on what might be happening?

9 hours ago, jcato said:

 

Hello! Has this happened again? I'm getting emails when the daily cron job runs that say "Mover not Needed." I don't get one every day, I guess only when the mover is not needed.😃

 

Thanks

 

I'll check the code but should only be happening when logging is enabled....

5 hours ago, polishprocessors said:

Hey there! I have this plugin installed and set to run the mover at 60% cache utilization with a run frequency of every 3 hours. However, my cache keeps getting over 60% and failing to move. If I run the mover manually it works fine so I changed the 'move now button follows plugin fliters’ option to ‘yes’ and ran it again. Here’s my output:

 

Sep 27 19:05:59 unRaid root: mvlogger: *********************************MOVER START*******************************
Sep 27 19:05:59 unRaid root: mvlogger: Age supplied
Sep 27 19:05:59 unRaid root: mvlogger: Size supplied
Sep 27 19:05:59 unRaid root: mvlogger: Sparness supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Skipfiles Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Before Script Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No After Script Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: CTIME Argument: no
Sep 27 19:05:59 unRaid root: mvlogger: CACHE THRESH to Move all Cache-Yes shares to array: 65
Sep 27 19:05:59 unRaid root: mvlogger: No Test Mode Argument Supplied
Sep 27 19:05:59 unRaid root: mvlogger: No Ignore Hidden Files Argument Supplied
Sep 27 19:05:59 unRaid root: mover: started
Sep 27 19:05:59 unRaid root: mvlogger: No Script to Run.
Sep 27 19:05:59 unRaid root: mvlogger: CACHETHRESH: 65
Sep 27 19:05:59 unRaid root: mvlogger: Checking to see if we should all files from share.
Sep 27 19:05:59 unRaid root: mvlogger: Move All Cache Threshold: 65
Sep 27 19:05:59 unRaid root: mvlogger: /mnt/cache PCT USED: 85
Sep 27 19:05:59 unRaid root: mvlogger: Pool /mnt/cache is above 'move all' percentage, moving all cache-yes shares to array
Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode
Sep 27 19:05:59 unRaid root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1'
Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find /mnt/cache/media -depth
Sep 27 19:05:59 unRaid root: mvlogger: Done checking Move All from Share
Sep 27 19:05:59 unRaid root: mvlogger: Share Name Only: Media
Sep 27 19:05:59 unRaid root: mvlogger: Cache Pool Name: cache 
Sep 27 19:05:59 unRaid root: mvlogger: cache Threshold Pct: 
Sep 27 19:05:59 unRaid root: mvlogger: OVERALL Threshold: 60
Sep 27 19:05:59 unRaid root: mvlogger: Share Path: /mnt/cache/Media
Sep 27 19:05:59 unRaid root: mvlogger: Pool Pct Used: 85 %
Sep 27 19:05:59 unRaid root: mvlogger: DFTPCT LIMIT USED FOR SETTING: 60
Sep 27 19:05:59 unRaid root: mvlogger: Threshold Used: 60
Sep 27 19:05:59 unRaid root: mvlogger: Adding Age
Sep 27 19:05:59 unRaid root: mvlogger: Age 1
Sep 27 19:05:59 unRaid root: mvlogger: Skipfiletypes string: find "/mnt/cache/Media" -depth -mtime +1
Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode
Sep 27 19:05:59 unRaid root: mvlogger: Complete Mover Command: find "/mnt/cache/Media" -depth -mtime +1
Sep 27 19:05:59 unRaid root: find: '/mnt/cache/Media': No such file or directory
Sep 27 19:05:59 unRaid root: mover: finished
Sep 27 19:05:59 unRaid root: mvlogger: No After Script to Run.

 

and some settings for reference:
 

 

Any thoughts on what might be happening?

Looks like it might be a share name issue.

 

Sep 27 19:05:59 unRaid root: mvlogger: Not in Test mode Sep 27 19:05:59 unRaid root: find: unknown predicate `-depth+= | /usr/local/sbin/move -d 1'

 

Is the share name media or Media. (lower versus upper).  Seems also maybe a configuration file may have a mismatch in it to cause the issue above.

Ahh, yes, I changed my media folder to lower-case m to avoid issues elsewhere. Where can I adjust the config file to fix this…?

1 hour ago, polishprocessors said:

Ahh, yes, I changed my media folder to lower-case m to avoid issues elsewhere. Where can I adjust the config file to fix this…?

Make sure the file matches in here.
/boot/config/shares

On 9/27/2021 at 8:51 AM, jcato said:

 

Hello! Has this happened again? I'm getting emails when the daily cron job runs that say "Mover not Needed." I don't get one every day, I guess only when the mover is not needed.😃

 

Thanks

 

There was an Echo in there for that statement.  Next release will have it updated to follow the logging settings. (But that may be a while...)

 

If you want to fix it now.

Line 396 of /usr/local/emhttp/plugins/ca.mover.tuning/age_mover

Change

echo "mover not Needed."

 

to

 

mvlogger "Mover not Needed."

 

17 minutes ago, hugenbdd said:

Make sure the file matches in here.
/boot/config/shares

Actually I had renamed my Media folder to media but it shows up in /boot/config/shares as Media.cfg

Think it’s safe to rename that to media.cfg ?

On 9/28/2021 at 11:26 AM, hugenbdd said:

There was an Echo in there for that statement.  Next release will have it updated to follow the logging settings. (But that may be a while...)

 

If you want to fix it now.

Line 396 of /usr/local/emhttp/plugins/ca.mover.tuning/age_mover

Change

echo "mover not Needed."

 

to

 

mvlogger "Mover not Needed."

 

I made this change and emails stopped. But, then they started again. I rechecked the file and it's back to an echo statement.

 

I think it's because I rebooted. Does this change not survive a reboot? If so, is there a way to make it permanent?

 

 

5 hours ago, jcato said:

I made this change and emails stopped. But, then they started again. I rechecked the file and it's back to an echo statement.

 

I think it's because I rebooted. Does this change not survive a reboot? If so, is there a way to make it permanent?

 

 

Probably doesn't survive reboot.

 

I'll work on a release in the next few days.

On 9/28/2021 at 11:39 AM, polishprocessors said:

Actually I had renamed my Media folder to media but it shows up in /boot/config/shares as Media.cfg

Think it’s safe to rename that to media.cfg ?

I think you will be okay... but make a backup of the file just in case.

Hello,

I'm trying to run a simple stop then start script with the user.scripts plugin but it doesn't what to run the scripts it looks like. When I got to check if the dockers have been stopped they have not. So my question is, where does this go to look for the before/after scripts? As well as how can I point this to the user scripts?

I have a problem setting up a text file with excluded paths. Whenever i set it up to exclude a single path, it work fine, but i just tried to make a file that has multiple lines in it, and it only excludes the last line in the file whenever it starts moving.

 

These are the three lines that i have in the file currently:

/mnt/cache/Media/Downloads
/mnt/cache/Syncthing/Telefoonbackup
/mnt/cache/Syncthing/Overdracht

 

But when running the mover, it only excludes /mnt/cache/Syncthing/Overdracht

 

I am positive that there are no spelling errors in the paths used, should i be using a different way to seperate them in the text file, instead of putting each path on a seperate line?

 

Any help would be appreciated.

 

5 hours ago, Tune said:

I have a problem setting up a text file with excluded paths. Whenever i set it up to exclude a single path, it work fine, but i just tried to make a file that has multiple lines in it, and it only excludes the last line in the file whenever it starts moving.

 

These are the three lines that i have in the file currently:

/mnt/cache/Media/Downloads
/mnt/cache/Syncthing/Telefoonbackup
/mnt/cache/Syncthing/Overdracht

 

But when running the mover, it only excludes /mnt/cache/Syncthing/Overdracht

 

I am positive that there are no spelling errors in the paths used, should i be using a different way to seperate them in the text file, instead of putting each path on a seperate line?

 

Any help would be appreciated.

 

Make sure logging is on.

Move Now button follows plug-in filters (Yes)

Turn on test mode (Very bottom)

 

 

Test each directory one at a time in your file.

 

It's possible there are control characters for the end of line if you created the file in windows.  If you created it with vi editor or from the command line this should not be the case.

 

2 hours ago, hugenbdd said:

Make sure logging is on.

Move Now button follows plug-in filters (Yes)

Turn on test mode (Very bottom)

 

 

Test each directory one at a time in your file.

 

It's possible there are control characters for the end of line if you created the file in windows.  If you created it with vi editor or from the command line this should not be the case.

 

Hey, thank you for taking the time to try and help me with this, i did have the settings on  that you mentioned here, and i used the test mode to come to the results I have at the moment.

I'll try recreating the file via command line as i have indeed created it in windows, I will report back later how this goes, thank you!

 

Edit: I just recreated the file using nano in the command line, and jus retyping the lines instead of copying them. Using the test mode of mover tuning it all seems to work now. So it seems that using Windows to create the file and edit it was indeed the issue, thank you for helping me out!

Edited October 10, 20214 yr by Tune
Reporting back

1 hour ago, Tune said:

Edit: I just recreated the file using nano in the command line, and jus retyping the lines instead of copying them. Using the test mode of mover tuning it all seems to work now. So it seems that using Windows to create the file and edit it was indeed the issue, thank you for helping me out!

Great!

In normal Linux dos2unix will take care of this.  There is a "end of line" character difference between Windows & Unix. Sometimes they show ^M if you print the file from the command line.

On 10/5/2021 at 8:49 AM, jcato said:

I made this change and emails stopped. But, then they started again. I rechecked the file and it's back to an echo statement.

 

I think it's because I rebooted. Does this change not survive a reboot? If so, is there a way to make it permanent?

 

 

New Release to fix this issue.

It seems that in May, the release notes decided to travel back in time 

 

 

21 minutes ago, KnifeFed said:

It seems that in May, the release notes decided to travel back in time 

 

 

Dooph!

I'm still living in 2020 don't ruin my reality and don't tell me what happens in 2021....

 

Fixed...

I’m trying to get this plugin configured but can’t seem to get it right. My goal is to get this plugin to run mover if the cache is above a set percentage and also at a set time every 24 hours regardless of used space.

 

Settings-

 

@hugenbdd I believe we discussed this in a previous post and at that time it wasn't possible to use both features together but I saw there have been changes and wanted to try again. The screenshots show both features enabled. Move files with disk usage above 40% and force move of all files at 3:30am. I have filled the cache disk to about 65% but mover doesn't run after waiting about 3 hours. I tried disabling "force move of all files" and waited again but still nothing. Have I gotten something else mis-configured?

11 minutes ago, wgstarks said:

I’m trying to get this plugin configured but can’t seem to get it right. My goal is to get this plugin to run mover if the cache is above a set percentage and also at a set time every 24 hours regardless of used space.

 

Settings-

 

@hugenbdd I believe we discussed this in a previous post and at that time it wasn't possible to use both features together but I saw there have been changes and wanted to try again. The screenshots show both features enabled. Move files with disk usage above 40% and force move of all files at 3:30am. I have filled the cache disk to about 65% but mover doesn't run after waiting about 3 hours. I tried disabling "force move of all files" and waited again but still nothing. Have I gotten something else mis-configured?

 

Looks right..

Can you enable logging and post the log entries?  Then I can track down the issue.

1 hour ago, hugenbdd said:

 

Looks right..

Can you enable logging and post the log entries?  Then I can track down the issue.

I may have found the issue-

 

 

Does the traditional mover schedule effect when the actions set in the tuning settings are performed? Seem to remember that it does. I set this to hourly and mover ran on the hour. Still testing to be sure the filters are being respected though. I've enabled logging and will include them in my next post if I'm still having issues.

seems like the plugin is broken. Mover worked without it, but it caused 100% CPU usage and IO Wait to level that plex didnt work anymore. So I installed the plugin - which made my cache drive to fill up to 100% and all docker stopped.

I had to remove it again. Someone else have this problem?

3 minutes ago, gandalf15 said:

which made my cache drive to fill up to 100%

That *implies* that you've got your shares set to be "Cache:Prefer" instead of "Cache:Yes" (assuming that the plugin does actually still work)