RedditPP Mascot

RedditPP

r/unRAID • … • u/Laucien

Issue with Mover not being called and not working form the UI?

So, this is a very weird issue that I just noticed on my server when it alerted me the cache disk was 90%+ full.

Basically Mover doesn't seem to be running despite the schedule being once a day _and_ calling it form the UI does nothing. The page reloads but then it's like the button did nothing.

I enabled logging for mover and when I hit the button to trigger it I get this in the syslog:

``` Feb 8 18:46:12 vault kernel: Feb 8 18:46:57 vault emhttpd: shcmd (1920): /usr/local/sbin/mover start |& logger -t move & Feb 8 18:46:57 vault kernel: mdcmd (42): set md_write_method 1 Feb 8 18:46:57 vault kernel: Feb 8 18:46:57 vault move: Usage: /usr/local/sbin/mover.old start [-e] <disk_name> Feb 8 18:46:57 vault move: /usr/local/sbin/mover.old stop|status Feb 8 18:46:57 vault move: <disk_name> must match pattern 'disk[0-9]*' ```

Looks like it's trying to call it with the wrong commands and/or parameters and failing silently?.

Another thing I noticed is that during boot there's a line complaning about `/usr/local/bin/mover` not existing but the binary is actually under `/usr/local/sbin/mover`.

If I manually call it from the terminal with `/usr/local/sbin/mover start` it works perfectly.

Has anyone seen anythin similar? Currently running 7.0.0 with the patch that specifically fixes mover not touching folders/files with spaces in the names.

//Edit: With logging disabled it does this:

``` Feb 8 19:02:33 vault emhttpd: shcmd (5110): /usr/local/sbin/mover start &> /dev/null & Feb 8 19:02:34 vault kernel: mdcmd (44): set md_write_method 1 Feb 8 19:02:34 vault kernel: Feb 8 19:02:34 vault kernel: mdcmd (45): set md_write_method auto Feb 8 19:02:34 vault kernel: ```

But that doesn't tell you anything and is actually hiding any possible errors because it's redirecting everything to the blackhole that is `/dev/null`.

//Edit 2: Nevermind, it was something with the mover tuning plugin. I installed it ages ago but never used it so forgot it was there. I uninstalled and it seems like it's working properly again.

— 0