Can't create jails

Status
Not open for further replies.

biltong

Dabbler
Joined
Apr 21, 2015
Messages
13
I'm getting "unable to find template" whenever I try to create a jail from the web GUI. I have searched and seen that this seems to be a fairly common problem with lots of different causes thanks to the unhelpful message.

Most of the answers I've seen for this is "your nas is not connected to the internet" but mine is, and my problem is whenever I try to create a template it will actually download the template completely then once it's downloaded it just says "unable to find template".

Code:
# warden template list
Jail Templates:
------------------------------
pluginjail - FreeBSD  (amd64)
pluginjail--x64 - FreeBSD  (amd64)
standard--x64 - FreeBSD  (amd64)


In the past I have created a standard jail without issue, and that jail is still running, so I don't know why it now wants me to redownload it every time I try create it (and I have tried MANY times).

I'm able to create a jail manually with warden using the standard--x64 template but get some errors while doing it:
Code:
~# warden create nzbget --ipv4 DHCP --src --ports --jailtype portjail --template standard--x64
Building new Jail... Please wait...
zfs clone storage/jails/.warden-template-standard--x64@clean storage/jails/nzbget
Boot-strapping pkgng
cp: /usr/local/etc/pkg-pubkey.cert: No such file or directory
cp: /usr/local/share/pcbsd/conf/server-excludes: No such file or directory
/usr/local/share/warden/scripts/backend/createjail.sh: aria2c: not found
cp: /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE/amd64/pkg.txz: No such file or directory
/usr/local/share/warden/scripts/backend/createjail.sh: aria2c: not found
cp: /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE/amd64/repo.txz: No such file or directory
ERROR: Failed boot-strapping PKGNG, most likely cause is internet connection failure.
Fetching ports...
cat: /usr/sbin/portsnap: No such file or directory
Done
Added new repo: "Official PC-BSD Repository" to the database.
Success!
Jail created at /mnt/storage/jails/nzbget


I'm a little concerned that it's looking at 9.1 instead of 9.3 there.

This is what my jails permissions are:
Code:
/mnt/storage/jails# ls -la
total 267
drwxrwxrwx  27 root  wheel  29 Aug 30 12:46 ./
drwxrwxr-x+  7 root  wheel   7 Jun 20 14:50 ../
drwxr-xr-x   2 root  wheel  18 Apr  8 22:03 .couchpotato_1.meta/
drwxr-xr-x   2 root  wheel  18 Aug 26 20:38 .customplugin_1.meta/
drwxr-xr-x   2 root  wheel   2 Aug 30 11:54 .download/
-rw-r--r--   1 root  wheel   0 Aug 30 11:53 .fbsd-aria-stat-amd64
drwxrwxrwx   2 root  wheel  17 Mar 23 19:38 .gcc.meta/
drwxr-xr-x   2 root  wheel  18 Apr  8 22:11 .headphones_1.meta/
drwxr-xr-x   2 root  wheel  13 Aug 30 12:46 .nzbget.meta/
-rw-r--r--   1 root  wheel   0 Aug 30 12:46 .pcbsd-aria-stat-amd64
drwxr-xr-x   2 root  wheel  18 Apr  5 20:23 .plexmediaserver_1.meta/
drwxrwxrwx   3 root  wheel   3 Mar 21 09:33 .plugins/
drwxr-xr-x   2 root  wheel  18 Apr  8 21:36 .sabnzbd_1.meta/
drwxr-xr-x   2 root  wheel  18 Apr 11 15:19 .sonarr_1.meta/
drwxr-xr-x   2 root  wheel  18 Apr  8 21:31 .transmission_1.meta/
drwxrwxrwx   5 root  wheel   5 Aug 25 08:29 .warden-files-cache/
drwxr-xr-x  18 root  wheel  22 Aug 25 23:20 .warden-template-pluginjail/
drwxrwxrwx  18 root  wheel  22 Mar 21 09:53 .warden-template-pluginjail--x64/
drwxr-xr-x  17 root  wheel  21 Aug 30 12:27 .warden-template-standard/
drwxrwxrwx  17 root  wheel  21 Mar 22 16:40 .warden-template-standard--x64/
drwxr-xr-x  18 root  wheel  22 Mar 21 09:53 couchpotato_1/
drwxr-xr-x  18 root  wheel  22 Aug 25 23:20 customplugin_1/
drwxrwxrwx  17 root  wheel  21 Mar 22 16:40 gcc/
drwxr-xr-x  18 root  wheel  22 Mar 21 09:53 headphones_1/
drwxr-xr-x  17 root  wheel  22 Aug 30 12:46 nzbget/
drwxr-xr-x  18 root  wheel  22 Mar 21 09:53 plexmediaserver_1/
drwxr-xr-x  18 root  wheel  22 Mar 21 09:53 sabnzbd_1/
drwxr-xr-x  18 root  wheel  22 Mar 21 09:53 sonarr_1/
drwxr-xr-x  18 root  wheel  22 Apr  8 21:54 transmission_1/


