network problems jails

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
hey you all.... still having problems... most of the time when jails go idle or something there seems to be problems....
I have to restart a jail and it works again, but after that.... another jail does loose its connection. I really have no idea why....
All have vnet configured no double IP addresses also deleted all addresses from the dhcp server, and still keep on having problems... i never had those problems with the old warden jails. Those were death stable also had no problems in corral with the docker. On 11.2 it is so much work to setup docker and let it work so i keep on using iocage but it is a hell... not stable network is is really a hell. I don't understand the problem....

So i have a couple of jails running
1. couchpotato
2. nzbget
3.Transmission
4. plex
5. minidlna
6. test box

All have vnet configured and all seems to be some time offline and all seem to be some time online.
I have esxi box with lan configured VM Network Promiscuous network and... like i said when i used the warden jails i had no problem, nothing else changed in mij freenas setup.

I really do not understand it any more.....

is there somebody who can hint me in some direction? is there a sleep mode in the iocage? so yes how can i disable it?

also ifconfig in a jail i get
netmask 0xffffff00

however it is set to 24 so it should be 255.255.255.0
 

millst

Contributor
Joined
Feb 2, 2015
Messages
141
Not sure about your problem, but the netmask is fine.

ff = 255
ff = 255
ff = 255
0 = 0
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Hardware and networking setup? I have 6 jails running on a 10gig nic and setup in lagg. A pretty complicated setup and it is working great.

Can you also check out /var/log/messages for anything strange. That log file should be basically empty if nothing is wrong.
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
Hardware and networking setup? I have 6 jails running on a 10gig nic and setup in lagg. A pretty complicated setup and it is working great.

Can you also check out /var/log/messages for anything strange. That log file should be basically empty if nothing is wrong.
Thank you i will check the log... i did not know where it was...

Setup is in my info...
ESXi 6.5 running freenas 11.2 with 72Gb ram and 12 cores @ 2.1Ghz. Using a Supermicro board with 2 intel nics with (i think out of my head i350 chipset....) in lagg in ESXi without any problem in other osses.
Running freenas in esxi in a Promiscuous virtual network with static ip, using my inetrnet provider's dns, al worked perfectly in warden jails.
At some time in idle it seems to loose connection with the jails, this never happend before, some jails will comeback without any issues some will not come back with a connection. Like plex it takes like 3 or 4 minutes before it has it connection bak, and NZBget i have to restart a couple of times to get a connections, also couchpotato has a lot of issues.... sometimes after starting the jail it can not connect at all. that is why i have a dummy jail. Sometimes i start that and stop it and then restart a not working jail and.... it gets a connection... strange i know.
I have this problem since i switch to the new jails in 11.2 before i always used warden jails, but everyone here keep sayng i need to switch.... well i feel stupid i did because i have more trouble then i ever had, and also updates for instance for plex are still very slow, not faster and better then on warden jail was.
When i have problems i can not ping to anywhere even not in my own home network.
Also found another strange bug when trying to use shell (in the web interface not SSH).... when connecting with the IP address or using freenas.local it works, but when using freenas.DOMAIN shell does not work... it did before in 11.1 and before....

Attached the log from one of the not working jails
Schermafbeelding 2019-02-01 om 21.50.17.png


Ifconfig
Code:

root@NZBget:~ # 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>
        groups: lo
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:60:b8:86:31
        hwaddr 02:7d:d0:00:0a:0b
        inet 192.168.178.3 netmask 0xffffff00 broadcast 192.168.178.255
        nd6 options=1<PERFORMNUD>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        groups: epair
root@NZBget:~ #


Using VNET and static ip addresses
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
/var/log/messages from the freenas host not the jail. So you are saying that your setup is esxi setup with a lagg and then you expose a single interface to the freenas server? You have an extremely complicated setup with lots of moving parts, it's going to be hard to figure things out.

and also updates for instance for plex are still very slow, not faster and better then on warden jail was.
Huh? Updating plex is literally the exact same as it was with warden. You run pkg upgrade to update anthing in a jail wether that is iocage or warden.
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
/var/log/messages from the freenas host not the jail. So you are saying that your setup is esxi setup with a lagg and then you expose a single interface to the freenas server? You have an extremely complicated setup with lots of moving parts, it's going to be hard to figure things out.


Huh? Updating plex is literally the exact same as it was with warden. You run pkg upgrade to update anthing in a jail wether that is iocage or warden.
yes i know about plex but it takes a couple of weeks before there is a update for freebsd

I use ESXi just for VM MacOS because i want to use a iTunes server, i can not run macOS in Freenas
Schermafbeelding 2019-02-01 om 22.25.15.png

i will lookup the log file
 
Last edited:

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Yeah the port has to get updated and then the pkg needs to get built.
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
to be extra clear i never had network problems in the warden jails

