FreeNAS plugin crashing daily

[trevordj 0]

I have emby up and running on my home server running FreeNAS. Over the last few weeks emby is crashing at least once daily. Once it crashes, I cannot restart it through the webGUI, I have to go into the jail and manually start it using the command 'service emby-server onestart.' I cleared my logs yesterday and this morning I woke up, the plugin crashed again. My logs are posted below. In case it helps, here are specs on my machine: 

 

[a href=http://www.ebay.com/itm/231360168024?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT]Supermicro 836TQ 16 bay chassis[/a]

[a href=http://www.amazon.com/gp/product/B005FYNSZA/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1]SanDisk Cruzer 16GB thumb drive[/a] (for FreeNAS OS)

[a href=http://www.amazon.com/gp/product/B006GD30UC/ref=oh_aui_detailpage_o02_s01?ie=UTF8&psc=1]5 x Noctua 80mm fans [/a] 

[a href=http://www.amazon.com/gp/product/B00DWFQ42I/ref=oh_aui_detailpage_o02_s04?ie=UTF8&psc=1]Noctua heatsink[/a]

[a href=http://www.amazon.com/gp/product/B00JDBYE1I/ref=oh_aui_detailpage_o01_s01?ie=UTF8&psc=1]Cheap samsung console monitor[/a]

[a href=http://www.amazon.com/gp/product/B003NREDC8/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1]Cheap console mouse and keyboard[/a]

[a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16813182927]Supermicro X10SRL motherboard[/a]

[a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16819117512]Intel Xeon E5 processor E5-1620[/a]

[a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16822145973]8 x HGST Deskstar NAS 6TB hard drives[/a]

[a href=http://www.newegg.com/Product/Product.aspx?Item=N82E16820147382]4 x Samsung 16GB 288-pin DDR4 ECC RAM[/a]

[a href=http://www.monoprice.com/Product?c_id=102&cp_id=10226&cs_id=1022602&p_id=5123&seq=1&format=2]A bunch of monoprice SATA cables[/a]

 

A list of the logs:

 

 

Here are the two logs labeled "unhandled"

 

 

 

Any thoughts/ideas on how to fix this is much appreciated!

Edited July 29, 2015 by trevordj

[kjp4756 41]

Just a wild guess here; try turning off the library realtime monitor if it's on.  The kqueue messages lead me to believe that's what it is.

Edited July 29, 2015 by kjp4756

[trevordj 0]

Just a wild guess here; try turning off the library realtime monitor if it's on.  The kqueue messages lead me to believe that's what it is.

Ok, let me give that a shot and see what happens. It definitely IS on by the way. Hopefully the fix is that simple. Thank you!

Edited July 29, 2015 by trevordj

[trevordj 0]

So far so good. The plugin didn't crash overnight like it usually does.