After a crash (electricity issue), network in my jail is not working properly

[benamira]

I have a jail with plexmediaserver installed.
I had yesterday an unexpected power off of my system.
I turned on after this crash and everything seemed to be working well, but when trying to access to the server of my plex jail, it can not access to the server.

I reach with ping to the jail, can connect, ssh, and top to see that plexmediaserver is running.
After further investigation I have checked the jail and found but some errors when booting the system and i guess something in the network of the jail is broken or is not working properly.

I get this log:

1. Sep 12 18:08:50 media notifier: Performing sanity check on nginx configuration:
2. Sep 12 18:08:50 media notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
3. Sep 12 18:08:50 media notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
4. Sep 12 18:08:50 media kernel: bridge0: Ethernet address: 02:ce:57:c5:7c:00
5. Sep 12 18:08:50 media kernel: bridge0: link state changed to UP
6. Sep 12 18:08:50 media kernel: em0: promiscuous mode enabled
7. Sep 12 18:08:50 media kernel: epair0a: Ethernet address: 02:09:52:00:07:0a
8. Sep 12 18:08:50 media kernel: epair0b: Ethernet address: 02:09:52:00:08:0b
9. Sep 12 18:08:50 media kernel: epair0a: link state changed to UP
10. Sep 12 18:08:50 media kernel: epair0b: link state changed to UP
11. Sep 12 18:08:51 media kernel: em0: link state changed to DOWN
12. Sep 12 18:08:51 media kernel: epair0a: promiscuous mode enabled
13. Sep 12 18:08:51 media kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
14. Sep 12 18:08:50 media rtsold[1703]: <rtsock_input_ifannounce> interface epair0b removed
15. Sep 12 18:08:54 media kernel: em0: link state changed to UP
16. Sep 12 18:12:07 media kernel: ifa_del_loopback_route: deletion failed
17. Sep 12 18:12:07 media kernel: Freed UMA keg (udp_inpcb) was not empty (40 items). Lost 4 pages of memory.
18. Sep 12 18:12:07 media kernel: Freed UMA keg (udpcb) was not empty (504 items). Lost 3 pages of memory.
19. Sep 12 18:12:07 media kernel: Freed UMA keg (tcptw) was not empty (200 items). Lost 4 pages of memory.
20. Sep 12 18:12:07 media kernel: Freed UMA keg (tcp_inpcb) was not empty (50 items). Lost 5 pages of memory.
21. Sep 12 18:12:07 media kernel: Freed UMA keg (tcpcb) was not empty (32 items). Lost 8 pages of memory.
22. Sep 12 18:12:07 media kernel: hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
23. Sep 12 18:12:07 media kernel: hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

Can someone help me to repair my config...
Thanks in advance.

 

[dlavigne]

Please create a bug report at bugs.freenas.org that contains this info and that error log and post the issue number here.

 

[benamira]

Issue Number: #6079.
Thanks for your attention. Something weird in my config after the crash :-(

 

[benamira]

So, this was not the right way.
Any idea of what is broken in my config??
Does the log gives any clue? i have been googling with no success.

thanks for your help

 

[cyberjock]

No clue what is broken in your config, but there's a good chance if you had used a UPS to do a proper shutdown you wouldn't be in this predicament. ;)

This is why we strongly urge people to buy and setup the UPS in FreeNAS so proper shutdowns can be performed. To answer your question about the logs, they'll only provide a small clue. You'd have to take the log message and go back through the code to figure out what is being pulled from your config file and see if that is bogus or not.

 

[benamira]

Thanks for your advise, i was looking to buy one, but now i'll do sooner than later.
Would you recommend any UPS with a good integration with freenas??

thanks!