Code:
Feb  1 21:17:23 freenas newsyslog[1978]: logfile first created
Feb  1 21:17:23 freenas syslog-ng[1996]: syslog-ng starting up; version='3.14.1'
Feb  1 21:17:23 freenas Copyright (c) 1992-2018 The FreeBSD Project.
Feb  1 21:17:23 freenas Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Feb  1 21:17:23 freenas     The Regents of the University of California. All rights reserved.
Feb  1 21:17:23 freenas FreeBSD is a registered trademark of The FreeBSD Foundation.
Feb  1 21:17:23 freenas FreeBSD 11.2-STABLE #0 r325575+fc3d65faae6(HEAD): Thu Dec 20 16:12:30 EST 2018
Feb  1 21:17:23 freenas root@nemesis.tn.ixsystems.com:/freenas-releng-final/freenas/_BE/objs/freenas-releng-final/freenas/_BE/os/sys/FreeNAS.amd64 amd64
Feb  1 21:17:23 freenas FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
Feb  1 21:17:23 freenas VT(vga): text 80x25
Feb  1 21:17:23 freenas CPU: Genuine Intel(R) CPU 0000 @ 2.10GHz (2100.00-MHz K8-class CPU)
Feb  1 21:17:23 freenas Origin="GenuineIntel"  Id=0x406f0  Family=0x6  Model=0x4f  Stepping=0
Feb  1 21:17:23 freenas Features=0xfa3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,MMX,FXSR,SSE,SSE2,SS>
Feb  1 21:17:23 freenas Features2=0xfffa3223<SSE3,PCLMULQDQ,VMX,SSSE3,FMA,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV>
Feb  1 21:17:23 freenas AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Feb  1 21:17:23 freenas AMD Features2=0x121<LAHF,ABM,Prefetch>
Feb  1 21:17:23 freenas Structured Extended Features=0x1c2fbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,RDSEED,ADX,SMAP>
Feb  1 21:17:23 freenas XSAVE Features=0x1<XSAVEOPT>
Feb  1 21:17:23 freenas VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
Feb  1 21:17:23 freenas TSC: P-state invariant
Feb  1 21:17:23 freenas Hypervisor: Origin = "VMwareVMware"
Feb  1 21:17:23 freenas real memory  = 77309411328 (73728 MB)
Feb  1 21:17:23 freenas avail memory = 75095261184 (71616 MB)
Feb  1 21:17:23 freenas Event timer "LAPIC" quality 600
Feb  1 21:17:23 freenas ACPI APIC Table: <PTLTD       APIC  >
Feb  1 21:17:23 freenas FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs
Feb  1 21:17:23 freenas FreeBSD/SMP: 12 package(s)
Feb  1 21:17:23 freenas WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Feb  1 21:17:23 freenas MADT: Forcing active-low polarity and level trigger for SCI
Feb  1 21:17:23 freenas ioapic0 <Version 1.1> irqs 0-23 on motherboard
Feb  1 21:17:23 freenas SMP: AP CPU #1 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #7 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #3 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #5 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #11 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #4 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #2 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #10 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #9 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #8 Launched!
Feb  1 21:17:23 freenas SMP: AP CPU #6 Launched!
Feb  1 21:17:23 freenas random: entropy device external interface
Feb  1 21:17:23 freenas random: registering fast source Intel Secure Key RNG
Feb  1 21:17:23 freenas random: fast provider: "Intel Secure Key RNG"
Feb  1 21:17:23 freenas kbd1 at kbdmux0
Feb  1 21:17:23 freenas nexus0
Feb  1 21:17:23 freenas vtvga0: <VT VGA driver> on motherboard
Feb  1 21:17:23 freenas cryptosoft0: <software crypto> on motherboard
Feb  1 21:17:23 freenas aesni0: <AES-CBC,AES-XTS,AES-GCM,AES-ICM> on motherboard
Feb  1 21:17:23 freenas padlock0: No ACE support.
Feb  1 21:17:23 freenas acpi0: <INTEL 440BX> on motherboard
Feb  1 21:17:23 freenas acpi0: Power Button (fixed)
Feb  1 21:17:23 freenas hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Feb  1 21:17:23 freenas Timecounter "HPET" frequency 14318180 Hz quality 950
Feb  1 21:17:23 freenas cpu0: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu1: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu2: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu3: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu4: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu5: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu6: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu7: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu8: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu9: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu10: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas cpu11: <ACPI CPU> numa-domain 0 on acpi0
Feb  1 21:17:23 freenas attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Feb  1 21:17:23 freenas Timecounter "i8254" frequency 1193182 Hz quality 0
Feb  1 21:17:23 freenas Event timer "i8254" frequency 1193182 Hz quality 100
Feb  1 21:17:23 freenas atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
Feb  1 21:17:23 freenas atrtc0: registered as a time-of-day clock, resolution 1.000000s
Feb  1 21:17:23 freenas Event timer "RTC" frequency 32768 Hz quality 0
Feb  1 21:17:23 freenas Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Feb  1 21:17:23 freenas acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
Feb  1 21:17:23 freenas pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Feb  1 21:17:23 freenas pci0: <ACPI PCI bus> on pcib0
Feb  1 21:17:23 freenas pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
Feb  1 21:17:23 freenas pci1: <ACPI PCI bus> on pcib1
Feb  1 21:17:23 freenas isab0: <PCI-ISA bridge> at device 7.0 on pci0
Feb  1 21:17:23 freenas isa0: <ISA bus> on isab0
Feb  1 21:17:23 freenas atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1060-0x106f at device 7.1 on pci0
Feb  1 21:17:23 freenas ata0: <ATA channel> at channel 0 on atapci0
Feb  1 21:17:23 freenas ata1: <ATA channel> at channel 1 on atapci0
Feb  1 21:17:23 freenas pci0: <bridge> at device 7.3 (no driver attached)
Feb  1 21:17:23 freenas vgapci0: <VGA-compatible display> port 0x1070-0x107f mem 0xe8000000-0xefffffff,0xfe000000-0xfe7fffff irq 16 at device 15.0 on pci0
Feb  1 21:17:23 freenas vgapci0: Boot video device
Feb  1 21:17:23 freenas pcib2: <ACPI PCI-PCI bridge> at device 17.0 on pci0
Feb  1 21:17:23 freenas pci2: <ACPI PCI bus> on pcib2
Feb  1 21:17:23 freenas uhci0: <UHCI (generic) USB controller> port 0x2000-0x201f irq 18 at device 0.0 on pci2
Feb  1 21:17:23 freenas usbus0 on uhci0
Feb  1 21:17:23 freenas usbus0: 12Mbps Full Speed USB v1.0
Feb  1 21:17:23 freenas ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfd5ff000-0xfd5fffff irq 16 at device 2.0 on pci2
Feb  1 21:17:23 freenas usbus1: EHCI version 1.0
Feb  1 21:17:23 freenas usbus1 on ehci0
Feb  1 21:17:23 freenas usbus1: 480Mbps High Speed USB v2.0
Feb  1 21:17:23 freenas ahci0: <AHCI SATA controller> mem 0xfd5fe000-0xfd5fefff irq 18 at device 4.0 on pci2
Feb  1 21:17:23 freenas ahci0: AHCI v1.30 with 30 6Gbps ports, Port Multiplier not supported
Feb  1 21:17:23 freenas ahcich0: <AHCI channel> at channel 0 on ahci0
Feb  1 21:17:23 freenas ahcich1: <AHCI channel> at channel 1 on ahci0
Feb  1 21:17:23 freenas ahcich2: <AHCI channel> at channel 2 on ahci0
Feb  1 21:17:23 freenas ahcich3: <AHCI channel> at channel 3 on ahci0
Feb  1 21:17:23 freenas ahcich4: <AHCI channel> at channel 4 on ahci0
Feb  1 21:17:23 freenas ahcich5: <AHCI channel> at channel 5 on ahci0
Feb  1 21:17:23 freenas ahcich6: <AHCI channel> at channel 6 on ahci0
Feb  1 21:17:23 freenas ahcich7: <AHCI channel> at channel 7 on ahci0
Feb  1 21:17:23 freenas ahcich8: <AHCI channel> at channel 8 on ahci0
Feb  1 21:17:23 freenas ahcich9: <AHCI channel> at channel 9 on ahci0
Feb  1 21:17:23 freenas ahcich10: <AHCI channel> at channel 10 on ahci0
Feb  1 21:17:23 freenas ahcich11: <AHCI channel> at channel 11 on ahci0
Feb  1 21:17:23 freenas ahcich12: <AHCI channel> at channel 12 on ahci0
Feb  1 21:17:23 freenas ahcich13: <AHCI channel> at channel 13 on ahci0
Feb  1 21:17:23 freenas ahcich14: <AHCI channel> at channel 14 on ahci0
Feb  1 21:17:23 freenas ahcich15: <AHCI channel> at channel 15 on ahci0
Feb  1 21:17:23 freenas ahcich16: <AHCI channel> at channel 16 on ahci0
Feb  1 21:17:23 freenas ahcich17: <AHCI channel> at channel 17 on ahci0
Feb  1 21:17:23 freenas ahcich18: <AHCI channel> at channel 18 on ahci0
Feb  1 21:17:23 freenas ahcich19: <AHCI channel> at channel 19 on ahci0
Feb  1 21:17:23 freenas ahcich20: <AHCI channel> at channel 20 on ahci0
Feb  1 21:17:23 freenas ahcich21: <AHCI channel> at channel 21 on ahci0
Feb  1 21:17:23 freenas ahcich22: <AHCI channel> at channel 22 on ahci0
Feb  1 21:17:23 freenas ahcich23: <AHCI channel> at channel 23 on ahci0
Feb  1 21:17:23 freenas ahcich24: <AHCI channel> at channel 24 on ahci0
Feb  1 21:17:23 freenas ahcich25: <AHCI channel> at channel 25 on ahci0
Feb  1 21:17:23 freenas ahcich26: <AHCI channel> at channel 26 on ahci0
Feb  1 21:17:23 freenas ahcich27: <AHCI channel> at channel 27 on ahci0
Feb  1 21:17:23 freenas ahcich28: <AHCI channel> at channel 28 on ahci0
Feb  1 21:17:23 freenas ahcich29: <AHCI channel> at channel 29 on ahci0
Feb  1 21:17:23 freenas pcib3: <ACPI PCI-PCI bridge> at device 21.0 on pci0
Feb  1 21:17:23 freenas pcib3: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pci3: <ACPI PCI bus> on pcib3
Feb  1 21:17:23 freenas mpt0: <LSILogic SAS/SATA Adapter> port 0x4000-0x40ff mem 0xfd4ec000-0xfd4effff,0xfd4f0000-0xfd4fffff irq 18 at device 0.0 on pci3
Feb  1 21:17:23 freenas mpt0: MPI Version=1.5.0.0
Feb  1 21:17:23 freenas pcib4: <ACPI PCI-PCI bridge> at device 21.1 on pci0
Feb  1 21:17:23 freenas pcib4: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib5: <ACPI PCI-PCI bridge> at device 21.2 on pci0
Feb  1 21:17:23 freenas pcib5: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib6: <ACPI PCI-PCI bridge> at device 21.3 on pci0
Feb  1 21:17:23 freenas pcib6: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib7: <ACPI PCI-PCI bridge> at device 21.4 on pci0
Feb  1 21:17:23 freenas pcib7: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib8: <ACPI PCI-PCI bridge> at device 21.5 on pci0
Feb  1 21:17:23 freenas pcib8: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib9: <ACPI PCI-PCI bridge> at device 21.6 on pci0
Feb  1 21:17:23 freenas pcib9: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib10: <ACPI PCI-PCI bridge> at device 21.7 on pci0
Feb  1 21:17:23 freenas pcib10: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib11: <ACPI PCI-PCI bridge> at device 22.0 on pci0
Feb  1 21:17:23 freenas pcib11: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pci4: <ACPI PCI bus> on pcib11
Feb  1 21:17:23 freenas vmx0: <VMware VMXNET3 Ethernet Adapter> port 0x5000-0x500f mem 0xfd3fc000-0xfd3fcfff,0xfd3fd000-0xfd3fdfff,0xfd3fe000-0xfd3fffff irq 19 at device 0.0 on pci4
Feb  1 21:17:23 freenas vmx0: Ethernet address: 00:0c:29:bf:a4:4f
Feb  1 21:17:23 freenas pcib12: <ACPI PCI-PCI bridge> at device 22.1 on pci0
Feb  1 21:17:23 freenas pcib12: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib13: <ACPI PCI-PCI bridge> at device 22.2 on pci0
Feb  1 21:17:23 freenas pcib13: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib14: <ACPI PCI-PCI bridge> at device 22.3 on pci0
Feb  1 21:17:23 freenas pcib14: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib15: <ACPI PCI-PCI bridge> at device 22.4 on pci0
Feb  1 21:17:23 freenas pcib15: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib16: <ACPI PCI-PCI bridge> at device 22.5 on pci0
Feb  1 21:17:23 freenas pcib16: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib17: <ACPI PCI-PCI bridge> at device 22.6 on pci0
Feb  1 21:17:23 freenas pcib17: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib18: <ACPI PCI-PCI bridge> at device 22.7 on pci0
Feb  1 21:17:23 freenas pcib18: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib19: <ACPI PCI-PCI bridge> at device 23.0 on pci0
Feb  1 21:17:23 freenas pcib19: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pci5: <ACPI PCI bus> on pcib19
Feb  1 21:17:23 freenas mps0: <Avago Technologies (LSI) SAS2008> port 0x6000-0x60ff mem 0xfd2f0000-0xfd2fffff,0xfd280000-0xfd2bffff irq 16 at device 0.0 on pci5
Feb  1 21:17:23 freenas mps0: Firmware: 20.00.07.00, Driver: 21.02.00.00-fbsd
Feb  1 21:17:23 freenas mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
Feb  1 21:17:23 freenas pcib20: <ACPI PCI-PCI bridge> at device 23.1 on pci0
Feb  1 21:17:23 freenas pcib20: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib21: <ACPI PCI-PCI bridge> at device 23.2 on pci0
Feb  1 21:17:23 freenas pcib21: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib22: <ACPI PCI-PCI bridge> at device 23.3 on pci0
Feb  1 21:17:23 freenas pcib22: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib23: <ACPI PCI-PCI bridge> at device 23.4 on pci0
Feb  1 21:17:23 freenas pcib23: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib24: <ACPI PCI-PCI bridge> at device 23.5 on pci0
Feb  1 21:17:23 freenas pcib24: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib25: <ACPI PCI-PCI bridge> at device 23.6 on pci0
Feb  1 21:17:23 freenas pcib25: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib26: <ACPI PCI-PCI bridge> at device 23.7 on pci0
Feb  1 21:17:23 freenas pcib26: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib27: <ACPI PCI-PCI bridge> at device 24.0 on pci0
Feb  1 21:17:23 freenas pcib27: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pci6: <ACPI PCI bus> on pcib27
Feb  1 21:17:23 freenas mps1: <Avago Technologies (LSI) SAS2008> port 0x7000-0x70ff mem 0xfd1fc000-0xfd1fffff,0xfd180000-0xfd1bffff irq 17 at device 0.0 on pci6
Feb  1 21:17:23 freenas mps1: Firmware: 20.00.07.00, Driver: 21.02.00.00-fbsd
Feb  1 21:17:23 freenas mps1: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
Feb  1 21:17:23 freenas pcib28: <ACPI PCI-PCI bridge> at device 24.1 on pci0
Feb  1 21:17:23 freenas pcib28: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib29: <ACPI PCI-PCI bridge> at device 24.2 on pci0
Feb  1 21:17:23 freenas pcib29: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib30: <ACPI PCI-PCI bridge> at device 24.3 on pci0
Feb  1 21:17:23 freenas pcib30: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib31: <ACPI PCI-PCI bridge> at device 24.4 on pci0
Feb  1 21:17:23 freenas pcib31: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib32: <ACPI PCI-PCI bridge> at device 24.5 on pci0
Feb  1 21:17:23 freenas pcib32: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib33: <ACPI PCI-PCI bridge> at device 24.6 on pci0
Feb  1 21:17:23 freenas pcib33: [GIANT-LOCKED]
Feb  1 21:17:23 freenas pcib34: <ACPI PCI-PCI bridge> at device 24.7 on pci0
Feb  1 21:17:23 freenas pcib34: [GIANT-LOCKED]
Feb  1 21:17:23 freenas acpi_acad0: <AC Adapter> on acpi0
Feb  1 21:17:23 freenas atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
Feb  1 21:17:23 freenas atkbd0: <AT Keyboard> irq 1 on atkbdc0
Feb  1 21:17:23 freenas kbd0 at atkbd0
Feb  1 21:17:23 freenas atkbd0: [GIANT-LOCKED]
Feb  1 21:17:23 freenas psm0: <PS/2 Mouse> irq 12 on atkbdc0
Feb  1 21:17:23 freenas psm0: [GIANT-LOCKED]
Feb  1 21:17:23 freenas psm0: model IntelliMouse, device ID 3
Feb  1 21:17:23 freenas acpi_syscontainer0: <System Container> on acpi0
Feb  1 21:17:23 freenas orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc9fff,0xca000-0xcafff,0xdc000-0xdffff,0xe0000-0xe7fff on isa0
Feb  1 21:17:23 freenas ZFS filesystem version: 5
Feb  1 21:17:23 freenas ZFS storage pool version: features support (5000)
Feb  1 21:17:23 freenas Timecounters tick every 10.000 msec
Feb  1 21:17:23 freenas freenas_sysctl: adding account.
Feb  1 21:17:23 freenas freenas_sysctl: adding directoryservice.
Feb  1 21:17:23 freenas freenas_sysctl: adding middlewared.
Feb  1 21:17:23 freenas freenas_sysctl: adding network.
Feb  1 21:17:23 freenas freenas_sysctl: adding services.
Feb  1 21:17:23 freenas ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Feb  1 21:17:23 freenas ugen0.1: <0x15ad UHCI root HUB> at usbus0
Feb  1 21:17:23 freenas ugen1.1: <0x15ad EHCI root HUB> at usbus1
Feb  1 21:17:23 freenas uhub0: <0x15ad UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
Feb  1 21:17:23 freenas uhub1: <0x15ad EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Feb  1 21:17:23 freenas uhub0: 2 ports with 2 removable, self powered
Feb  1 21:17:23 freenas ugen0.2: <VMware VMware Virtual USB Mouse> at usbus0
Feb  1 21:17:23 freenas mps0: SAS Address for SATA device = c383b22f8ce8e6d8
Feb  1 21:17:23 freenas mps0: SAS Address from SATA device = c383b22f8ce8e6d8
Feb  1 21:17:23 freenas mps0: SAS Address for SATA device = d265534bfee2d291
Feb  1 21:17:23 freenas mps0: SAS Address from SATA device = d265534bfee2d291
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = 39395d306f8c5033
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = 39395d306f8c5033
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = 39395d3071805257
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = 39395d3071805257
Feb  1 21:17:23 freenas mps0: SAS Address for SATA device = d265634bfebac090
Feb  1 21:17:23 freenas mps0: SAS Address from SATA device = d265634bfebac090
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = d55f472cd0ad8f75
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = d55f472cd0ad8f75
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = 39395d30706b5757
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = 39395d30706b5757
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = 495e4e5bf5d9c997
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = 495e4e5bf5d9c997
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = 495d3a48d7bfb271
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = 495d3a48d7bfb271
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = d548450dd1ab8a6f
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = d548450dd1ab8a6f
Feb  1 21:17:23 freenas mps1: SAS Address for SATA device = d53d4428d1ab8b85
Feb  1 21:17:23 freenas ugen0.3: <vendor 0x0e0f VMware Virtual USB Hub> at usbus0
Feb  1 21:17:23 freenas mps1: SAS Address from SATA device = d53d4428d1ab8b85
Feb  1 21:17:23 freenas uhub2 on uhub0
Feb  1 21:17:23 freenas uhub2: <VMware Virtual USB Hub> on usbus0
Feb  1 21:17:23 freenas uhub1: 6 ports with 6 removable, self powered
Feb  1 21:17:23 freenas uhub2: 7 ports with 7 removable, self powered
Feb  1 21:17:23 freenas mps0: SAS Address for SATA device = 382f62308c864545
Feb  1 21:17:23 freenas mps0: SAS Address from SATA device = 382f62308c864545
Feb  1 21:17:23 freenas ada0 at ahcich1 bus 0 scbus3 target 0 lun 0
Feb  1 21:17:23 freenas ada0: <VMware Virtual SATA Hard Drive 00000001> ATA-6 SATA 2.x device
Feb  1 21:17:23 freenas ada0: Serial Number 01000000000000000001
Feb  1 21:17:23 freenas ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
Feb  1 21:17:23 freenas ada0: Command Queueing enabled
Feb  1 21:17:23 freenas ada0: 16384MB (33554432 512 byte sectors)
Feb  1 21:17:23 freenas da0 at mps0 bus 0 scbus33 target 9 lun 0
Feb  1 21:17:23 freenas da0: <ATA Corsair Force LE B1.1> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da0: Serial Number 18198168000125910107
Feb  1 21:17:23 freenas da0: 600.000MB/s transfers
Feb  1 21:17:23 freenas da0: Command Queueing enabled
Feb  1 21:17:23 freenas da0: 114473MB (234441648 512 byte sectors)
Feb  1 21:17:23 freenas da2 at mps0 bus 0 scbus33 target 11 lun 0
Feb  1 21:17:23 freenas da2: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da1 at mps0 bus 0 scbus33 target 10 lun 0
Feb  1 21:17:23 freenas da2: Serial Number WD-WCC4N3SHV29S
Feb  1 21:17:23 freenas da2: 600.000MB/s transfers
Feb  1 21:17:23 freenas da2: Command Queueing enabled
Feb  1 21:17:23 freenas da2: 2861588MB (5860533168 512 byte sectors)
Feb  1 21:17:23 freenas da2: quirks=0x8<4K>
Feb  1 21:17:23 freenas da1: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da1: Serial Number WD-WCC4N3CHVZKT
Feb  1 21:17:23 freenas da1: 600.000MB/s transfers
Feb  1 21:17:23 freenas da1: Command Queueing enabled
Feb  1 21:17:23 freenas da1: 2861588MB (5860533168 512 byte sectors)
Feb  1 21:17:23 freenas da1: quirks=0x8<4K>
Feb  1 21:17:23 freenas da8 at mps1 bus 0 scbus34 target 9 lun 0
Feb  1 21:17:23 freenas da9 at mps1 bus 0 scbus34 target 10 lun 0
Feb  1 21:17:23 freenas da8: da9: <ATA WDC WD40EZRX-00S 0A80> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da9: Serial Number WD-WCC4E1174874
Feb  1 21:17:23 freenas da9: 600.000MB/s transfers
Feb  1 21:17:23 freenas da9: Command Queueing enabled
Feb  1 21:17:23 freenas da9: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas syslog-ng[1996]: Error processing log message: <ATA WDC WD40EZRX-00S 0A80> Fixed Direct Access SPC-4 SCSI device
da9: quirks=0x8<4K>
da8: Serial Number WD-WCC4E2EJRRNZ
da8: 600.000MB/s transfers
da8: Command Queueing enabled
da8: 3815447MB (7814037168 512 byte sectors)
da8: quirks=0x8<4K>
random: unblocking device.
da7 at mps1 bus 0 scbus34 target 8 lun 0
da7: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
da7: Serial Number WDH170MY
da7: 600.000MB/s transfers
da7: Command Queueing enabled
da7: 3815447MB (7814037168 512 byte sectors)
da7: quirks=0x8<4K>
da5 at mps1 bus 0 scbus34 target 6 lun 0
da5: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number WDH18EHY
da5: 600.000MB/s transfers
da5: Command Queueing enabled
da5: 3815447MB (7814037168 512 byte sectors)
da5: quirks=0x8<4K>
Trying to mount root from zfs:freenas-boot/ROOT/11.2-RELEASE-U1 []...
da3 at mps0 bus 0 scbus33 target 12 lun 0
da3: <ATA ST3000VN000-1HJ1 SC60> Fixed Direct Access SPC-4 SCSI device
da3: Serial Number W6A0SKAG
da3: 600.000MB/s transfers
da3: Command Queueing enabled
da3: 2861588MB (5860533168 512 byte sectors)
da4 at mps1 bus 0 scbus34 target 5 lun 0
da4: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
da4: Serial Number WDH16QF5
da4: 600.000MB/s transfers
da4: Command Queueing enabled
da4: 3815447MB (7814037168 512 byte sectors)
da4: quirks=0x8<4K>
da10 at mps1 bus 0 scbus34 target 11 lun 0
da10: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
da10: Serial Number Z4E1KBB8FSAA
da10: 600.000MB/s transfers
da10: Command Queueing enabled
da10: 3815447MB (7814037168 512 byte sectors)
da6 at mps1 bus 0 scbus34 target 7 lun 0
da6: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
da6: Serial Number Y6J7KYDWFSAA
da6: 600.000MB/s transfers
da6: Command Queueing enabled
da6: 3815447MB (7814037168 512 byte sectors)
da11 at mps1 bus 0 scbus34 target 12 lun 0
da11: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
da11: Serial Number Z4EGK7ASFSBA
d
Feb  1 21:17:23 freenas da9: quirks=0x8<4K>
Feb  1 21:17:23 freenas da8: Serial Number WD-WCC4E2EJRRNZ
Feb  1 21:17:23 freenas da8: 600.000MB/s transfers
Feb  1 21:17:23 freenas da8: Command Queueing enabled
Feb  1 21:17:23 freenas da8: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da8: quirks=0x8<4K>
Feb  1 21:17:23 freenas random: unblocking device.
Feb  1 21:17:23 freenas da7 at mps1 bus 0 scbus34 target 8 lun 0
Feb  1 21:17:23 freenas da7: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da7: Serial Number WDH170MY
Feb  1 21:17:23 freenas da7: 600.000MB/s transfers
Feb  1 21:17:23 freenas da7: Command Queueing enabled
Feb  1 21:17:23 freenas da7: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da7: quirks=0x8<4K>
Feb  1 21:17:23 freenas da5 at mps1 bus 0 scbus34 target 6 lun 0
Feb  1 21:17:23 freenas da5: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da5: Serial Number WDH18EHY
Feb  1 21:17:23 freenas da5: 600.000MB/s transfers
Feb  1 21:17:23 freenas da5: Command Queueing enabled
Feb  1 21:17:23 freenas da5: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da5: quirks=0x8<4K>
Feb  1 21:17:23 freenas Trying to mount root from zfs:freenas-boot/ROOT/11.2-RELEASE-U1 []...
Feb  1 21:17:23 freenas da3 at mps0 bus 0 scbus33 target 12 lun 0
Feb  1 21:17:23 freenas da3: <ATA ST3000VN000-1HJ1 SC60> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da3: Serial Number W6A0SKAG
Feb  1 21:17:23 freenas da3: 600.000MB/s transfers
Feb  1 21:17:23 freenas da3: Command Queueing enabled
Feb  1 21:17:23 freenas da3: 2861588MB (5860533168 512 byte sectors)
Feb  1 21:17:23 freenas da4 at mps1 bus 0 scbus34 target 5 lun 0
Feb  1 21:17:23 freenas da4: <ATA ST4000DM005-2DP1 0001> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da4: Serial Number WDH16QF5
Feb  1 21:17:23 freenas da4: 600.000MB/s transfers
Feb  1 21:17:23 freenas da4: Command Queueing enabled
Feb  1 21:17:23 freenas da4: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da4: quirks=0x8<4K>
Feb  1 21:17:23 freenas da10 at mps1 bus 0 scbus34 target 11 lun 0
Feb  1 21:17:23 freenas da10: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da10: Serial Number Z4E1KBB8FSAA
Feb  1 21:17:23 freenas da10: 600.000MB/s transfers
Feb  1 21:17:23 freenas da10: Command Queueing enabled
Feb  1 21:17:23 freenas da10: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da6 at mps1 bus 0 scbus34 target 7 lun 0
Feb  1 21:17:23 freenas da6: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da6: Serial Number Y6J7KYDWFSAA
Feb  1 21:17:23 freenas da6: 600.000MB/s transfers
Feb  1 21:17:23 freenas da6: Command Queueing enabled
Feb  1 21:17:23 freenas da6: 3815447MB (7814037168 512 byte sectors)
Feb  1 21:17:23 freenas da11 at mps1 bus 0 scbus34 target 12 lun 0
Feb  1 21:17:23 freenas da11: <ATA TOSHIBA MD04ACA4 FP2A> Fixed Direct Access SPC-4 SCSI device
Feb  1 21:17:23 freenas da11: Serial Number Z4EGK7ASFSBA
Feb  1 21:17:23 freenas da11: 600.000MB/s transfers
Feb  1 21:17:23 freenas da11: Command Queueing enabled
Feb  1 21:17:23 freenas da11: 3815447MB (7814037168 512 byte sectors)

