David McKeen
Dabbler
- Joined
- Sep 5, 2016
- Messages
- 10
This is the second time this has happened to me. The first time it happened to just one plugin. I tried to update the sickrage plugin through the web interface and it bombed out. I didn't realize that I couldn't update the them through normal means. After that i tried to remove and readd the plugin and I couldn't get it to start.
I did a fresh reinstall and the same things happened again, after a reboot. Now none of the plugins will start and I am seeing a similar issue that I saw with the sickrage plugin. I hadn't even configured btsync yet so i'm a little confused. This is what is showing on the console.
I have the system dataset being saved to the freenas-boot partition. Don't know if that has anything to do with it.
Running:
Build FreeNAS-9.10.1 (d989edd)
Platform Intel(R) Celeron(R) CPU G1610T @ 2.30GHz
Memory 16192MB
I did a fresh reinstall and the same things happened again, after a reboot. Now none of the plugins will start and I am seeing a similar issue that I saw with the sickrage plugin. I hadn't even configured btsync yet so i'm a little confused. This is what is showing on the console.
Code:
Sep 5 17:48:01 freenas epair3a: Ethernet address: 02:ff:20:00:08:0a Sep 5 17:48:01 freenas epair3b: Ethernet address: 02:ff:70:00:09:0b Sep 5 17:48:01 freenas kernel: epair3a: link state changed to UP Sep 5 17:48:01 freenas kernel: epair3a: link state changed to UP Sep 5 17:48:01 freenas kernel: epair3b: link state changed to UP Sep 5 17:48:01 freenas kernel: epair3b: link state changed to UP Sep 5 17:48:01 freenas devd: Executing '/etc/pccard_ether epair3b start' Sep 5 17:48:01 freenas kernel: epair3a: promiscuous mode enabled Sep 5 17:48:01 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair3a' Sep 5 17:48:01 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair3b' Sep 5 17:48:02 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b Sep 5 17:48:02 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b Sep 5 17:53:19 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.1.95/plugins/btsync/1/_s/treemenu: No JSON object could be decoded Sep 5 18:15:32 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.1.95/plugins/btsync/1/_s/status: No JSON object could be decoded
I have the system dataset being saved to the freenas-boot partition. Don't know if that has anything to do with it.
Running:
Build FreeNAS-9.10.1 (d989edd)
Platform Intel(R) Celeron(R) CPU G1610T @ 2.30GHz
Memory 16192MB