Plugins Keep crashing and not being able to turn back on

Status
Not open for further replies.

Ethan Hall

Cadet
Joined
Apr 17, 2016
Messages
4
I recently built my freenas system and have setup plex on it to stream my media. Every once and while the plugin will just crash and will be shown as off in the plugins list. If i try to turn it back on it shows the loading sign for a few seconds then nothing happens and its still off. I have tried restarting the jail associated with plex and the only way to fix this is by reinstalling the plugin, which means I have to reconfigure all the storage and plex has to re download all the metadata and re sort every thing. Can someone help me figure out why this is happening? thanks!
 
D

dlavigne

Guest
Build version (from System -> Information)? Also, post the output of /var/log/messages.
 

Ethan Hall

Cadet
Joined
Apr 17, 2016
Messages
4
Build version (from System -> Information)? Also, post the output of /var/log/messages.
I am running build 9.1 output of /var/log/messages:(sorry i am not sure how to format a code block on this forum so im just posting it raw...)
`
Apr 20 00:00:00 freenas newsyslog[27239]: logfile turned over due to size>100K
Apr 20 00:00:00 freenas syslog-ng[1284]: Configuration reload request received, reloading configuration;
Apr 20 01:00:00 freenas shutdown: power-down by root:
Apr 20 08:00:00 freenas dhclient[869]: connection closed
Apr 20 08:00:00 freenas dhclient[869]: exiting.
Apr 20 01:00:01 freenas syslog-ng[29222]: syslog-ng starting up; version='3.6.4'
Apr 20 01:00:01 freenas kernel: pid 1284 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Apr 20 08:00:07 freenas devd: notify_clients: send() failed; dropping unresponsive client
Apr 20 08:00:09 freenas devd: Executing '/etc/pccard_ether epair1b start'
Apr 20 01:00:09 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Apr 20 01:00:09 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Apr 20 01:00:09 freenas kernel: ifa_del_loopback_route: deletion failed: 48
Apr 20 01:00:09 freenas Freed UMA keg (udp_inpcb) was not empty (60 items). Lost 6 pages of memory.
Apr 20 01:00:09 freenas Freed UMA keg (udpcb) was not empty (668 items). Lost 4 pages of memory.
Apr 20 01:00:09 freenas Freed UMA keg (tcptw) was not empty (270 items). Lost 6 pages of memory.
Apr 20 01:00:09 freenas Freed UMA keg (tcp_inpcb) was not empty (60 items). Lost 6 pages of memory.
Apr 20 01:00:09 freenas Freed UMA keg (tcpcb) was not empty (27 items). Lost 9 pages of memory.
Apr 20 01:00:09 freenas hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Apr 20 01:00:09 freenas hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Apr 20 01:00:11 freenas kernel: epair0a: link state changed to DOWN
Apr 20 01:00:11 freenas kernel: epair0a: link state changed to DOWN
Apr 20 01:00:11 freenas kernel: epair0b: link state changed to DOWN
Apr 20 01:00:11 freenas kernel: epair0b: link state changed to DOWN
Apr 20 01:00:40 freenas mDNSResponder: mDNSResponder (Engineering Build) (Apr 11 2016 18:06:30) stopping
Apr 20 01:00:40 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 000000080147C580 01 25 _smb._tcp.local. PTR free
Apr 20 01:00:40 freenas mDNSResponder: mDNS_FinalExit failed to send goodbye for: 00000008014C8580 01 26 _http._tcp.local. PTR fre
Apr 20 01:00:40 freenas smbd: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Apr 20 01:00:40 freenas cnid_metad[2255]: shutting down on SIGTERM
Apr 20 01:00:40 freenas afpd[2254]: AFP Server shutting down
Apr 20 01:00:40 freenas netatalk[2244]: Netatalk AFP server exiting
Apr 20 01:00:42 freenas ntpd[1591]: ntpd exiting on signal 15 (Terminated)
Apr 20 01:00:47 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Apr 20 01:00:48 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Apr 20 01:00:49 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Apr 20 01:00:50 freenas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:4 Err:-1 Errno:61 Conn
Apr 20 01:00:52 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Apr 20 01:00:53 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Apr 20 01:00:54 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Apr 20 01:00:55 freenas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:4 Err:-1 Errno:61 Conn
Apr 20 01:00:58 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Apr 20 01:00:59 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Apr 20 01:01:00 freenas python: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Apr 20 01:01:01 freenas python: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:4 Err:-1 Errno:61 Conn`
 
D

dlavigne

Guest
Hardware specs?

And you're running version 9.1? That's nearly 3 years old...
 

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527
They probably meant 9.10.

P.S.
Here's how to insert code tags:
 

Attachments

  • Code_Tags.png
    Code_Tags.png
    7.8 KB · Views: 275

typojoe

Cadet
Joined
Apr 17, 2016
Messages
1
Very curious to see what you guys have to say about this because I had a very similar experience. Except min stopped working after a FreeNAS update. Now it has me worried about the stability of my new system. Worst part is, I have an alert saying there's a new update available, but I'm scare to update it.
 
Status
Not open for further replies.
Top