next post more
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
The end of the messages log

Code:
Feb  1 21:17:23 freenas GEOM_MIRROR: Device mirror/swap0 launched (2/2).
Feb  1 21:17:23 freenas GEOM_MIRROR: Device mirror/swap1 launched (2/2).
Feb  1 21:17:23 freenas GEOM_MIRROR: Device mirror/swap2 launched (2/2).
Feb  1 21:17:23 freenas GEOM_MIRROR: Device mirror/swap3 launched (2/2).
Feb  1 21:17:23 freenas GEOM_MIRROR: Device mirror/swap4 launched (2/2).
Feb  1 21:17:23 freenas GEOM_ELI: Device mirror/swap0.eli created.
Feb  1 21:17:23 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb  1 21:17:23 freenas GEOM_ELI:     Crypto: hardware
Feb  1 21:17:23 freenas GEOM_ELI: Device mirror/swap1.eli created.
Feb  1 21:17:23 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb  1 21:17:23 freenas GEOM_ELI:     Crypto: hardware
Feb  1 21:17:23 freenas GEOM_ELI: Device mirror/swap2.eli created.
Feb  1 21:17:23 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb  1 21:17:23 freenas GEOM_ELI:     Crypto: hardware
Feb  1 21:17:23 freenas GEOM_ELI: Device mirror/swap3.eli created.
Feb  1 21:17:23 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb  1 21:17:23 freenas GEOM_ELI:     Crypto: hardware
Feb  1 21:17:23 freenas GEOM_ELI: Device mirror/swap4.eli created.
Feb  1 21:17:23 freenas GEOM_ELI: Encryption: AES-XTS 128
Feb  1 21:17:23 freenas GEOM_ELI:     Crypto: hardware
Feb  1 21:17:23 freenas hwpc_core: unknown PMC architecture: 1
Feb  1 21:17:23 freenas hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI>
Feb  1 21:17:23 freenas VMware memory control driver initialized
Feb  1 21:17:23 freenas kernel: vmx0: link state changed to UP
Feb  1 21:17:23 freenas kernel: vmx0: link state changed to UP
Feb  1 21:17:23 freenas uhid0 on uhub0
Feb  1 21:17:23 freenas uhid0: <VMware> on usbus0
Feb  1 21:17:23 freenas uhid1 on uhub0
Feb  1 21:17:23 freenas uhid1: <VMware> on usbus0
Feb  1 21:17:25 freenas ntpd[2469]: ntpd 4.2.8p11-a (1): Starting
Feb  1 21:17:26 freenas proftpd[2618]: 127.0.0.1 - ProFTPD 1.3.6 (stable) (built Thu Dec 20 2018 21:26:19 UTC) standalone mode STARTUP
Feb  1 21:17:31 freenas root: /etc/rc: WARNING: failed precmd routine for minio
Feb  1 21:16:57 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 21:16:57 freenas bridge0: Ethernet address: 02:df:c7:34:6e:00
Feb  1 21:16:57 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 21:16:57 freenas epair0b: Ethernet address: 02:7d:d0:00:05:0b
Feb  1 21:16:57 freenas kernel: epair0a: link state changed to UP
Feb  1 21:16:57 freenas kernel: epair0a: link state changed to UP
Feb  1 21:16:57 freenas kernel: epair0b: link state changed to UP
Feb  1 21:16:57 freenas kernel: epair0b: link state changed to UP
Feb  1 21:16:57 freenas kernel: epair0a: changing name to 'vnet0:1'
Feb  1 21:16:57 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 21:16:57 freenas kernel: bridge0: link state changed to UP
Feb  1 21:16:57 freenas kernel: bridge0: link state changed to UP
Feb  1 21:16:57 freenas kernel: vmx0: promiscuous mode enabled
Feb  1 21:16:57 freenas kernel: vnet0:1: promiscuous mode enabled
Feb  1 21:17:01 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair1a removed
Feb  1 21:17:01 freenas epair1a: Ethernet address: 02:7d:d0:00:05:0a
Feb  1 21:17:01 freenas epair1b: Ethernet address: 02:7d:d0:00:06:0b
Feb  1 21:17:01 freenas kernel: epair1a: link state changed to UP
Feb  1 21:17:01 freenas kernel: epair1a: link state changed to UP
Feb  1 21:17:01 freenas kernel: epair1b: link state changed to UP
Feb  1 21:17:01 freenas kernel: epair1b: link state changed to UP
Feb  1 21:17:01 freenas kernel: epair1a: changing name to 'vnet0:2'
Feb  1 21:17:01 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair1b removed
Feb  1 21:17:01 freenas kernel: epair1b: changing name to 'epair0b'
Feb  1 21:17:01 freenas kernel: vnet0:2: promiscuous mode enabled
Feb  1 21:17:05 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair2a removed
Feb  1 21:17:05 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair2b removed
Feb  1 21:17:05 freenas epair2a: Ethernet address: 02:7d:d0:00:06:0a
Feb  1 21:17:05 freenas epair2b: Ethernet address: 02:7d:d0:00:07:0b
Feb  1 21:17:05 freenas kernel: epair2a: link state changed to UP
Feb  1 21:17:05 freenas kernel: epair2a: link state changed to UP
Feb  1 21:17:05 freenas kernel: epair2b: link state changed to UP
Feb  1 21:17:05 freenas kernel: epair2b: link state changed to UP
Feb  1 21:17:05 freenas kernel: epair2a: changing name to 'vnet0:3'
Feb  1 21:17:05 freenas kernel: epair2b: changing name to 'epair0b'
Feb  1 21:17:05 freenas kernel: vnet0:3: promiscuous mode enabled
Feb  1 21:17:09 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair3a removed
Feb  1 21:17:09 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair3b removed
Feb  1 21:17:09 freenas epair3a: Ethernet address: 02:7d:d0:00:07:0a
Feb  1 21:17:09 freenas epair3b: Ethernet address: 02:7d:d0:00:08:0b
Feb  1 21:17:09 freenas kernel: epair3a: link state changed to UP
Feb  1 21:17:09 freenas kernel: epair3a: link state changed to UP
Feb  1 21:17:09 freenas kernel: epair3b: link state changed to UP
Feb  1 21:17:09 freenas kernel: epair3b: link state changed to UP
Feb  1 21:17:09 freenas kernel: epair3a: changing name to 'vnet0:4'
Feb  1 21:17:09 freenas kernel: epair3b: changing name to 'epair0b'
Feb  1 21:17:09 freenas kernel: vnet0:4: promiscuous mode enabled
Feb  1 21:17:13 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair4a removed
Feb  1 21:17:13 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair4b removed
Feb  1 21:17:13 freenas epair4a: Ethernet address: 02:7d:d0:00:08:0a
Feb  1 21:17:13 freenas epair4b: Ethernet address: 02:7d:d0:00:09:0b
Feb  1 21:17:13 freenas kernel: epair4a: link state changed to UP
Feb  1 21:17:13 freenas kernel: epair4a: link state changed to UP
Feb  1 21:17:13 freenas kernel: epair4b: link state changed to UP
Feb  1 21:17:13 freenas kernel: epair4b: link state changed to UP
Feb  1 21:17:13 freenas kernel: epair4a: changing name to 'vnet0:5'
Feb  1 21:17:13 freenas kernel: epair4b: changing name to 'epair0b'
Feb  1 21:17:13 freenas kernel: vnet0:5: promiscuous mode enabled
Feb  1 21:41:26 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair5a removed
Feb  1 21:41:26 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair5b removed
Feb  1 21:41:27 freenas epair5a: Ethernet address: 02:7d:d0:00:09:0a
Feb  1 21:41:27 freenas epair5b: Ethernet address: 02:7d:d0:00:0a:0b
Feb  1 21:41:27 freenas kernel: epair5a: link state changed to UP
Feb  1 21:41:27 freenas kernel: epair5a: link state changed to UP
Feb  1 21:41:27 freenas kernel: epair5b: link state changed to UP
Feb  1 21:41:27 freenas kernel: epair5b: link state changed to UP
Feb  1 21:41:27 freenas kernel: epair5a: changing name to 'vnet0:6'
Feb  1 21:41:27 freenas kernel: epair5b: changing name to 'epair0b'
Feb  1 21:41:27 freenas kernel: vnet0:6: promiscuous mode enabled
Feb  1 21:46:28 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:1 removed
Feb  1 21:46:28 freenas kernel: vnet0:1: link state changed to DOWN
Feb  1 21:46:28 freenas kernel: vnet0:1: link state changed to DOWN
Feb  1 21:46:28 freenas kernel: epair0b: link state changed to DOWN
Feb  1 21:46:28 freenas kernel: epair0b: link state changed to DOWN
Feb  1 21:46:28 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 21:46:38 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 21:46:38 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 21:46:38 freenas epair0b: Ethernet address: 02:7d:d0:00:0a:0b
Feb  1 21:46:38 freenas kernel: epair0a: link state changed to UP
Feb  1 21:46:38 freenas kernel: epair0a: link state changed to UP
Feb  1 21:46:38 freenas kernel: epair0b: link state changed to UP
Feb  1 21:46:38 freenas kernel: epair0b: link state changed to UP
Feb  1 21:46:38 freenas kernel: epair0a: changing name to 'vnet0:7'
Feb  1 21:46:38 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 21:46:38 freenas kernel: vnet0:7: promiscuous mode enabled
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas netatalk: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Feb  1 21:54:36 freenas smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Feb  1 21:54:44 freenas smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Feb  1 21:56:18 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:6 removed
Feb  1 21:56:18 freenas kernel: vnet0:6: link state changed to DOWN
Feb  1 21:56:18 freenas kernel: vnet0:6: link state changed to DOWN
Feb  1 21:56:18 freenas kernel: epair0b: link state changed to DOWN
Feb  1 21:56:18 freenas kernel: epair0b: link state changed to DOWN
Feb  1 21:56:18 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:05:43 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair5a removed
Feb  1 22:05:43 freenas epair5a: Ethernet address: 02:7d:d0:00:09:0a
Feb  1 22:05:43 freenas epair5b: Ethernet address: 02:7d:d0:00:0a:0b
Feb  1 22:05:43 freenas kernel: epair5a: link state changed to UP
Feb  1 22:05:43 freenas kernel: epair5a: link state changed to UP
Feb  1 22:05:43 freenas kernel: epair5b: link state changed to UP
Feb  1 22:05:43 freenas kernel: epair5b: link state changed to UP
Feb  1 22:05:43 freenas kernel: epair5a: changing name to 'vnet0:8'
Feb  1 22:05:43 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair5b removed
Feb  1 22:05:43 freenas kernel: epair5b: changing name to 'epair0b'
Feb  1 22:05:43 freenas kernel: vnet0:8: promiscuous mode enabled
Feb  1 22:06:56 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:8 removed
Feb  1 22:06:56 freenas kernel: vnet0:8: link state changed to DOWN
Feb  1 22:06:56 freenas kernel: vnet0:8: link state changed to DOWN
Feb  1 22:06:56 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:06:56 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:07:29 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:11:55 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:7 removed
Feb  1 22:11:55 freenas kernel: vnet0:7: link state changed to DOWN
Feb  1 22:11:55 freenas kernel: vnet0:7: link state changed to DOWN
Feb  1 22:11:55 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:11:55 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:12:03 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:13:49 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 22:13:49 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 22:13:49 freenas epair0b: Ethernet address: 02:7d:d0:00:09:0b
Feb  1 22:13:49 freenas kernel: epair0a: link state changed to UP
Feb  1 22:13:49 freenas kernel: epair0a: link state changed to UP
Feb  1 22:13:49 freenas kernel: epair0b: link state changed to UP
Feb  1 22:13:49 freenas kernel: epair0b: link state changed to UP
Feb  1 22:13:49 freenas kernel: epair0a: changing name to 'vnet0:9'
Feb  1 22:13:49 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 22:13:49 freenas kernel: vnet0:9: promiscuous mode enabled
Feb  1 22:14:53 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:9 removed
Feb  1 22:14:53 freenas kernel: vnet0:9: link state changed to DOWN
Feb  1 22:14:53 freenas kernel: vnet0:9: link state changed to DOWN
Feb  1 22:14:53 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:14:53 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:14:53 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:15:16 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 22:15:16 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 22:15:16 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 22:15:16 freenas epair0b: Ethernet address: 02:7d:d0:00:09:0b
Feb  1 22:15:16 freenas kernel: epair0a: link state changed to UP
Feb  1 22:15:16 freenas kernel: epair0a: link state changed to UP
Feb  1 22:15:16 freenas kernel: epair0b: link state changed to UP
Feb  1 22:15:16 freenas kernel: epair0b: link state changed to UP
Feb  1 22:15:16 freenas kernel: epair0a: changing name to 'vnet0:10'
Feb  1 22:15:16 freenas kernel: vnet0:10: promiscuous mode enabled
Feb  1 22:15:36 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:10 removed
Feb  1 22:15:36 freenas kernel: vnet0:10: link state changed to DOWN
Feb  1 22:15:36 freenas kernel: vnet0:10: link state changed to DOWN
Feb  1 22:15:36 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:15:36 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:15:36 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:15:51 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 22:15:51 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 22:15:51 freenas epair0b: Ethernet address: 02:7d:d0:00:09:0b
Feb  1 22:15:51 freenas kernel: epair0a: link state changed to UP
Feb  1 22:15:51 freenas kernel: epair0a: link state changed to UP
Feb  1 22:15:51 freenas kernel: epair0b: link state changed to UP
Feb  1 22:15:51 freenas kernel: epair0b: link state changed to UP
Feb  1 22:15:51 freenas kernel: epair0a: changing name to 'vnet0:11'
Feb  1 22:15:51 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 22:15:51 freenas kernel: vnet0:11: promiscuous mode enabled
Feb  1 22:16:38 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:4 removed
Feb  1 22:16:38 freenas kernel: vnet0:4: link state changed to DOWN
Feb  1 22:16:38 freenas kernel: vnet0:4: link state changed to DOWN
Feb  1 22:16:38 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:16:38 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:16:38 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:16:44 freenas rtsold[1699]: <rtsock_input_ifannounce> interface vnet0:11 removed
Feb  1 22:16:44 freenas kernel: vnet0:11: link state changed to DOWN
Feb  1 22:16:44 freenas kernel: vnet0:11: link state changed to DOWN
Feb  1 22:16:44 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:16:44 freenas kernel: epair0b: link state changed to DOWN
Feb  1 22:16:49 freenas kernel: in6_purgeaddr: err=65, destination address delete failed
Feb  1 22:16:51 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0a removed
Feb  1 22:16:51 freenas rtsold[1699]: <rtsock_input_ifannounce> interface epair0b removed
Feb  1 22:16:51 freenas epair0a: Ethernet address: 02:7d:d0:00:04:0a
Feb  1 22:16:51 freenas epair0b: Ethernet address: 02:7d:d0:00:07:0b
Feb  1 22:16:51 freenas kernel: epair0a: link state changed to UP
Feb  1 22:16:51 freenas kernel: epair0a: link state changed to UP
Feb  1 22:16:51 freenas kernel: epair0b: link state changed to UP
Feb  1 22:16:51 freenas kernel: epair0b: link state changed to UP
Feb  1 22:16:51 freenas kernel: epair0a: changing name to 'vnet0:12'
Feb  1 22:16:51 freenas kernel: vnet0:12: promiscuous mode enabled

 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Everything in your logs look like a normal boot process. Can you describe what you mean by the jails lose connection? Like can they ping stuff on your network or can stuff on your network ping the jails? Or does the service just not work? I think this has something to do with your virtualization of freenas.
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
there are several problems...
For instance Plex, after 1 hour (more or less....) of no connected devices to plex it looses network, when i try to ping in the jail it does not work.
After going to plex on a device it takes 2 minutes and then it finds the server, if i then ping in the jail, it works all fine
Sometimes i can ping but the gui is not reachable or...for plex, sometimes it also does not find the server in the plex app.
Different in NZBget i can ping, but web gui is not reachable, but sometimes there is no possibility to ping any address in my home network nor the outsite network (read internet).
So the thing is it is really unclear.... sometimes... i just stop jails that don't work, i make a new jail and then start it, after running the new jail and ping google.com i stop the new jail and start the jail that did not work... and... yes it works... but after every reboot doing this for 6 jails is a lot of work...

