Plugins stopped working after restart

Status
Not open for further replies.

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.

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
 

David McKeen

Dabbler
Joined
Sep 5, 2016
Messages
10
No, still an issue.
 
Joined
May 23, 2016
Messages
19
I'm getting the same error since I updated to to 9,3, with only the plex plugin. I tried to go back but still same issue. I loose internet on my plex jail shortly after I go to the web GUI for plex. I can still ping computers on my network but no internet connection. After I loose internet connection if I change the IP address on the jail and restart the jail. The internet connection comes back till I accesses the web GUI for plex. I have two other jails (Sickrage & Transmission) and they run flawlessly. I read in some forums (I'm sorry I don't remember where right now) people getting the same error, using plex plugin as well and they changed their NIC to a Intel 1000 Series and that fixed the issue. I put an Intel Pro 1000 GT Desktop in my box (I'm going to swap it out for the PCI-E version but I doubt that fixes my issue) but I'm still having the same problem and I can't find an answer anywhere, I've research for many hours now, since I have had this issue for nearly two months. Any help would be greatly appreciated.

Here's the whole process from the messages log:

Code:
Sep 25 19:46:09 freenas warden: Building new Jail... Please wait...
Sep 25 19:46:09 freenas warden: zfs clone FreeNas/jails/.warden-template-pluginjail@clean FreeNas/jails/plexmediaserver_1
Sep 25 19:46:09 freenas warden: Success!
Sep 25 19:46:09 freenas warden: Jail created at /mnt/FreeNas/jails/plexmediaserver_1
Sep 25 19:46:10 freenas devd: Executing '/etc/pccard_ether epair3a start'
Sep 25 19:46:10 freenas devd: Executing '/etc/pccard_ether epair3b start'
Sep 25 19:46:10 freenas devd: Executing '/etc/rc.d/dhclient quietstart epair3a'
Sep 25 19:46:10 freenas epair3a: Ethernet address: 02:ff:20:00:08:0a
Sep 25 19:46:10 freenas epair3b: Ethernet address: 02:00:70:00:09:0b
Sep 25 19:46:10 freenas kernel: epair3a: link state changed to UP
Sep 25 19:46:10 freenas kernel: epair3a: link state changed to UP
Sep 25 19:46:10 freenas kernel: epair3b: link state changed to UP
Sep 25 19:46:10 freenas kernel: epair3b: link state changed to UP
Sep 25 19:46:10 freenas kernel: epair3a: promiscuous mode enabled
Sep 25 19:46:10 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Sep 25 19:46:10 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b
Sep 25 19:46:26 freenas notifier: Performing sanity check on nginx configuration:
Sep 25 19:46:26 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Sep 25 19:46:26 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Sep 25 19:46:27 freenas manage.py: [freeadmin.navtree:631] An error occurred while unserializing from http://192.168.1.9/plugins/plexmediaserver/8/_s/treemenu: No JSON object could be decoded




or I get this (its exactly the same until after "freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair3b" :

Code:
Sep 26 18:07:09 freenas kernel: ifa_del_loopback_route: deletion failed: 48
Sep 26 18:07:09 freenas Freed UMA keg (udp_inpcb) was not empty (150 items).  Lost 15 pages of memory.
Sep 26 18:07:09 freenas Freed UMA keg (udpcb) was not empty (1169 items).  Lost 7 pages of memory.
Sep 26 18:07:09 freenas Freed UMA keg (tcptw) was not empty (540 items).  Lost 12 pages of memory.
Sep 26 18:07:09 freenas Freed UMA keg (tcp_inpcb) was not empty (180 items).  Lost 18 pages of memory.
Sep 26 18:07:09 freenas Freed UMA keg (tcpcb) was not empty (63 items).  Lost 21 pages of memory.
Sep 26 18:07:09 freenas Freed UMA keg (ripcb) was not empty (90 items).  Lost 9 pages of memory.
Sep 26 18:07:09 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Sep 26 18:07:09 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
 
Status
Not open for further replies.
Top