Manually running the mover on 6.12.9 through the "Move" button in the GUI invokes this command:
BACKUP emhttpd: shcmd (666): /usr/local/sbin/mover &> /dev/null &
However with both standard output and standard error output being piped to /dev/null no logging whatsoever is taking place. It is therefore impossible to diagnose a failing (or successful) mover operation. This is particularly annoying when you press the button "Move" and nothing happens, with no indication of an error having occured being shown in the GUI either. Only running the mover command manually through the terminal then eventually showed this output:
mover: started
file: /mnt/disk1/system/docker/docker.img
move_object: /mnt/disk1/system/docker/docker.img File exists
file: /mnt/disk1/system/libvirt/libvirt.img
move_object: /mnt/disk1/system/libvirt/libvirt.img File exists
mover: finished
... which is what I would have expected and liked to see in the syslog in the first place.
Also from a support point of view it'd be very hard to help users without having such information in the syslogs.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.