[FreeNAS 9 Plugin] - Syncthing

[Joshua Parker Ruehlig]

OK glad it's working.

 

[George51]

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

Just to let you know - I wouldn't have said I've been running it for too long... And I also had to do that. but on the plus side it worked and is auto upgrading now. Thank you.

 

[mskenderian]

OK glad it's working.

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.

 

[Joshua Parker Ruehlig]

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.

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.

 

[Silwanyx]

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.

 

[Joshua Parker Ruehlig]

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.

I enabled autoupdating in the plugin. so you should be able to update within syncthing itself. is in not working for you?

 

[hungarianhc]

I enabled autoupdating in the plugin. so you should be able to update within syncthing itself. is in not working for you?

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.

 

[Joshua Parker Ruehlig]

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.

hmm, maybe because of a process name change. I wonder if 'service syncthing onestatus' works or not.

 

[Silwanyx]

Hi Joshua

sorry, long time not be here. Ah, i see the autoupdate button, but, i don't klicked it, until today, i have not knowing, that you have let the autoupdate.

But, after i clicked, here is the error:
upgrading: open /usr/pbi/syncthing-amd64/bin/syncthing/syncthing218012204: permission denied

Here the steps i solved this problem:

I have read some older post, and this does the trick, and let the Syncthing to autoupdate, putting this on syncthing_1 jail shell (on FreeNAS GUI, go to jails, click on "syncthing_1" jail, and, on the bottom of list, click on black "shell" icon) and input this:

chown -R syncthing:syncthing /usr/pbi/syncthing-amd64/bin/syncthing

After this, i have enabled the "Automatic upgrades" on Syncthing GUI Settings, started the Syncthing on FreeNAS GUI Plugins (if service status is "Off"), and DONE.

Now, i have the new, autoupdated version of Syncthing. Great!

The only thing is, that the showed version on FreeNAS GUI plugins is the old 0.11.11, and this is not correct.

Josua, maybe you can change this to show somthing like "Autoupdate", or somthing like this for Syncthing? It would be great, if you can somehow correct this, to show the right version from Syncthing itself, or puting somthig like "Auto-Updated"

Hope, someone help this informations to.

Thank you, Joshua. Great work.

 

[Joshua Parker Ruehlig]

@Silwanyx
that's a good idea, maybe for programs that autoupdate I can put auto in the version somehow.

I'll look into this in the future

 

[Silwanyx]

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.

What i have now the error:
connectionsget_ea_dos_attribute: Cannot get attribute from EA on file Sync/Syncthing/Server/ZH1/Proxmox WebServer1/var/spool/postfix/usr/lib/zoneinfo/localtime: Error = Operation not supported

And this Proxmox WebServer1 i have deleted it about a 3 Weeks ago. It looks like a shadow information somwhere is stored, and re-readed, but, this is i think a bug, it should not be there any info about this anymore.

Any suggestion for this problem?

 

[Joshua Parker Ruehlig]

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?

can you ping your computer from the syncthing jail?

 

[Silwanyx]

i 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

 

[Silwanyx]

Here more what i have on my log info:

Sep 17 00:00:00 FreeNAS1-ZH1 newsyslog[43581]: logfile turned over due to size>100K
Sep 17 00:00:00 FreeNAS1-ZH1 syslog-ng[17906]: Configuration reload request received, reloading configuration;
Sep 17 00:12:27 FreeNAS1-ZH1 kernel: epair6a: link state changed to DOWN
Sep 17 00:12:27 FreeNAS1-ZH1 kernel: epair6a: link state changed to DOWN
Sep 17 00:12:27 FreeNAS1-ZH1 kernel: epair6b: link state changed to DOWN
Sep 17 00:12:27 FreeNAS1-ZH1 kernel: epair6b: link state changed to DOWN
Sep 17 00:12:31 FreeNAS1-ZH1 kernel: ifa_del_loopback_route: deletion failed
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (udp_inpcb) was not empty (40 items). Lost 4 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (udpcb) was not empty (504 items). Lost 3 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (tcptw) was not empty (200 items). Lost 4 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (tcp_inpcb) was not empty (40 items). Lost 4 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (tcpcb) was not empty (24 items). Lost 6 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 Freed UMA keg (ripcb) was not empty (10 items). Lost 1 pages of memory.
Sep 17 00:12:31 FreeNAS1-ZH1 hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Sep 17 00:12:31 FreeNAS1-ZH1 hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Sep 17 00:13:03 FreeNAS1-ZH1 notifier: Performing sanity check on nginx configuration:
Sep 17 00:13:03 FreeNAS1-ZH1 notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Sep 17 00:13:03 FreeNAS1-ZH1 notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Sep 17 00:13:04 FreeNAS1-ZH1 epair6a: Ethernet address: 02:34:69:00:0f:0a
Sep 17 00:13:04 FreeNAS1-ZH1 epair6b: Ethernet address: 02:34:69:00:11:0b
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: epair6a: link state changed to UP
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: epair6a: link state changed to UP
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: epair6b: link state changed to UP
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: epair6b: link state changed to UP
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: epair6a: promiscuous mode enabled
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
Sep 17 00:13:04 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
Sep 17 00:21:13 FreeNAS1-ZH1 smbd[96119]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsget_ea_dos_attribute: Cannot get attribute from EA on file Sync/Syncthing/Server/ZH1/Proxmox WebServer1/var/spool/postfix/usr/lib/zoneinfo/localtime: Error = Operation not supported

 

[Joshua Parker Ruehlig]

i 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

OK so not a networking problem. try 'top' or 'ps aux' in the syncthing jail. there may also be logs in /var/db/syncthing

 

