paradoxiom
Patron
- Joined
- Jun 16, 2015
- Messages
- 239
So I have FreeNAS 9.3 on an HP Gen8 MicroServer (signature specs), all firmware is up to date etc and at the moment all it has on it is FreeNAS with Plex manually installed in a jail (didn't use plugin manager thing). I use CIFS to transfer files to and from the server.
Aside from worrying errors like these everything runs perfectly fine.
Bolded the parts I'm unsure about. I've tried googling each one (and variations from other times I've seen them in the logs) numerous times but I always end up at the same google results for each one, and they either end in "harmless error nothing to worry about ignore it" or people not having any clue how to resolve it.
So firstly the "can't re-name node epair0b" I get this almost all the time after starting up, what does it mean and how can I 'fix' whatever it 'wrong' to stop it showing in the log? I don't want to simply turn logging a step down or anything like that for any of this.
"kernel: ifa_del_loopback_route: deletion failed" is a fairly new one I don't see often, no idea here either.
"Freed UMA keg (udp_inpcb) was not empty (100 items). Lost 10 pages of memory."
My server seems to run fine all day without this showing up, but then I go to sleep and wake up in the morning and the log has at least one instance of all these "Freed UMA keg" lines, the server being idle all night. I believe google search indicated it might be something related to Plex but again I couldn't find a definitive way to fix this. This one bothers me because as I understand it ZFS likes RAM(memory) a lot and bad things happen if it doesn't like the RAM, could that be what is happening here? This link has a couple of people mentioning that they also get this error with the HP Gen8 MicroServer which is what I have too, so I don't know if there's a link there.
If it's any help, this is the exact RAM I use x2.
"hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required"
Another one I see often, I think usually after a bootup but I can't really remember, again no idea how to 'cleanup' whatever needs cleaning up to fix this.
Hopefully these are quick fixes I can do but if not I'm of course willing to find log files and post them etc (wherever they may be) to try and sort these out.
Thanks in advance,
para
Aside from worrying errors like these everything runs perfectly fine.
Bolded the parts I'm unsure about. I've tried googling each one (and variations from other times I've seen them in the logs) numerous times but I always end up at the same google results for each one, and they either end in "harmless error nothing to worry about ignore it" or people not having any clue how to resolve it.
So firstly the "can't re-name node epair0b" I get this almost all the time after starting up, what does it mean and how can I 'fix' whatever it 'wrong' to stop it showing in the log? I don't want to simply turn logging a step down or anything like that for any of this.
"kernel: ifa_del_loopback_route: deletion failed" is a fairly new one I don't see often, no idea here either.
"Freed UMA keg (udp_inpcb) was not empty (100 items). Lost 10 pages of memory."
My server seems to run fine all day without this showing up, but then I go to sleep and wake up in the morning and the log has at least one instance of all these "Freed UMA keg" lines, the server being idle all night. I believe google search indicated it might be something related to Plex but again I couldn't find a definitive way to fix this. This one bothers me because as I understand it ZFS likes RAM(memory) a lot and bad things happen if it doesn't like the RAM, could that be what is happening here? This link has a couple of people mentioning that they also get this error with the HP Gen8 MicroServer which is what I have too, so I don't know if there's a link there.
If it's any help, this is the exact RAM I use x2.
"hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required"
Another one I see often, I think usually after a bootup but I can't really remember, again no idea how to 'cleanup' whatever needs cleaning up to fix this.
Hopefully these are quick fixes I can do but if not I'm of course willing to find log files and post them etc (wherever they may be) to try and sort these out.
Thanks in advance,
para