Code:
[root@steve] /mnt/storage/jails# cd .warden-files-cache/
[root@steve] /mnt/storage/jails/.warden-files-cache# ls -la
total 13
drwxrwxrwx   5 root  wheel   5 Aug 25 08:29 ./
drwxrwxrwx  27 root  wheel  29 Aug 30 12:46 ../
drwxrwxrwx   3 root  wheel   3 Aug 30 11:53 distfiles/
drwxr-xr-x   2 root  wheel   3 Aug 26 01:00 mtree/
drwxrwxrwx   3 root  wheel   3 Aug 30 11:53 packages/
[root@steve] /mnt/storage/jails/.warden-files-cache# cd packages/
[root@steve] /mnt/storage/jails/.warden-files-cache/packages# ls
./           ../          9.1-RELEASE/
[root@steve] /mnt/storage/jails/.warden-files-cache/packages# cd 9.1-RELEASE/
[root@steve] /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE# ls
./     ../    amd64/
[root@steve] /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE# cd amd64
[root@steve] /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE/amd64# ls
./  ../
[root@steve] /mnt/storage/jails/.warden-files-cache/packages/9.1-RELEASE/amd64# ls -la
total 1
drwxr-xr-x  2 root  wheel  2 Aug 30 11:53 ./
drwxr-xr-x  3 root  wheel  3 Aug 30 11:53 ../


After creating the jail I'm unable to start it from the web GUI. It says it starts successfully but the status says "stopped" and jls doesn't show that it is running. I also can't start it with warden:

Code:
# warden start nzbget
Mounting user-supplied file-systems
ifconfig: DHCP: bad value
jail -c path=/mnt/storage/jails/nzbget ip4.addr=DHCP host.hostname=nzbget allow.raw_sockets=true persist
jail: ip4.addr: not an IPv4 address: DHCP
ERROR: Failed starting jail with above command...
Unmounting /mnt/storage/jails/nzbget/proc


Does anyone know what's going on here?

Edit: right, forgot the important information.