[Silwanyx]

It is weird, the syncthing is there on shell of syncthing plugin:
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
syncthing 33265 95.9 0.5 184352 177920 ?? SJ 1:04AM 1:10.19 /usr/pbi/syncth
root 13045 0.0 0.0 12088 1920 ?? IsJ 1:01AM 0:00.00 dhclient: epair
_dhcp 13088 0.0 0.0 12088 1992 ?? IsJ 1:01AM 0:00.00 dhclient: epair
root 13484 0.0 0.0 12092 1872 ?? IsJ 1:01AM 0:00.00 /usr/sbin/syslo
syncthing 13535 0.0 0.0 12092 1628 ?? IsJ 1:01AM 0:00.00 daemon: /usr/pb
syncthing 13536 0.0 0.0 15368 8120 ?? SJ 1:01AM 0:00.02 /usr/pbi/syncth
root 13544 0.0 0.0 14188 1864 ?? SsJ 1:01AM 0:00.00 /usr/sbin/cron
root 13850 0.0 0.1 166856 48488 ?? IJ 1:01AM 0:01.91 /usr/pbi/syncth
root 33353 0.0 0.0 17572 3400 0 SsJ 1:06AM 0:00.01 /bin/csh
root 33355 0.0 0.0 16300 2136 0 R+J 1:06AM 0:00.00 ps aux


And here after restarting the server logs showed on footer of FreeNAS GUI:
Sep 17 01:01:14 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
Sep 17 01:01:14 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair6b
Sep 17 01:01:22 FreeNAS1-ZH1 epair7a: Ethernet address: 02:53:3f:00:10:0a
Sep 17 01:01:22 FreeNAS1-ZH1 epair7b: Ethernet address: 02:53:3f:00:11:0b
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: epair7a: link state changed to UP
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: epair7a: link state changed to UP
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: epair7b: link state changed to UP
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: epair7b: link state changed to UP
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: epair7a: promiscuous mode enabled
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair7b
Sep 17 01:01:22 FreeNAS1-ZH1 kernel: ng_ether_ifnet_arrival_event: can't re-name node epair7b
Sep 17 01:01:36 FreeNAS1-ZH1 zfsd: DevfsEvent::ReadLabel: /dev/ada0p1: Unable to extract pool GUID from vdev label data.
Sep 17 01:01:37 FreeNAS1-ZH1 syslog-ng[17921]: syslog-ng starting up; version='3.5.6'
Sep 17 01:01:37 FreeNAS1-ZH1 kernel: pid 2048 (syslog-ng), uid 0: exited on signal 6 (core dumped)

The Syncthing of FreeNAS Server is showed on my other machines as offline to, but, on FreeNAS server itself, seems to work.
And i have no Syncthing log folder or files on var/logs...

 

[Joshua Parker Ruehlig]

well syncthing is running so you might want to ask for help on their support resources.

please post any logs from the directory I mentioned earlier, those should be more helpful then the system logs you keep posting.
also please show the following from the jail
sockstat
service syncthing onerestart

 

[Silwanyx]

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.

With top from jail:


PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND
64405 syncthing 8 79 0 118M 111M CPU1 1 0:23 96.68% syncthing
13850 root 6 20 0 163M 48872K usem 0 0:02 0.00% python2.7
64268 syncthing 6 20 0 15368K 10460K uwait 2 0:00 0.00% syncthing
64394 root 1 20 0 18672K 2412K CPU2 2 0:00 0.00% top
64166 root 1 20 0 17572K 3400K pause 0 0:00 0.00% csh
13484 root 1 20 0 12092K 1872K select 2 0:00 0.00% syslogd
13544 root 1 20 0 14188K 1864K nanslp 3 0:00 0.00% cron
13088 _dhcp 1 20 0 12088K 1992K select 0 0:00 0.00% dhclient
13045 root 1 52 0 12088K 1920K select 0 0:00 0.00% dhclient
64267 syncthing 1 52 0 12092K 1628K sigwai 0 0:00 0.00% daemon


The CPU seems to be used from Syncthing.

The Syncthing has worked without problems until i have updated FreeNAS about 2 hours ago. I don't think this is a problem with Syncthing itself. Somthing is wrong with last system update of FreeNAS.

 

[Joshua Parker Ruehlig]

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.

from that sockstat output it doesn't show syncthing as listening for a network connection.

what does the following output?
service syncthing onestatus

also please look for logs in /var/db/syncthing in the jail.

 

[Silwanyx]

The 192.168.1.22 is my syncthing adress from router, and jail DHCP adress.

service syncthing onestatus
syncthing is running as pid 64268.

Ah.. from the jail log, sorry, i have looked on the root folder... my fault, there i have for example, on the newest panic log:
.....
goroutine 65 [select]:
github.com/syncthing/syncthing/lib/ignore.(*Matcher).clean(0xc208fa07d0, 0x68c61714000)
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:161 +0x1c9
created by github.com/syncthing/syncthing/lib/ignore.New
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:53 +0x170

goroutine 67 [select]:
github.com/syncthing/syncthing/lib/ignore.(*Matcher).clean(0xc208659ae0, 0x68c61714000)
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:161 +0x1c9
created by github.com/syncthing/syncthing/lib/ignore.New
/go/src/github.com/syncthing/syncthing/lib/ignore/ignore.go:53 +0x170

Bounch of such infos

And found now a panic error on this file:
Panic at 2015-09-17T01:27:48+02:00
panic: leveldb/table: corruption on data-block (pos=293186): checksum mismatch, want=0x41efb446 got=0x4b203464 [file=3005312.ldb]