I am really thinking about to try to make new warden jails i think i can still do it with warden in the shell.

Also tried to install Docker, but i don't know what to do next... it worked well on coral (i know everybody hated it and it had a lot of bugs but most things i do with freenas just worked only took a lot of time to get used to the cli and when i was mastering cli coral died), i did not had enough time to dig in the new docker thing in 11.2

To be clear in freenas i can alsways ping, and i can always acces the GUI, smb, ftp, afp, SSH etc.
i can easliy ping outside... and yes in 11.2 i had warden jails to but i changed them for iocage one by one and... yes this was stupid.... never change something that is working.....
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
Like can they ping stuff on your network or can stuff on your network ping the jails? Or does the service just not work? I think this has something to do with your virtualization of freenas.
1) I can ping my the working jails on my network from the jail other devices and from other devices the jails
2) Not working jails, sometimes i can ping (two ways)
3) New jails ALWAYS work until reboot freenas or restart jail

Te be clear.... it is a lottery which jails runs works correct a reboot and which don't... it is not always the same jails that are not working.
Also... even plugins sometimes don't work so it does. not matter if i setup the jail myself or if it is a plugin

For instance now NZBget, couchpotato, miniDLNA does not work, Plex, Transmission and test jail work
Last week all worked, boot before that Plex and Transmission did not work the rest did...
 

ajschot

Patron
Joined
Nov 7, 2016
Messages
341
Found something interessting...
I triggered NZBget by putting a nzb file into the nzb path, if the service work, it should pick up the file and start to work on it....
It did.... and yes the web gui woke up too. So if i can ping it is working but there seem to be a firewall that blocks when a jail is long time in idle like it is sometimes in plex, after giving it a push from a sideway it opens up the port of the webgui...
Maybe that is just the problem... now i have to test with couchpotato but i vcan not thing about something... also miniDLNA but that is adding a a cd or something to the media folder should trigger that....
So maybe only the webgui is blocked, but why is this since using iocage?
 
Top