Btsync Running, Not Showing in Installed Plugins List

[ericv]

I had btsync up and running for a few weeks. After a recent reboot the plugin does not list under the installed plugins and it doesn't show up in the left nav either. The plugin is up and running. Can't figure out why it isn't showing. Any suggestions?

If the solution to the problem is to manually delete the plugin, that is fine if someone can help out with some instructions. Searched and couldn't find any. I've read a bunch of threads about how exactly to do it the the results / methods all seem mixed.

I'd like to just fix the problem, rather than manually delete it if possible.

 

[Joshua Parker Ruehlig]

can you ping your computer from the btsync jail?

 

[ericv]

can you ping your computer from the btsync jail?

Yes.

root@btsync_1:/ # ping 192.168.1.84
PING 192.168.1.84 (192.168.1.84): 56 data bytes
64 bytes from 192.168.1.84: icmp_seq=0 ttl=64 time=257.467 ms
64 bytes from 192.168.1.84: icmp_seq=1 ttl=64 time=2.504 ms
64 bytes from 192.168.1.84: icmp_seq=2 ttl=64 time=2.360 ms
64 bytes from 192.168.1.84: icmp_seq=3 ttl=64 time=23.691 ms
64 bytes from 192.168.1.84: icmp_seq=4 ttl=64 time=4.480 ms
64 bytes from 192.168.1.84: icmp_seq=5 ttl=64 time=6.819 ms
^C
--- 192.168.1.84 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.360/49.554/257.467/93.270 ms

 

[Joshua Parker Ruehlig]

Yes.

root@btsync_1:/ # ping 192.168.1.84
PING 192.168.1.84 (192.168.1.84): 56 data bytes
64 bytes from 192.168.1.84: icmp_seq=0 ttl=64 time=257.467 ms
64 bytes from 192.168.1.84: icmp_seq=1 ttl=64 time=2.504 ms
64 bytes from 192.168.1.84: icmp_seq=2 ttl=64 time=2.360 ms
64 bytes from 192.168.1.84: icmp_seq=3 ttl=64 time=23.691 ms
64 bytes from 192.168.1.84: icmp_seq=4 ttl=64 time=4.480 ms
64 bytes from 192.168.1.84: icmp_seq=5 ttl=64 time=6.819 ms
^C
--- 192.168.1.84 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.360/49.554/257.467/93.270 ms

hmm, ok then the plugin middleware should be accessible. You might want to try restarting the btsync jail.
Also showing the status of 'ps aux' may be interesting.

 

[ericv]

hmm, ok then the plugin middleware should be accessible. You might want to try restarting the btsync jail.
Also showing the status of 'ps aux' may be interesting.

I should have mentioned I've tried restarting the server since the reboot that initiated the plugin not showing up. Here are the result from the 'ps aux' from within the jail.

root@btsync_1:/ # ps aux
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 4912 0.0 0.0 12080 1868 ?? IsJ Thu04PM 0:00.08 /usr/sbin/syslogd -s
btsync 4963 0.0 0.9 411316 297408 ?? SsJ Thu04PM 42:23.93 /usr/pbi/btsync-amd64/bin/btsync --config /usr/pbi/btsync-amd64/etc/btsync.conf
root 4970 0.0 0.0 14184 1860 ?? SsJ Thu04PM 0:00.09 /usr/sbin/cron -s
root 30760 0.0 0.0 17568 3100 0 SJ 8:47AM 0:00.00 /bin/tcsh
root 30762 0.0 0.0 16296 1808 0 R+J 8:47AM 0:00.00 ps aux

 

[Joshua Parker Ruehlig]

I should have mentioned I've tried restarting the server since the reboot that initiated the plugin not showing up. Here are the result from the 'ps aux' from within the jail.

root@btsync_1:/ # ps aux
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 4912 0.0 0.0 12080 1868 ?? IsJ Thu04PM 0:00.08 /usr/sbin/syslogd -s
btsync 4963 0.0 0.9 411316 297408 ?? SsJ Thu04PM 42:23.93 /usr/pbi/btsync-amd64/bin/btsync --config /usr/pbi/btsync-amd64/etc/btsync.conf
root 4970 0.0 0.0 14184 1860 ?? SsJ Thu04PM 0:00.09 /usr/sbin/cron -s
root 30760 0.0 0.0 17568 3100 0 SJ 8:47AM 0:00.00 /bin/tcsh
root 30762 0.0 0.0 16296 1808 0 R+J 8:47AM 0:00.00 ps aux

not sure why, but your plugin middleware process isn't running. It should look something like "/usr/pbi/btsync-amd64/bin/python2.7 /usr/pbi/btsync-amd64/control.py start 192.168.1.X 1234X"
Like I said, you could try restarting the jail, not the server.

 

[ericv]

I figured restarting the server would restart the jail.

To restart the jail I just do a....

jail -rc 1

correct, from outside the jail?

 

[ericv]

not sure why, but your plugin middleware process isn't running. It should look something like "/usr/pbi/btsync-amd64/bin/python2.7 /usr/pbi/btsync-amd64/control.py start 192.168.1.X 1234X"
Like I said, you could try restarting the jail, not the server.

