Marcvz

Well, the problem I'm having is that my cache disk is filling up. My previous configuration checked every hour if the cache disk was >xx% full. If so, it would move all files (that should be moves) to the array. Every night at 05.00 it would move all the files it can move, regardless of how full the cache disk is. Before moving, a script is run to stop certain containers to unlock files. After the move, they were started again. Exactly what I need. But after a waterfall of updates, something stopped working. That not the first time. Previous time, it was fixed after I've made a post and changes were made to the plugin. So I was hoping the problem would fix itself in a future update. But nope.. multiple updates later and it's still not working. And I've been to busy with other stuff to troubleshoot this thing. So now I'm clicking the move button every night before I go to bed.

I really dont get all the updates. It went from a perfectly fine plugin that did everything I need to a broken mess the last couple months.

It works again! :) Thanks a lot!

Yes. Same settings. If I run the update, it stops working. And if I remove it and reinstall, reapply the settings, it also won't work. It seems to be a combination of settings. If I install the new version with the default settings it does work. Again, thx for your work! Plugin solves a lot.

This are the settings I use. I'm running the old version now but I used the same settings in the new version. As far as I know I have the plugin enabled on schedule.

Thanks a lot. That an awesome amount of work you did! I do use the cron setting of the plugin. When I first tried to run the new version, I did see the cron error msg. But the second time I tried it, it didn't show this msg. So I figured it was a file missing thats created on the first run or something. This is my output when I run the crond --help command root@Tower:~# crond --help dillon's cron daemon 4.5 crond [-s dir] [-c dir] [-t dir] [-m user@host] [-M mailer] [-S|-L [file]] [-l level] [-b|-f|-d] -s directory of system crontabs (defaults to /etc/cron.d) -c directory of per-user crontabs (defaults to /var/spool/cron/crontabs) -t directory of timestamps (defaults to /var/spool/cron/cronstamps) -m user@host where should cron output be directed? (defaults to local user) -M mailer (defaults to /usr/sbin/sendmail) -S log to syslog using identity 'crond' (default) -L file log to specified file instead of syslog -l loglevel log events <= this level (defaults to notice (level 5)) -b run in background (default) -f run in foreground -d run in debugging mode

Yeah, I tried both options. The plugin doesn't even get to the point where it looks what needs to be moved or not.

Normally it would tell me there is nothing to move because the threshold is not met. It doesnt even get that far. It crashes before that. Like I said, I've installed an older version and everything works perfectly again. So something broke in one of the changes since may. Well, that's kinda bold to draw a conclusion form that. I think the group that uses the plugin has updated it, and saw there is a problem because their chache disk ran full, aint that big. And the group becomes even more smaller if the problem is only there when you use a certain setting. Of course I appreciate your work on the plugin and if my tone is a bit to harsh, I'm sorry for that. I just don't know how can pinpoint it any further. The last zip I've posted is gathered from clicking the button in the plugin help section. If there is not any sign of the plugin in there, I don't know why not. And the plugin says it had made log files at the boot/logs location. But it didn't. I'm now using the 2025-04-24a version. And that works perfectly. The new version gives very little output. I've posted this a couple times. Nothing else is there. No errors, no logs, no notification. Despite all these settings being on. The old version gives me a notification every hour if it had moves something or not. How many files it moves etc etc. The before and after scripts work. Everything is just perfect and the plugin does exactly what I need. So I'm really thankful for that because it enables me to fill some needs. So it's no biggy to keep using the older version. Only thing bothering me is the update msg really.. ^^ I'll try again when there is a new version released. Maybe it'll be solved then. If there are any specifics you want me to try for you. Let me know. I can even screen record if you want.

Normally it would tell me there is nothing to move because the threshold is not met. It doesnt even get that far. It crashes before that. Like I said, I've installed an older version and everything works perfectly again. So something broke in one of the changes since may.

I've reinstalled the plugin and tried it without the before and awfter script. But it doesn't work. I've downloaded the 25-04-24 version and everything works fine again. Even with the before and after scripts. So I'll just ignore the update warning for now. This is a zip downloaded from the latest version without the before and after scripts ca.mover.tuning-debug-20250612-1352.zip

That might be true. But mover did nothing inbetween.. That being said. I see the before and after scripts have an issue. Due to a deluge update it seems. Maybe that causes the mover to fail.. When I install the plugin and dont change the settings it seems to work. I'll try to pinpoint what setting causes it to not work anymore.

I'm not sure what you're trying to say?

mover debug didnt create a zip file. But the link in the help section did. ca.mover.tuning-debug-20250611-2206.zip

How do I get this debug.zip? Do I have to reinstall the plugin again? Right now I'm searching for ways to install the version from 3 weeks back. That was working perfectly. But I haven't found a way to download an older version yet. So for now, I've uninstalled the plugin and everything works. Problem is my before and after scripts don't get executed now. So a working version of the plugin would be nice...

So my post from yesterday didnt get approved apparently. I made a post that mover aint working anymore since the last update of the plugin. It still doesnt. I've removed the plugin and now Mover works again. But I'd like to use the plugin again ofcourse. This is what the log says (There is no dianostics file at the location it says) Jun 10 23:06:34 Tower move: Mover Tuning Plugin version 2025.06.07 Jun 10 23:06:34 Tower move: Jun 10 23:06:34 Tower move: Usage: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover <or> mover start [-e <disk_name>] Jun 10 23:06:34 Tower move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover <or> mover stop|softstop|status|reset|debug Jun 10 23:06:34 Tower move: <disk_name> must match pattern 'disk[0-9]*' and /mnt/<disk_name> must be a mountpoint Jun 10 23:06:34 Tower move: Jun 10 23:06:34 Tower move: reset - reset config file to default values and delete override config folder Jun 10 23:06:34 Tower move: debug - creating plugin diagnostics file at /boot/logs/ca.mover.tuning-debug-<date-time>.zip