I get these in my log file every 2 hours when mover runs.  Why is it logging when I have logging disabled?  Is this an error?

Nov 15 06:00:16 Tower crond[1441]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Nov 15 08:00:16 Tower crond[1441]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

 

That setting is not meant to control that message being logged.   What it controls is whether details of each file being moved (or attempted) are logged.

Those messages were never logged until I recently upgraded from 6.4.x.  Is this just a new "feature" of the newer version of unraid?

49 minutes ago, romanodog said:

exit status 1

This means there was an error, or possibly a warning like a file that wasn't copied because it already exists, enable mover logging for more details.

When I enable mover logging this is what I get:

 

Nov 15 13:55:54 Tower root: mover: started
Nov 15 13:55:54 Tower root: mover: finished

Is there any other way to see what the error or warning would be?

Looks like when the mover runs on a schedule it always outputs exit status 1, this should mean there's an error, so probably a small bug,

but the mover being logged is normal even if you have mover logging disabled, just the activity isn't logged.

I asked a similar question here:

 

 

but no one replied. I'm still getting the message on all servers, whether running Unraid 6.6.6 or 6.7.0-rc4. If I run the mover manually I don't get the error.