Figured restarting the server would restart the jail.

I restart the jail like this correct?

jail -rc btsync_1

 

[Joshua Parker Ruehlig]

Figured restarting the server would restart the jail.

I restart the jail like this correct?

jail -rc btsync_1

you were correct, but I wanted to see if it changed something restarting the jail when the system is running. not sure if that command works, I would have used the restart button on the jails tab

 

[ericv]

you were correct, but I wanted to see if it changed something restarting the jail when the system is running. not sure if that command works, I would have used the restart button on the jails tab

Oh man, I forgot about the jails tab...

Ok, restarted. Still not in the plugins list.

Output from /var/log/messages
Oct 3 13:05:07 beast kernel: epair0a: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0a: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0b: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0b: link state changed to DOWN
Oct 3 13:05:12 beast epair0a: Ethernet address: 02:6c:71:00:08:0a
Oct 3 13:05:12 beast epair0b: Ethernet address: 02:6c:71:00:0b:0b
Oct 3 13:05:12 beast kernel: epair0a: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0a: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0b: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0b: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0a: promiscuous mode enabled
Oct 3 13:05:12 beast kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Oct 3 13:05:12 beast kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b

Output from 'ps aux' after restart
root@btsync_1:/ # ps aux
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 41567 0.0 0.0 12080 1876 ?? SsJ 1:05PM 0:00.00 /usr/sbin/syslogd -s
btsync 41618 0.0 0.8 341172 265328 ?? SsJ 1:05PM 0:23.98 /usr/pbi/btsync-amd64/bin/btsync --config /usr/pbi/btsync-amd64/etc/btsync.conf
root 41625 0.0 0.0 14184 1852 ?? IsJ 1:05PM 0:00.00 /usr/sbin/cron -s
root 47671 0.0 0.0 17568 3100 0 SJ 1:07PM 0:00.00 /bin/tcsh
root 47674 0.0 0.0 16296 1808 0 R+J 1:07PM 0:00.00 ps aux

 

[Joshua Parker Ruehlig]

Oh man, I forgot about the jails tab...

Ok, restarted. Still not in the plugins list.

Output from /var/log/messages
Oct 3 13:05:07 beast kernel: epair0a: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0a: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0b: link state changed to DOWN
Oct 3 13:05:07 beast kernel: epair0b: link state changed to DOWN
Oct 3 13:05:12 beast epair0a: Ethernet address: 02:6c:71:00:08:0a
Oct 3 13:05:12 beast epair0b: Ethernet address: 02:6c:71:00:0b:0b
Oct 3 13:05:12 beast kernel: epair0a: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0a: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0b: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0b: link state changed to UP
Oct 3 13:05:12 beast kernel: epair0a: promiscuous mode enabled
Oct 3 13:05:12 beast kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Oct 3 13:05:12 beast kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b

Output from 'ps aux' after restart
root@btsync_1:/ # ps aux
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 41567 0.0 0.0 12080 1876 ?? SsJ 1:05PM 0:00.00 /usr/sbin/syslogd -s
btsync 41618 0.0 0.8 341172 265328 ?? SsJ 1:05PM 0:23.98 /usr/pbi/btsync-amd64/bin/btsync --config /usr/pbi/btsync-amd64/etc/btsync.conf
root 41625 0.0 0.0 14184 1852 ?? IsJ 1:05PM 0:00.00 /usr/sbin/cron -s
root 47671 0.0 0.0 17568 3100 0 SJ 1:07PM 0:00.00 /bin/tcsh
root 47674 0.0 0.0 16296 1808 0 R+J 1:07PM 0:00.00 ps aux

Not sure why the plugins service isn't running. Maybe FreeNAS doesn't know what IP to start it on? Is your jail set to use a static IP or DHCP?

A possible "fix" is to install a second instance of btsync, setup your mountpoint(s) and copy over you /var/db/btsync folder over.

 

[ericv]

It is using a static IP. I tried installing another instance of btsync. I couldn't get it to start.

 

[Joshua Parker Ruehlig]

It is using a static IP. I tried installing another instance of btsync. I couldn't get it to start.

Ok, it has to do with your jail networking or plugin middleware layer not working. My earlier workaround wouldn't work for you. Sorry, not sure what else you should try.

 

[ericv]

Ok, it has to do with your jail networking or plugin middleware layer not working. My earlier workaround wouldn't work for you. Sorry, not sure what else you should try.

If I just outright delete the jail, will FreeNAS still think there is a plugin and try to start it?

 

[diedrichg]

If I just outright delete the jail, will FreeNAS still think there is a plugin and try to start it?

No, it will not try to start something that isn't there.

 

[Joshua Parker Ruehlig]

If I just outright delete the jail, will FreeNAS still think there is a plugin and try to start it?

nope, freenas isn't the one starting btsync in this case. the reason it is starting is because you enabled it before which added the line "btsync_enable=YES" to your jail's /etc/rc.conf, which is read by your jail's init system.