estrabd
Dabbler
- Joined
- Nov 21, 2013
- Messages
- 38
I am running the latest 9.3 on PE 2950. The controller is a m1015 flashed to the lastest IT firmware. All systems are a go...
Except when I stop a jail and restart it, FreeNAS crashes. When done via the WebGUI, I find a message like in the image attached. It hangs for a few minutes, then reboots.
If I start the jail via command line (warden start <jailname>), it hangs without an error output. Then it reboots.
The machine will boot up fine, jail included. A couple of other things to note:
1. this host machine is running a very simple pf nat
2. I have set the jail to use the host as the gateway
3. a "netstat -r" on the gateway prints not values (so gateway is not getting set)
4. relevant portion of dmesg for jail seems to be,
bridge0: bpf attached
bridge0: Ethernet address: 02:a1:e5:5c:0b:00
bce1: promiscuous mode enabled
bridge0: link state changed to UP
epair0a: bpf attached
epair0a: Ethernet address: 02:50:42:00:0c:0a
epair0b: bpf attached
epair0b: Ethernet address: 02:50:42:00:0d:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: promiscuous mode enabled
lo0: bpf attached
ng_ether_ifnet_arrival_event: can't re-name node epair0b
Any thoughts? Could the reboot have anything to do with some weird network/gateway interaction?
TIA,
Brett
Except when I stop a jail and restart it, FreeNAS crashes. When done via the WebGUI, I find a message like in the image attached. It hangs for a few minutes, then reboots.
If I start the jail via command line (warden start <jailname>), it hangs without an error output. Then it reboots.
The machine will boot up fine, jail included. A couple of other things to note:
1. this host machine is running a very simple pf nat
2. I have set the jail to use the host as the gateway
3. a "netstat -r" on the gateway prints not values (so gateway is not getting set)
4. relevant portion of dmesg for jail seems to be,
bridge0: bpf attached
bridge0: Ethernet address: 02:a1:e5:5c:0b:00
bce1: promiscuous mode enabled
bridge0: link state changed to UP
epair0a: bpf attached
epair0a: Ethernet address: 02:50:42:00:0c:0a
epair0b: bpf attached
epair0b: Ethernet address: 02:50:42:00:0d:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
epair0a: promiscuous mode enabled
lo0: bpf attached
ng_ether_ifnet_arrival_event: can't re-name node epair0b
Any thoughts? Could the reboot have anything to do with some weird network/gateway interaction?
TIA,
Brett