Running FreeNAS-9.3-STABLE-201508250051
Core i3 i3-4160 @ 3.60GHz
Asrock Z87E ITX/M Motherboard
16GB Kingston HyperX Fury DDR3-1600, CL10, 1.5v
Corsair CXM430 PSU
3x1TB WD Reds, 3x2TB WD Reds, two separate ZFS arrays
(I know not server grade stuff, that stuff's hard to come by where I live and this is just for home stuff)


Dmesg:
Code:
uhub2: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.04, addr 2> on usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.04, addr 2> on usbus1
uhub2: 6 ports with 6 removable, self powered
uhub3: 8 ports with 8 removable, self powered
ugen0.3: <Broadcom Corp> at usbus0
ugen1.3: <Kingston> at usbus1
umass0: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 3> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:7:0:-1: Attached to scbus7
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada0: Serial Number WD-WCC4M2VKJALZ
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: <Kingston DataTraveler 2.0 PMAP> Removable Direct Access SCSI-4 device
da0: Serial Number 6CF049E3311BBF1159011325
da0: 40.000MB/s transfers
da0: 15004MB (30728832 512 byte sectors: 255H 63S/T 1912C)
da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada1: Serial Number WD-WCC4M0VR15YY
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada2: Serial Number WD-WCC4M2VKJCK1
ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada3: Serial Number WD-WCC4J0LS24JN
ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada3: quirks=0x1<4K>
ada3: Previously was known as ad10
ada4 at ahcich4 bus 0 scbus4 target 0 lun 0
ada4: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada4: Serial Number WD-WCC4J0VJR8HT
ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada4: quirks=0x1<4K>
ada4: Previously was known as ad12
ada5 at ahcich5 bus 0 scbus5 target 0 lun 0
ada5: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada5: Serial Number WD-WCC4J3LDEEN7
ada5: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada5: quirks=0x1<4K>
ada5: Previously was known as ad14
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC-low" frequency 1799512290 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201508250051 []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...0 done
All buffers synced.
Uptime: 1m10s
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
   The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.3-RELEASE-p23 #2 r281084+e56b349: Fri Aug 21 21:59:07 PDT 2015
  root@build3.ixsystems.com:/tank/home/jkh/build/FN/objs/os-base/amd64/tank/home/jkh/build/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz (3599.02-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x306c3  Family = 0x6  Model = 0x3c  Stepping = 3
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7fdafbbf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,<b11>,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x21<LAHF,ABM>
  Standard Extended Features=0x27ab<GSFSBASE,TSCADJ,SMEP,ENHMOVSB,INVPCID>
  TSC: P-state invariant, performance statistics
real memory  = 17706254336 (16886 MB)
avail memory = 16182005760 (15432 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ACPI Warning: FADT (revision 5) is longer than ACPI 5.0 version, truncating length 268 to 256 (20111123/tbfadt-325)
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ispfw: registered firmware <isp_1040>
ispfw: registered firmware <isp_1040_it>
ispfw: registered firmware <isp_1080>
ispfw: registered firmware <isp_1080_it>
ispfw: registered firmware <isp_12160>
ispfw: registered firmware <isp_12160_it>
ispfw: registered firmware <isp_2100>
ispfw: registered firmware <isp_2200>
ispfw: registered firmware <isp_2300>
ispfw: registered firmware <isp_2322>
ispfw: registered firmware <isp_2400>
ispfw: registered firmware <isp_2400_multi>
ispfw: registered firmware <isp_2500>
ispfw: registered firmware <isp_2500_multi>
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I> on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem 0xf0000000-0xf03fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
vgapci0: Boot video device
pci0: <multimedia, HDA> at device 3.0 (no driver attached)
pci0: <serial bus, USB> at device 20.0 (no driver attached)
pci0: <simple comms> at device 22.0 (no driver attached)
em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xf080-0xf09f mem 0xf0700000-0xf071ffff,0xf073d000-0xf073dfff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: bc:5f:f4:b1:1e:b6
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf073c000-0xf073c3ff irq 16 at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci2: <ACPI PCI bus> on pcib2
pci2: <network> at device 0.0 (no driver attached)
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf073b000-0xf073b3ff irq 23 at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf0d0-0xf0d7,0xf0c0-0xf0c3,0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf060-0xf07f mem 0xf073a000-0xf073a7ff irq 19 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
acpi_button0: <Power Button> on acpi0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ugen0.2: <vendor 0x8087> at usbus0
uhub2: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.04, addr 2> on usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.04, addr 2> on usbus1
uhub2: 6 ports with 6 removable, self powered
uhub3: 8 ports with 8 removable, self powered
ugen0.3: <Broadcom Corp> at usbus0
ugen1.3: <Kingston> at usbus1
umass0: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 3> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:7:0:-1: Attached to scbus7
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada0: Serial Number WD-WCC4M2VKJALZ
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0: <Kingston DataTraveler 2.0 PMAP> Removable Direct Access SCSI-4 device
da0: Serial Number 6CF049E3311BBF1159011325
da0: 40.000MB/s transfers
da0: 15004MB (30728832 512 byte sectors: 255H 63S/T 1912C)
da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada1: Serial Number WD-WCC4M0VR15YY
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <WDC WD20EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
ada2: Serial Number WD-WCC4M2VKJCK1
ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada3: Serial Number WD-WCC4J0LS24JN
ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada3: quirks=0x1<4K>
ada3: Previously was known as ad10
ada4 at ahcich4 bus 0 scbus4 target 0 lun 0
ada4: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada4: Serial Number WD-WCC4J0VJR8HT
ada4: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada4: Command Queueing enabled
ada4: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada4: quirks=0x1<4K>
ada4: Previously was known as ad12
ada5 at ahcich5 bus 0 scbus5 target 0 lun 0
ada5: <WDC WD10EFRX-68FYTN0 82.00A82> ATA-9 SATA 3.x device
ada5: Serial Number WD-WCC4J3LDEEN7
ada5: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada5: Command Queueing enabled
ada5: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada5: quirks=0x1<4K>
ada5: Previously was known as ad14
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Timecounter "TSC-low" frequency 1799512100 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201508250051 []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
GEOM_ELI: Device ada3p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device ada4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device ada5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device ada0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device ada1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
GEOM_ELI: Device ada2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:  Crypto: hardware
vboxdrv: fAsync=0 offMin=0x1cc offMax=0xf38
bridge0: Ethernet address: 02:38:21:8b:b8:00
em0: promiscuous mode enabled
bridge0: link state changed to UP
epair0a: Ethernet address: 02:75:7b:00:07:0a
epair0b: Ethernet address: 02:75:7b:00:08:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
em0: link state changed to DOWN
epair0a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair0b
em0: link state changed to UP
epair1a: Ethernet address: 02:99:78:00:08:0a
epair1b: Ethernet address: 02:99:78:00:09:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair1a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair1b
epair2a: Ethernet address: 02:30:b9:00:09:0a
epair2b: Ethernet address: 02:30:b9:00:0a:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair2a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair2b
epair3a: Ethernet address: 02:e9:85:00:0a:0a
epair3b: Ethernet address: 02:e9:85:00:0b:0b
epair3a: link state changed to UP
epair3b: link state changed to UP
epair3a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair3b
epair4a: Ethernet address: 02:09:1a:00:0b:0a
epair4b: Ethernet address: 02:09:1a:00:0c:0b
epair4a: link state changed to UP
epair4b: link state changed to UP
epair4a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair4b
epair5a: Ethernet address: 02:a8:d4:00:0c:0a
epair5b: Ethernet address: 02:a8:d4:00:0d:0b
epair5a: link state changed to UP
epair5b: link state changed to UP
epair5a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair5b
epair6a: Ethernet address: 02:53:a4:00:0d:0a
epair6b: Ethernet address: 02:53:a4:00:0e:0b
epair6a: link state changed to UP
epair6b: link state changed to UP
epair6a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair6b
epair3a: link state changed to DOWN
epair3b: link state changed to DOWN
epair0a: link state changed to DOWN
epair0b: link state changed to DOWN
epair1a: link state changed to DOWN
epair1b: link state changed to DOWN
epair4a: link state changed to DOWN
epair4b: link state changed to DOWN
epair6a: link state changed to DOWN
epair6b: link state changed to DOWN
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (tcpcb) was not empty (16 items).  Lost 4 pages of memory.
Freed UMA keg (ripcb) was not empty (30 items).  Lost 3 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
epair2a: link state changed to DOWN
epair2b: link state changed to DOWN
epair5a: link state changed to DOWN
epair5b: link state changed to DOWN
em0: link state changed to DOWN
em0: promiscuous mode disabled
bridge0: link state changed to DOWN
em0: link state changed to UP
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcptw) was not empty (200 items).  Lost 4 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (tcpcb) was not empty (24 items).  Lost 6 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
bridge0: Ethernet address: 02:38:21:8b:b8:00
em0: promiscuous mode enabled
bridge0: link state changed to UP
epair0a: Ethernet address: 02:e4:fb:00:07:0a
epair0b: Ethernet address: 02:e4:fb:00:08:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
em0: link state changed to DOWN
epair0a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair0b
em0: link state changed to UP
arp: 10.0.0.252 moved from 02:e4:fb:00:07:0a to bc:5f:f4:b1:1e:b6 on epair0b
epair1a: Ethernet address: 02:65:ab:00:08:0a
epair1b: Ethernet address: 02:65:ab:00:09:0b
epair1a: link state changed to UP
epair1b: link state changed to UP
epair1a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair1b
epair2a: Ethernet address: 02:84:05:00:09:0a
epair2b: Ethernet address: 02:84:05:00:0a:0b
epair2a: link state changed to UP
epair2b: link state changed to UP
epair2a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair2b
epair3a: Ethernet address: 02:02:43:00:0a:0a
epair3b: Ethernet address: 02:02:43:00:0b:0b
epair3a: link state changed to UP
epair3b: link state changed to UP
epair3a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair3b
epair4a: Ethernet address: 02:c7:d1:00:0b:0a
epair4b: Ethernet address: 02:c7:d1:00:0c:0b
epair4a: link state changed to UP
epair4b: link state changed to UP
epair4a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair4b
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcptw) was not empty (200 items).  Lost 4 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (80 items).  Lost 8 pages of memory.
Freed UMA keg (tcpcb) was not empty (44 items).  Lost 11 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
epair5a: Ethernet address: 02:1a:18:00:0c:0a
epair5b: Ethernet address: 02:1a:18:00:0d:0b
epair5a: link state changed to UP
epair5b: link state changed to UP
epair5a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair5b
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (70 items).  Lost 7 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcptw) was not empty (250 items).  Lost 5 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (70 items).  Lost 7 pages of memory.
Freed UMA keg (tcpcb) was not empty (36 items).  Lost 9 pages of memory.
Freed UMA keg (ripcb) was not empty (30 items).  Lost 3 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: 10.0.0.252 moved from 02:1a:18:00:0c:0a to bc:5f:f4:b1:1e:b6 on epair5b
arp: 10.0.0.252 moved from 02:c7:d1:00:0b:0a to bc:5f:f4:b1:1e:b6 on epair4b
arp: 10.0.0.252 moved from 02:02:43:00:0a:0a to bc:5f:f4:b1:1e:b6 on epair3b
arp: 10.0.0.252 moved from 02:84:05:00:09:0a to bc:5f:f4:b1:1e:b6 on epair2b
arp: 10.0.0.252 moved from 02:65:ab:00:08:0a to bc:5f:f4:b1:1e:b6 on epair1b
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (60 items).  Lost 6 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcptw) was not empty (250 items).  Lost 5 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (100 items).  Lost 10 pages of memory.
Freed UMA keg (sackhole) was not empty (202 items).  Lost 2 pages of memory.
Freed UMA keg (tcpcb) was not empty (48 items).  Lost 12 pages of memory.
Freed UMA keg (ripcb) was not empty (30 items).  Lost 3 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
ifa_del_loopback_route: deletion failed
Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Freed UMA keg (tcptw) was not empty (250 items).  Lost 5 pages of memory.
Freed UMA keg (tcp_inpcb) was not empty (90 items).  Lost 9 pages of memory.
Freed UMA keg (tcpcb) was not empty (32 items).  Lost 8 pages of memory.
Freed UMA keg (ripcb) was not empty (30 items).  Lost 3 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
epair6a: Ethernet address: 02:b9:ac:00:0d:0a
epair6b: Ethernet address: 02:b9:ac:00:0e:0b
epair6a: link state changed to UP
epair6b: link state changed to UP
epair6a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair6b
swap_pager_getswapspace(16): failed
swap_pager_getswapspace(16): failed
pid 2896 (python2.7), uid 0, was killed: out of swap space
pid 78622 (Plex Media Scanner), uid 972: exited on signal 6
arp: 10.0.0.252 moved from 02:b9:ac:00:0d:0a to bc:5f:f4:b1:1e:b6 on epair6b
arp: 10.0.0.252 moved from 02:1a:18:00:0c:0a to bc:5f:f4:b1:1e:b6 on epair5b
arp: 10.0.0.252 moved from 02:c7:d1:00:0b:0a to bc:5f:f4:b1:1e:b6 on epair4b
arp: 10.0.0.252 moved from 02:02:43:00:0a:0a to bc:5f:f4:b1:1e:b6 on epair3b
arp: 10.0.0.252 moved from 02:84:05:00:09:0a to bc:5f:f4:b1:1e:b6 on epair2b
arp: 10.0.0.252 moved from 02:65:ab:00:08:0a to bc:5f:f4:b1:1e:b6 on epair1b
arp: 10.0.0.252 moved from 02:e4:fb:00:07:0a to bc:5f:f4:b1:1e:b6 on epair0b


