new to FreeNAS and need help with logs

[pix]

so i've had FreeNAS (newest) running for a few weeks now. 6x2TB RaidZ2.

I've setup 4 jails of available plugins and was working on getting a 5th working manually (read the wiki for choosing which jail template to use (pluginjail).

The 5th jail i'm trying to setup is DokuWiki from the ports and not having much success. After trying a few times and deleting and recreating the jail i have started getting this email report.

sidenote: i've been using the same ip when i delete and recreate the jail.

i do not know what all these Lost Pages messages mean.

all i could find on the forum was something about the vnet on the jails. can someone tell me if this is a serious message or how to fix it and avoid it? i'm still searching through the forums while i post this.

Code:

freenas.local kernel log messages:
> epair4a: link state changed to DOWN
> epair4b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (30 items).  Lost 3 pages of memory.
> Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
> Freed UMA keg (tcpreass) was not empty (588 items).  Lost 7 pages of memory.
> Freed UMA keg (tcptw) was not empty (50 items).  Lost 1 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
> Freed UMA keg (tcpcb) was not empty (12 items).  Lost 3 pages of memory.
> Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair4a: Ethernet address: 02:24:19:00:0c:0a
> epair4b: Ethernet address: 02:24:19:00:0d:0b
> epair4a: link state changed to UP
> epair4b: link state changed to UP
> epair4a: promiscuous mode enabled
> epair4a: link state changed to DOWN
> epair4b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
> Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
> Freed UMA keg (tcptw) was not empty (50 items).  Lost 1 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
> Freed UMA keg (tcpcb) was not empty (8 items).  Lost 2 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.0.5 moved from 02:b9:f1:00:0b:0a to bc:5f:f4:e7:99:f0 on epair3b
> arp: 192.168.0.5 moved from 02:c4:7b:00:0a:0a to bc:5f:f4:e7:99:f0 on epair2b
> arp: 192.168.0.5 moved from 02:50:84:00:08:0a to bc:5f:f4:e7:99:f0 on epair0b
> epair4a: Ethernet address: 02:70:b2:00:0c:0a
> epair4b: Ethernet address: 02:70:b2:00:0d:0b
> epair4a: link state changed to UP
> epair4b: link state changed to UP
> epair4a: promiscuous mode enabled
> arp: 192.168.0.5 moved from 02:b9:f1:00:0b:0a to bc:5f:f4:e7:99:f0 on epair3b
> arp: 192.168.0.5 moved from 02:c4:7b:00:0a:0a to bc:5f:f4:e7:99:f0 on epair2b
> arp: 192.168.0.5 moved from 02:50:84:00:08:0a to bc:5f:f4:e7:99:f0 on epair0b
> epair4a: link state changed to DOWN
> epair4b: link state changed to DOWN
> ifa_del_loopback_route: deletion failed
> Freed UMA keg (udp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
> Freed UMA keg (udpcb) was not empty (336 items).  Lost 2 pages of memory.
> Freed UMA keg (tcpreass) was not empty (672 items).  Lost 8 pages of memory.
> Freed UMA keg (tcptw) was not empty (50 items).  Lost 1 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
> Freed UMA keg (tcpcb) was not empty (8 items).  Lost 2 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair4a: Ethernet address: 02:21:0f:00:0c:0a
> epair4b: Ethernet address: 02:21:0f:00:0d:0b
> epair4a: link state changed to UP
> epair4b: link state changed to UP
> epair4a: promiscuous mode enabled
> arp: 192.168.0.5 moved from 02:b9:f1:00:0b:0a to bc:5f:f4:e7:99:f0 on epair3b
> arp: 192.168.0.5 moved from 02:c4:7b:00:0a:0a to bc:5f:f4:e7:99:f0 on epair2b
> arp: 192.168.0.5 moved from 02:50:84:00:08:0a to bc:5f:f4:e7:99:f0 on epair0b

 

[dlavigne]

Nothing exciting in the messages. What issue are you having with the jail?

 

[pix]

not having any troubles with the jails i already setup using the plugins repo. i only started getting those Lost Pages messages in the email log tonight. And the only changes I've been making this night is deleting and recreating a jail with the same reused IP. the reason i'm doing this is because i keep following different guides trying to get the dokuwiki port up and running. i can install it just fine, and the address pings but nothing is connected and i see nothing running when i do a sockstat.

i was thinking these messages had something to do with why my dokuwiki install wasn't working correctly.


if there's nothing exciting or something to worry about in the logs then i'll keep trying out different guides in hopes of installing dokuwiki. :)

 

[dlavigne]

Are you using the em driver (from the output of ifconfig)? If so, those messages are related to the driver: https://bugs.freenas.org/issues/4058.

 

[pix]

i am using the defaults that the "pluginsjail" template has checked and VIMAGE is one of the boxes that is checked by default. i leave all defaults and i have stopped and started the jail and deleted and recreated it a few times, however i have no come across the issue with having to do a hard reset/restart.