Joshua Parker Ruehlig
Hall of Famer
- Joined
- Dec 5, 2011
- Messages
- 5,949
OK glad it's working.
have you been updating the same instance for a while? I must not have tested updating from earlier versions.
maybe this would fix it for you
Code:chown -R syncthing:syncthing /usr/pbi/syncthing-amd64/bin/syncthing
i have noticed that when i browse to freenas GUI plugins->installed, it shows my plugin is Off. if i go to the jails, it shows its running, i have checked it actually running but after the update, my plugin status page shows its not running.OK glad it's working.
that issue sounds unrelated. if "service syncthing onestatus" says it's started then it is. the plugins > installed tab relies on the plugin's middleware layer working. restarting the jail might fix this.i havent noticed that when i browse to freenas GUI plugins->installed, it shows my plugin is Off. if i go to the jails, it shows its running, i have checked it actually running but after the update, my plugin status page shows its not running.
I enabled autoupdating in the plugin. so you should be able to update within syncthing itself. is in not working for you?Hi Joshua
Just wondering, if the Syncthing plugin would be updated soon to? There are 10 versions, or 10 other updates from the last 0.11.11, now, the newest one is 0.11.21, and many bugs are repaired and add some new stuff.
It would be nice, if this plugin would be update every week, like Syncthing itself, every sunday.
Thanks in advice.
The auto-update is definitely working for me on two separate FreeNAS systems. The only issue I'm seeing is that the plugin status shows as off, even though Syncthing is running just fine.I enabled autoupdating in the plugin. so you should be able to update within syncthing itself. is in not working for you?
hmm, maybe because of a process name change. I wonder if 'service syncthing onestatus' works or not.The auto-update is definitely working for me on two separate FreeNAS systems. The only issue I'm seeing is that the plugin status shows as off, even though Syncthing is running just fine.
can you ping your computer from the syncthing jail?I have a new problem:
I have updated the FreeNAS 9.3 today, the update from 16.09.2015, and now, i'm unable to access the Syncthing GUI. The plugin seems to be started, it showed status ON, jail it looks ok, but, no access to GUI, GUI is not there.
Have tryed couple of restartings of server, and of Syncthing itself, but nothing, it doesn't help.
Any suggestion for this problem?
OK so not a networking problem. try 'top' or 'ps aux' in the syncthing jail. there may also be logs in /var/db/syncthingi have update the earlyer post with the error i have.
Yes, i can ping it, here the results:
64 bytes from 192.168.1.57: icmp_seq=9 ttl=64 time=0.264 ms
64 bytes from 192.168.1.57: icmp_seq=10 ttl=64 time=0.286 ms
64 bytes from 192.168.1.57: icmp_seq=11 ttl=64 time=0.279 ms
64 bytes from 192.168.1.57: icmp_seq=12 ttl=64 time=0.283 ms
64 bytes from 192.168.1.57: icmp_seq=13 ttl=64 time=0.254 ms
^C
--- 192.168.1.57 ping statistics ---
14 packets transmitted, 14 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.137/0.254/0.286/0.036 ms
.57 is my PC
And, what i have see, if i go to freenas shell, and check the "top" command, the syncthing is not there
from that sockstat output it doesn't show syncthing as listening for a network connection.sockstat:
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python2.7 13850 3 tcp4 192.168.1.22:12353 *:*
root cron 13544 4 dgram -> /var/run/logpriv
root syslogd 13484 4 dgram /var/run/log
root syslogd 13484 5 dgram /var/run/logpriv
root syslogd 13484 6 udp6 *:514 *:*
root syslogd 13484 7 udp4 *:514 *:*
service syncthing onerestart i have do, but, no Syncthing GUI: ERR_CONNECTION_REFUSED on Chrome, and on Firefox the same.
The mentioned Syncthing dir or log file doesn't exist on my server, on var/db, nor var/logs, nowhere.