Debug info is attached.
 

Attachments

  • debug-steve-20150830185017..tgz
    586 KB · Views: 225
Last edited:

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Can you try creating a new dataset called jail2 for example. Then under the jail configuring change the root path to be the new dataset. Then try to deploy a jail/plugin.

If this works then it's not a networking problem. It's probably that the permissions or something for changed on your old datasets. I notice your gcc jail has different permissions which makes me think things have been messed with.

Also please read the forum rules and provide that information.
 

biltong

Dabbler
Joined
Apr 21, 2015
Messages
13
Right, sorry, forgot about all that. Updated OP with more info of my system.

I tried doing as you said, it looks like the jail download stalled:

jails.PNG


I've noticed in the past that there's a bsdtar process that spawns when I start creating a jail and it downloads the template. No such luck with this time, and there was zero activity over my wan interface so it seems something hung or broke silently.

EDIT: Ok so I changed my configuration back and changed permissions on my datasets to 755 as the others all were and tried again. Same thing happened. Immediately afterwards I saved the debug information again and started looking through everything, and in debug.log I found this:
Code:
extract-tarball: Houston! We have a problem!

mtree: line 28596 too long
ERROR: mtree failed for /mnt/storage/jails/.warden-files-cache/mtree/freenas-standard-9.3-RELEASE.mtree
cannot open 'storage/jails/.warden-template-standard': dataset does not exist
find: /mnt/storage/jails/.warden-template-standard: No such file or directory
ERROR: Failed to create ZFS base dataset


So I pulled the mtree and went to line 28596 and saw that the hash is actually shorter than everything else in it:

mtree.PNG


Line 28596 also happens to be the very last line in the file.

I'm going to try remove this mtree and redownload and see how it behaves.
 
Last edited:

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Don't ever change the permissions on your jail dataset that will never fix your problem, just cause more.

I think the jail process is download the tarball, unzip it, then clone the data. Is there maybe some reason one of those steps might be failing? I suspect the clone is failing since you have copies of the jails.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
ever figure out the issue? happening to me. tried all steps.
Start a new thread, this one is over 2 years old and likely a different version of FreeNAS that you are running.

Necro post strikes again...........
 
Status
Not open for further replies.
Top