Jump to content
  • 6.12.9 - (Manual) Mover not Logging to Syslog

    • Closed

    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.

    User Feedback

    Recommended Comments

    There's a setting to enable mover logging, enable it when needed for troubleshooting then disable afterwards, point is not to have thousands of lines of log spam when nothing's wrong.



    • Thanks 1
    Link to comment

    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.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.

  • Create New...