OctaneZ
Dabbler
- Joined
- Aug 6, 2011
- Messages
- 24
I was having too much trouble with the PBI, it kept failing, wouldn't upgrade. Tore it down built new plugin/pbi/jail for plex, and it didnt work again, (after 3 years of working, I know a lot is changing under the hood right now.
I have a new problem. My jail (standard) "Plex" seems to "move", it has been jls listed as 4,6, and now 9. The NIC also changes, and the route fails.
Here is rc.conf in "Plex" Jail:
The IPv4 address is hardcoded to 192.168.0.60 and never changes across reboots or jail restarts.
ping fails: "55" is the FreeNAS server, "01" is the gateway.
The routing table looks totally hosed, but at least it is using "epair1b":
I am also unable to ping it from the subnet. The GUI/login/jail all worked fine, I let it chug through 4+ TB of data and build the DB. Thoughts as to how to proceed? I may try switching off IPv6, but I am not sure why the jail is moving from 4, to 6, and currently 9, though it seems to be limited to those number right now.
Here is the current "jls" output:
Current Train: FreeNAS-9.10-STABLE (...)
Update Server: http://update.freenas.org/FreeNAS
Freenas Build (Plex Jail Build the same):
I have a new problem. My jail (standard) "Plex" seems to "move", it has been jls listed as 4,6, and now 9. The NIC also changes, and the route fails.
Here is rc.conf in "Plex" Jail:
Code:
portmap_enable="NO" sshd_enable="NO" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" hostname="Plex" devfs_enable="YES" devfs_system_ruleset="devfsrules_common" inet6_enable="YES" ip6addrctl_enable="YES" rtsold_enable="YES" ifconfig_epair5b_ipv6="inet6 accept_rtadv auto_linklocal" plexmediaserver_enable="YES" ifndconfig_epair3b_ipv6="inet6 accept_rtadv auto_linklocal" ifconfig_epair1b_ipv6="inet6 accept_rtadv auto_linklocal"
The IPv4 address is hardcoded to 192.168.0.60 and never changes across reboots or jail restarts.
Code:
root@Plex:~ # ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> epair1b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8<VLAN_MTU> ether 02:ff:b0:00:0a:0b inet 192.168.0.60 netmask 0xffffffff broadcast 192.168.0.60 inet6 fe80::ff:b0ff:fe00:a0b%epair1b prefixlen 64 scopeid 0x2 inet6 2604:xxxx:100f:xxxx:ff:xxxx:fe00:a0b prefixlen 64 autoconf nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>) status: active
ping fails: "55" is the FreeNAS server, "01" is the gateway.
Code:
root@Plex:~ # ping 192.168.0.55 PING 192.168.0.55 (192.168.0.55): 56 data bytes ping: sendto: Network is unreachable ping: sendto: Network is unreachable ^C --- 192.168.0.55 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss root@Plex:~ # ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sendto: Network is unreachable ping: sendto: Network is unreachable ^C --- 192.168.0.1 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss
The routing table looks totally hosed, but at least it is using "epair1b":
Code:
root@Plex:~ # netstat -r Routing tables Internet: Destination Gateway Flags Netif Expire localhost link#1 UH lo0 Plex link#2 UHS lo0 192.168.0.60/32 link#2 U epair1b Internet6: Destination Gateway Flags Netif Expire :: localhost UGRS lo0 default fe80::d217:c2ff:fe UG epair1b localhost link#1 UH lo0 ::ffff:0.0.0.0 localhost UGRS lo0 2604:6000:100f:803 link#2 U epair1b 2604:6000:100f:803 link#2 UHS lo0 fe80:: localhost UGRS lo0 fe80::%lo0 link#1 U lo0 fe80::1%lo0 link#1 UHS lo0 fe80::%epair1b link#2 U epair1b fe80::ff:b0ff:fe00 link#2 UHS lo0 ff01::%lo0 localhost U lo0 ff01::%epair1b fe80::ff:b0ff:fe00 U epair1b ff02:: localhost UGRS lo0 ff02::%lo0 localhost U lo0 ff02::%epair1b fe80::ff:b0ff:fe00 U epair1b
I am also unable to ping it from the subnet. The GUI/login/jail all worked fine, I let it chug through 4+ TB of data and build the DB. Thoughts as to how to proceed? I may try switching off IPv6, but I am not sure why the jail is moving from 4, to 6, and currently 9, though it seems to be limited to those number right now.
Here is the current "jls" output:
Code:
[benc@freenas] /mnt/fourslot-data/benc# jls JID IP Address Hostname Path 1 - firefly_2 /mnt/fourslot-data/jails/firefly_2 3 - s3cmd_1 /mnt/fourslot-data/jails/s3cmd_1 5 - transmission_1 /mnt/fourslot-data/jails/transmission_1 9 - Plex /mnt/fourslot-data/jails/Plex
Current Train: FreeNAS-9.10-STABLE (...)
Update Server: http://update.freenas.org/FreeNAS
Freenas Build (Plex Jail Build the same):
Code:
# uname -a FreeBSD freenas.local 10.3-STABLE FreeBSD 10.3-STABLE #0 455d13d(9.10-STABLE): Sun Jun 26 22:47:03 PDT 2016 root@build.ixsystems.com:/tank/home/nightlies/build-freenas9/_BE/objs/tank/home/nightlies/build-freenas9/_BE/trueos/sys/FreeNAS.amd64 amd64