• [6.6.7] Shares segfault


    nanouke
    • Minor

    Hello everyone,

    I have already reported a similar problem in version 6.6.4. My Shares were not accessible after a certain time, often within 24 hours. The problem was fixed in version 6.6.5 and then reappeared in version 6.6.6. I was waiting for version 6.6.7 to check if the problem still persisted and it still. Here in the logs where I think there is a problem:

    Feb 27 03:40:01 Tower kernel: shfs[2255]: segfault at 0 ip 0000000000402722 sp 000015511c8088f0 error 4 in shfs[400000+f000]
    Feb 27 03:40:01 Tower kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8 
    Feb 27 04:03:41 Tower crond[1736]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null


    I do not know if this is really a problem or if there is corruption in my system.
    I would like to solve this problem because to get around it, I have to restart the server every day.

     

    Thank you for your help




    User Feedback

    Recommended Comments

    I am also having the exact same problem. It occurs at the exact same time too. My shares aren't available anymore when it happens. When I click on the "shares" tab, it has none of them listed. I have to reboot to fix the issue, but it happens every day. 

     

    Two things have happened recently. I upgraded to 6.6.7 recently and my cache drive died. The time that this occurs lines up with the scheduled mover doesn't it?

     

     

    Link to comment
    9 hours ago, limetech said:

    I don't see a crash in there.

    I had rebooted so it was already fixed.

     

    I woke up this morning to it again.

     

    Mar 13 03:40:01 SHIRT kernel: shfs[29664]: segfault at 0 ip 0000000000402722 sp 00001540036768f0 error 4 in shfs[400000+f000]
    Mar 13 03:40:01 SHIRT kernel: Code: 89 7d f8 48 89 75 f0 eb 1d 48 8b 55 f0 48 8d 42 01 48 89 45 f0 48 8b 45 f8 48 8d 48 01 48 89 4d f8 0f b6 12 88 10 48 8b 45 f0 <0f> b6 00 84 c0 74 0b 48 8b 45 f0 0f b6 00 3c 2f 75 cd 48 8b 45 f8 
    Mar 13 03:40:01 SHIRT crond[1738]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

     

    shirt-diagnostics-20190313-0718.zip

    Link to comment

    My issue was resolved. I got around to replacing my cache drive and everything started functioning normal. 

     

    So when my cache drive died, the mover would start nightly and would cause the segfault. Which made all the shares disappear and would only be resolved by rebooting. 

    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.

    Guest
    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.