Bittorrent Sync Kills all my filesystems

  • Hi,


    I recently installed the Bittorrent sync plugin. It works well once it starts.


    The only MAJOR issue is that every time that I make any changes to the BTSync configuration via the WebUI all my filesystems get offline.


    I get email alerts like this:


    Does not exist Service fs_media_XXXXXXXXXXXXXXXXXXX
    Date: Thu, 29 Oct 2015 16:02:44
    Action: restart
    Host: XXXXXXXX.WORKGROUP
    Description: filesystem doesn't exist
    Your faithful employee,Monit


    and when I check the filesystems in the WebUI everything is n/a except Device,Label and maybe File-System columns.


    Any Idea where to diagnose the cause ?


    Thank you,
    G

    • Offizieller Beitrag

    Any Idea where to diagnose the cause ?


    Look at the syslog and dmesg the moment you apply changes. Something should come there


    changes to the BTSync configuration via the WebUI


    Is this the webui of omv or the btsync webui?


    Point a side btsync plugin uses an old version of btsync binary which is no longer maintained by Bittorrent inc. The plugin developer doesn't want to move to v2.0. You should consider other alternatives like syncthing or use btsync 2.0 without the plugin, maybe a docker container can do the trick

  • It sounds very tempting. The problem is in OMV UI.


    What about using the latest stable from getsync.com?


    I could have it autostart each time OMV starts. How would I do that?


    What other implications might there be?



    Here is part of syslog at the very moment I click on a shared folder's details (took out alert email sanding messages) :


    Oct 31 07:43:25 E3-W7-SERV btsync.openmediavault: btsync instance openmediavault started successfully
    Oct 31 07:45:01 E3-W7-SERV /USR/SBIN/CRON[29416]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
    Oct 31 07:45:01 E3-W7-SERV rrdcached[2820]: Received FLUSHALL
    Oct 31 07:45:33 E3-W7-SERV monit[4335]: 'fs_media_FCF68668F686234E' filesystem doesn't exist
    Oct 31 07:45:33 E3-W7-SERV postfix/smtpd[29516]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled
    Oct 31 07:45:33 E3-W7-SERV postfix/smtpd[29516]: connect from localhost[127.0.0.1]
    ...some postfix stuff
    Oct 31 07:45:33 E3-W7-SERV monit[4335]: 'fs_media_FCF68668F686234E' trying to restart
    ...more postfix stuff
    Oct 31 07:45:33 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected
    Oct 31 07:45:39 E3-W7-SERV postfix/smtp[29520]: 4654B2008B4: replace: header Subject: monit alert -- Does not exist fs_media_FCF68668F68: Subject
    : monit alert -- Does not exist fs_media_FCF68668F686234E [E3-W7-SERV.WORKGROUP]
    ...more postfix stuff
    Oct 31 07:45:43 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected
    Oct 31 07:45:53 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected
    Oct 31 07:46:03 E3-W7-SERV monit[4335]: 'fs_media_FCF68668F686234E' filesystem doesn't exist
    Oct 31 07:46:03 E3-W7-SERV monit[4335]: 'fs_media_FCF68668F686234E' trying to restart
    Oct 31 07:46:03 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected
    Oct 31 07:46:13 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected
    Oct 31 07:46:23 E3-W7-SERV collectd[2926]: statvfs(/media/FCF68668F686234E) failed: Transport endpoint is not connected

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!