I don't think so, I also don't see the option to update like I have on my windows machine. On windows I have a option to allow, or disallow the auto update, this option is no on my freenas/freebsd installation.
I don't think so, I also don't see the option to update like I have on my windows machine. On windows I have a option to allow, or disallow the auto update, this option is no on my freenas/freebsd installation.
I just tried installing syncthing and got this message.
So, the plugin obviously can update itself. For some reason your install isn't doing it. Maybeit doesn't see the update or a restart of the plugin would help?
Got the same issue. I was not able to upgrade the minor version of syncthing. After couple of investigations, I remembered that I had changed the network addressing of my jails. Then I check if the name resolution was working.
For weird reason, it was not on the jail but was working on the FreeNAS.
I changed the resolv.conf of the jail with the right dns server and restarted the jail.
Everything came back to normal and syncthing was able to see updates.
My case was potentially unique but worth checking if the dns resolution is working within the jail before going further.
Got the same issue. I was not able to upgrade the minor version of syncthing. After couple of investigations, I remembered that I had changed the network addressing of my jails. Then I check if the name resolution was working.
For weird reason, it was not on the jail but was working on the FreeNAS.
I changed the resolv.conf of the jail with the right dns server and restarted the jail.
Everything came back to normal and syncthing was able to see updates.
My case was potentially unique but worth checking if the dns resolution is working within the jail before going further.
Trying to get SickRage to start myself and I kept on seeing in the "/var/log/messages" the following:
Code:
Jun 30 19:19:22 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://172.18.172.18/plugins/sickrage/11/_s/status: HTTP Error 503: OK
Jun 30 19:30:12 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://172.18.172.18/plugins/sickrage/11/_s/status: HTTP Error 503: OK
One of the things that I noticed in the "/var/log/debug.log" that for each jail that was created from the plugin it was using the same duplicate MAC Address (mac: 02:ff:70:00:10:0b) as show below:
Code:
#####
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = host: sickrage_1
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = iface:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = ipv4: 172.18.172.14/24
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = bridge-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-bridge-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = defaultrouter-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = bridge-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-bridge-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = defaultrouter-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = autostart: Enabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = vnet: Enabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = nat: Disabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = mac: 02:ff:70:00:10:0b
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = status: Running
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = type: pluginjail
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = flags: allow.raw_sockets=true
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out =
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out =
Code:
#####
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = id: 15
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = host: sonarr_1
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = iface:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = ipv4: 172.18.172.6/24
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = bridge-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-bridge-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = defaultrouter-ipv4:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = bridge-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = alias-bridge-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = defaultrouter-ipv6:
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = autostart: Enabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = vnet: Enabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = nat: Disabled
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = mac: 02:ff:70:00:10:0b
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = status: Running
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = type: pluginjail
Jun 30 19:26:32 freenas manage.py: [common.cmd:209] cmd_pipe.__init__: out = flags: allow.raw_sockets=true
My workaround was to go to the Jail and select Advanced and change the MAC Address.
JFYI, I installed syncthing (0.14.2 on FreeNAS FreeNAS-9.10.2-U5) via the plugin 'wizard' and somehow the tool managed to give the syncthing-jail the same MAC as another jail that I have running for a plexmedia server jail.
I didn't have to or did change any MAC addresses on my own.
After that I used the 'service syncthing onestart' in the jail command line to get it running, as the toggle switch in the GUI didn't 'stick'.
JFYI, I installed syncthing (0.14.2 on FreeNAS FreeNAS-9.10.2-U5) via the plugin 'wizard' and somehow the tool managed to give the syncthing-jail the same MAC as another jail that I have running for a plexmedia server jail.
I didn't have to or did change any MAC addresses on my own.
After that I used the 'service syncthing onestart' in the jail command line to get it running, as the toggle switch in the GUI didn't 'stick'.
yup, it was already enabled. clicking the button on the Plugins > Installed tab enables it, so maybe that actually worked to enable it but not start it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.