From carlopmart at gmail.com Thu Dec 1 08:35:16 2016 From: carlopmart at gmail.com (C. L. Martinez) Date: Thu, 1 Dec 2016 08:35:16 +0000 Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? Message-ID: <20161201083516.GC3723@scotland.uxdom.org> Hi all, I need a new NAS for my home :)) .. Due to old hardware supplied on HP Microserver Gen8 (and it doesn't seems that HP release another model soon), I would like to know if exists some alternative with similar features: low noise, compact, etc. Exists? Many thanks. -- Greetings, C. L. Martinez From lotheac at iki.fi Thu Dec 1 09:15:09 2016 From: lotheac at iki.fi (Lauri Tirkkonen) Date: Thu, 1 Dec 2016 11:15:09 +0200 Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? In-Reply-To: <20161201083516.GC3723@scotland.uxdom.org> References: <20161201083516.GC3723@scotland.uxdom.org> Message-ID: <20161201091509.GB8402@kekkonen.niksula.hut.fi> On Thu, Dec 01 2016 08:35:16 +0000, C. L. Martinez wrote: > I need a new NAS for my home :)) .. Due to old hardware supplied on HP Microserver Gen8 (and it doesn't seems that HP release another model soon), I would like to know if exists some alternative with similar features: low noise, compact, etc. I use this with a small mini-ITX case that fits six 3.5" disks: https://www.supermicro.com/products/motherboard/Atom/X10/A1SAi-2550F.cfm -- Lauri Tirkkonen | lotheac @ IRCnet From glush at jet.msk.su Thu Dec 1 10:48:07 2016 From: glush at jet.msk.su (=?utf-8?B?0JTQvNC40YLRgNC40Lkg0JPQu9GD0YjQtdC90L7Qug==?=) Date: Thu, 1 Dec 2016 13:48:07 +0300 Subject: [OmniOS-discuss] Host is not being rebooted if it uses ZFS over iSCSI In-Reply-To: <8ADA4920-626E-4313-97A3-B933E96E70CD@cos.ru> References: <20161130150522.43BE25A0044@apps1.cs.toronto.edu> <326FA912-A3C6-4CC0-8D1A-D62DE81395E0@jet.msk.su> <8ADA4920-626E-4313-97A3-B933E96E70CD@cos.ru> Message-ID: <8424C202-4829-495A-9072-0FC8C7DB865F@jet.msk.su> Thanks for the scripts, but I would like to avoid hardcoding pool names anywhere. Due to specific roles of my ZFS servers it is possible to export all zpools at iSCSI stop and import all visible pools at iSCSI start. So, I end up with following modifications: /lib/svc/method/iscsi-initiator: at start: sleep 5 zpool import -a at stop: zpools=$(zpool list | awk '!/^rpool / && !/^NAME / {print $1}') if [ -z $zpools ]; then echo "No ZFS pools to export" return $rc fi for pool in $zpools; do echo "Exporting pool $pool" zpool export $pool echo "Done, rc=$?" done For zpool command to work from SMF service I've also removed privilege restrictions: svccfg -s iscsi/initiator delprop start/privileges svccfg -s iscsi/initiator delprop stop/privileges svcadm refresh iscsi/initiator:default > 30 ????. 2016 ?., ? 22:47, Jim Klimov ???????(?): > > 30 ?????? 2016 ?. 17:45:53 CET, "??????? ????????" ?????: >> The 'reboot' works, but it kills all processes at once (including >> iscsid), leaving no chances for ZFS to flush write cache. And I suspect >> that with current iscsi/initiator SMF service implementation the same >> happens (but for some reason sync(), which is being called by 'reboot' >> after killing all processes, is not hangs). >> >>> 30 ????. 2016 ?., ? 18:05, Chris Siebenmann >> ???????(?): >>> >>>> Does anybody uses ZFS over iSCSI? >>>> >>>> There is problem with reboots as iscsi-initiator service does not >>>> taking care of ZFS while shutting down. It leads to zpool goes into >>>> UNAVAIL state and then first sync() issued gets blocked with >> following >>>> stack: >>> >>> We have a significant ZFS-over-iSCSI fileserver environment and >>> haven't seen this, but we may be shutting our systems down in a >>> different way than you are. >>> >>> We're on OmniOS r151014 and we haven't seen this behavior when we >>> reboot or shut down our systems via 'reboot' or 'poweroff'. For us it >>> seems to go the other way around; running 'reboot' won't completely >> shut >>> down the iSCSI initiator before the machine reboots, apparently >> because >>> it's being held busy by our active ZFS pools. >>> >>> It may be relevant that we're using OmniOS multipathing across two >>> IPs for each target (configured statically); this might change the >>> device stack inside the kernel. >>> >>> I don't think we've ever tried 'shutdown' itself on a live production >>> system, so I don't know how that would work. >>> >>> - cks >> >> -- >> Dmitry Glushenok >> Jet Infosystems >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss > > Shameless plug: did you try an approach like https://github.com/jimklimov/illumos-smf-zfspools to define an SMF dependency between a pool whose vdevs reside on an iscsi initiator, or an iscsi target residing on a pool, and perhaps other services like zones to depend on the non-rpool zfs pool (SMFized)? > > At least for the case of well ordered and synced graceful shutdowns and startups, this should help you. > > HTH, Jim Klimov > -- > Typos courtesy of K-9 Mail on my Samsung Android -- Dmitry Glushenok Jet Infosystems -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.barfield at bissinc.com Thu Dec 1 14:50:44 2016 From: john.barfield at bissinc.com (John Barfield) Date: Thu, 1 Dec 2016 14:50:44 +0000 Subject: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x In-Reply-To: References: <13E9878C-23F7-4A66-8344-32A46E051E29@omniti.com> <9D220EB5-9DA3-4F01-8802-ED4ACA98FBED@bissinc.com> <8730ACC7-BDAE-4590-AA33-DEB58E3EE157@omniti.com> <60406939-051E-49CD-B292-0C6DAE9B94BB@bissinc.com> <648473C8-17C1-42C0-A54E-4F8CC8038473@omniti.com> <46F191E9-9810-4377-96F8-37109093C136@bissinc.com> Message-ID: <0AF8600C-4188-454E-BB75-B2F40EFBCAB5@bissinc.com> Well, I still cannot make a backup of my BE. For now the system works. I think I?ll just have to do a fresh install and reimport my storage pool when I really need to upgrade. On 11/29/16, 7:30 PM, "Dan McDonald" wrote: You may need to construct your menu.lst yourself, then. Here's a few sample entries. Note the up-front globals (like default entry), followed by specific entries. HOPEFULLY that's all you have to do. Otherwise, you may need to re-run installgrub(1M). Dan =============== # default menu entry to boot default 1 # # menu timeout in second before default OS is booted # set to -1 to wait for user input timeout 30 # # To enable grub serial console to ttya uncomment the following lines # and comment out the splashimage line below # WARNING: do not enable grub serial console when BIOS console serial # redirection is active. # serial --unit=0 --speed=9600 # terminal serial # # Uncomment the following line to enable GRUB splashimage on console splashimage /boot/grub/splash.xpm.gz foreground F7FBFF background 333333 # # To chainload another OS # # title Another OS # root (hd,) # chainloader +1 # # To chainload a Solaris release not based on GRUB: # # title Solaris 9 # root (hd,) # chainloader +1 # makeactive # # To load a Solaris instance based on GRUB: # # title Solaris # bootfs /ROOT/ # kernel /platform/i86pc/kernel/amd64/unix # module /platform/i86pc/amd64/boot_archive # # To override Solaris boot args (see kernel(1M)), console device and # properties set via eeprom(1M) edit the "kernel" line to: # # kernel /platform/i86pc/kernel/amd64/unix -B prop=value,... # # # title r151021-bootstrap bootfs rpool/ROOT/r151021-bootstrap kernel$ /platform/i86pc/kernel/amd64/unix -B $ZFS-BOOTFS module$ /platform/i86pc/amd64/boot_archive #============ End of LIBBE entry ============= title r151021-bootstrap-backup-1 bootfs rpool/ROOT/r151021-bootstrap-backup-1 kernel$ /platform/i86pc/kernel/amd64/unix -B $ZFS-BOOTFS module$ /platform/i86pc/amd64/boot_archive #============ End of LIBBE entry ============= From jcoombs at staff.gwi.net Thu Dec 1 14:58:57 2016 From: jcoombs at staff.gwi.net (Josh Coombs) Date: Thu, 1 Dec 2016 09:58:57 -0500 Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? In-Reply-To: <20161201083516.GC3723@scotland.uxdom.org> References: <20161201083516.GC3723@scotland.uxdom.org> Message-ID: I've just started looking into this myself. Seems the common alternatives are the Dell T20 (on cybermonday blow out this week) and Lenovo T130. Both have support for ECC RAM and four 3.5" drives, but not via externally accessible bays like the HP unfortunately. IX Systems has the FreeNAS Mini which looks slick, but doesn't have an appealing price tag. (Got this suggestion from the #illumos channel.) Supermicro has https://www.supermicro.com/products/system/midtower/5028/SYS-5028A-TN4.cfm which looks to have potential as a direct competitor to the microserver, utilizing the mobo Lauri mentioned. Supermicro has a bunch of builds based around that chassis depending on how much grunt you want, all SATA based though. Josh C Joshua Coombs GWI *office* 207-494-2140 www.gwi.net On Thu, Dec 1, 2016 at 3:35 AM, C. L. Martinez wrote: > Hi all, > > I need a new NAS for my home :)) .. Due to old hardware supplied on HP > Microserver Gen8 (and it doesn't seems that HP release another model soon), > I would like to know if exists some alternative with similar features: low > noise, compact, etc. > > Exists? > > Many thanks. > > -- > Greetings, > C. L. Martinez > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bfriesen at simple.dallas.tx.us Fri Dec 2 03:27:33 2016 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Thu, 1 Dec 2016 21:27:33 -0600 (CST) Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? In-Reply-To: References: <20161201083516.GC3723@scotland.uxdom.org> Message-ID: On Thu, 1 Dec 2016, Josh Coombs wrote: > > Supermicro has > https://www.supermicro.com/products/system/midtower/5028/SYS-5028A-TN4.cfm > which looks to have potential as a direct competitor to the microserver, > utilizing the mobo Lauri mentioned. Supermicro has a bunch of builds based > around that chassis depending on how much grunt you want, all SATA based > though. The Xeon-D version at https://www.supermicro.com/products/system/midtower/5028/SYS-5028D-TN4T.cfm has a lot more capability than the Atom-based model. If you are willing to have one boot drive, then you could use the M.2 slot to add a M.2-based SSD for excellent performance and retaining four drive slots for server disks. It also says that it has 2x 2.5" internal drive bays so you could have SATA 6 drives in all, plus the M.2-based SSD. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From geoffn at gnaa.net Fri Dec 2 05:13:38 2016 From: geoffn at gnaa.net (Geoff Nordli) Date: Thu, 1 Dec 2016 21:13:38 -0800 Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? In-Reply-To: <20161201083516.GC3723@scotland.uxdom.org> References: <20161201083516.GC3723@scotland.uxdom.org> Message-ID: <5fcf0ceb-1ba1-1b5c-7620-80eb5ed5eebb@gnaa.net> On 2016-12-01 12:35 AM, C. L. Martinez wrote: > Hi all, > > I need a new NAS for my home :)) .. Due to old hardware supplied on HP Microserver Gen8 (and it doesn't seems that HP release another model soon), I would like to know if exists some alternative with similar features: low noise, compact, etc. > > Exists? > > Many thanks. My last configuration for a smaller nas used this case: http://www.silverstonetek.com/product.php?pid=452 with an asrock mobo. http://www.asrockrack.com/general/productdetail.asp?Model=C2750D4I#Specifications Geoff From carlopmart at gmail.com Fri Dec 2 07:40:47 2016 From: carlopmart at gmail.com (C. L. Martinez) Date: Fri, 2 Dec 2016 07:40:47 +0000 Subject: [OmniOS-discuss] An alternative to HP Microserver Gen8? In-Reply-To: References: <20161201083516.GC3723@scotland.uxdom.org> Message-ID: <20161202074047.GA4107@scotland.uxdom.org> On Thu 1.Dec'16 at 21:27:33 -0600, Bob Friesenhahn wrote: > On Thu, 1 Dec 2016, Josh Coombs wrote: > > > > Supermicro has > > https://www.supermicro.com/products/system/midtower/5028/SYS-5028A-TN4.cfm > > which looks to have potential as a direct competitor to the microserver, > > utilizing the mobo Lauri mentioned. Supermicro has a bunch of builds based > > around that chassis depending on how much grunt you want, all SATA based > > though. > > The Xeon-D version at > https://www.supermicro.com/products/system/midtower/5028/SYS-5028D-TN4T.cfm > has a lot more capability than the Atom-based model. > > If you are willing to have one boot drive, then you could use the M.2 slot > to add a M.2-based SSD for excellent performance and retaining four drive > slots for server disks. > > It also says that it has 2x 2.5" internal drive bays so you could have SATA > 6 drives in all, plus the M.2-based SSD. > > Bob Many thanks Bob and Josh. Both, they seems a perfect replacement for microserver gen8. But what about the noise?? I will use it as a home NAS :)) -- Greetings, C. L. Martinez From natxo.asenjo at gmail.com Fri Dec 2 08:05:35 2016 From: natxo.asenjo at gmail.com (Natxo Asenjo) Date: Fri, 2 Dec 2016 09:05:35 +0100 Subject: [OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days In-Reply-To: References: <5F8422A7-850F-4008-A4AF-FC9B1A5E4136@lji.org> Message-ID: On Mon, Nov 28, 2016 at 3:51 PM, Rafael Pardinas wrote: > Perhaps you should add a network mask to avoid network inconsistencies. I > did it by just adding the IP using the CIDR notation, in your case it > should be: > > add property (name=ips,value="192.168.0.120/24") <-- or whatever your > subnet definition may be. > I added the netmask and restarted the zone. 4 days later I can still use it :-) So I guess this has fixed it. Thanks! -- regards, Natxo -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniil.landau at gmail.com Fri Dec 2 12:18:40 2016 From: daniil.landau at gmail.com (Daniil V. Landau) Date: Fri, 2 Dec 2016 15:18:40 +0300 Subject: [OmniOS-discuss] VNC access to KVM Message-ID: Hi! I have a clearly installed OmniOS r151020 and trying to setup a KVM virtual machine but can't connect to it's console using VNC client. I created a simple script to start my VM following the instructions on the OmniOS site: #!/usr/bin/bash HDD=/dev/zvol/rdsk/rpool/vmdisks/mds-system CD=/export/vm-distr/CentOS-6.7-x86_64-bin-DVD1.iso VNC=0 MEM=4096 mac1=`dladm show-vnic -po macaddress $VNIC1` mac2=`dladm show-vnic -po macaddress $VNIC2` /usr/bin/qemu-system-x86_64 \ -name "$(basename $CD)" \ -boot cd \ -enable-kvm \ -vnc 0.0.0.0:$VNC \ -smp 2 \ -m $MEM \ -no-hpet \ -localtime \ -drive file=$HDD,if=ide,index=0 \ -drive file=$CD,media=cdrom,if=ide,index=2 \ -vga std When I start it looks like the VM starts normally: # ./mds-kvm.sh.tmp Start bios (version 0.6.1.2-20110201_165504-titi) Ram Size=0xe0000000 (0x0000000020000000 high) CPU Mhz=2096 PCI: pci_bios_init_bus_rec bus = 0x0 PIIX3/PIIX4 init: elcr=00 0c PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237 PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000 PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010 region 4: 0x0000c000 <---skipped---> Booting from Hard Disk... Boot failed: not a bootable disk enter handle_18: NULL Booting from DVD/CD... 3714MB medium detected Booting from 0000:7c00 In the same time I can't connect to VM console using VNC: OS X native client hangs in loop and Real VNC Viewer client just exits. It's log says: <14> 2016-12-02T12:15:23.963Z Fingolfin vncviewer[2568]: Child: CConnection: close: [EndOfStream] The connection closed unexpectedly. What could be the reason of this problem? Daniil -------------- next part -------------- An HTML attachment was scrubbed... URL: From nshalman at omniti.com Fri Dec 2 14:45:27 2016 From: nshalman at omniti.com (Nahum Shalman) Date: Fri, 2 Dec 2016 09:45:27 -0500 Subject: [OmniOS-discuss] VNC access to KVM In-Reply-To: References: Message-ID: Have you tried Chicken of the VNC? I seem to recall people in the SmartOS community having to be particular about which VNC client worked. Since the code is pretty much the same, I think OmniOS has the same issue... -Nahum On Fri, Dec 2, 2016 at 7:18 AM, Daniil V. Landau wrote: > Hi! > > I have a clearly installed OmniOS r151020 and trying to setup a KVM > virtual machine but can't connect to it's console using VNC client. > > I created a simple script to start my VM following the instructions on the > OmniOS site: > > #!/usr/bin/bash > > HDD=/dev/zvol/rdsk/rpool/vmdisks/mds-system > > CD=/export/vm-distr/CentOS-6.7-x86_64-bin-DVD1.iso > > VNC=0 > > MEM=4096 > > > mac1=`dladm show-vnic -po macaddress $VNIC1` > > mac2=`dladm show-vnic -po macaddress $VNIC2` > > > /usr/bin/qemu-system-x86_64 \ > > -name "$(basename $CD)" \ > > -boot cd \ > > -enable-kvm \ > > -vnc 0.0.0.0:$VNC \ > > -smp 2 \ > > -m $MEM \ > > -no-hpet \ > > -localtime \ > > -drive file=$HDD,if=ide,index=0 \ > > -drive file=$CD,media=cdrom,if=ide,index=2 \ > > -vga std > > When I start it looks like the VM starts normally: > > # ./mds-kvm.sh.tmp > Start bios (version 0.6.1.2-20110201_165504-titi) > Ram Size=0xe0000000 (0x0000000020000000 high) > CPU Mhz=2096 > PCI: pci_bios_init_bus_rec bus = 0x0 > PIIX3/PIIX4 init: elcr=00 0c > PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237 > PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000 > PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010 > region 4: 0x0000c000 > > <---skipped---> > > Booting from Hard Disk... > Boot failed: not a bootable disk > > enter handle_18: > NULL > Booting from DVD/CD... > 3714MB medium detected > Booting from 0000:7c00 > > In the same time I can't connect to VM console using VNC: OS X native > client hangs in loop and Real VNC Viewer client just exits. It's log says: > > <14> 2016-12-02T12:15:23.963Z Fingolfin vncviewer[2568]: Child: > CConnection: close: [EndOfStream] The connection closed unexpectedly. > > What could be the reason of this problem? > > > Daniil > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniil.landau at gmail.com Fri Dec 2 15:25:37 2016 From: daniil.landau at gmail.com (Daniil V. Landau) Date: Fri, 2 Dec 2016 18:25:37 +0300 Subject: [OmniOS-discuss] VNC access to KVM In-Reply-To: References: Message-ID: Nahum, thank you! Chicken client resolved the problem! 2016-12-02 17:45 GMT+03:00 Nahum Shalman : > Have you tried Chicken of the VNC? > I seem to recall people in the SmartOS community having to be particular > about which VNC client worked. > Since the code is pretty much the same, I think OmniOS has the same > issue... > > -Nahum > > On Fri, Dec 2, 2016 at 7:18 AM, Daniil V. Landau > wrote: > >> Hi! >> >> I have a clearly installed OmniOS r151020 and trying to setup a KVM >> virtual machine but can't connect to it's console using VNC client. >> >> I created a simple script to start my VM following the instructions on >> the OmniOS site: >> >> #!/usr/bin/bash >> >> HDD=/dev/zvol/rdsk/rpool/vmdisks/mds-system >> >> CD=/export/vm-distr/CentOS-6.7-x86_64-bin-DVD1.iso >> >> VNC=0 >> >> MEM=4096 >> >> >> mac1=`dladm show-vnic -po macaddress $VNIC1` >> >> mac2=`dladm show-vnic -po macaddress $VNIC2` >> >> >> /usr/bin/qemu-system-x86_64 \ >> >> -name "$(basename $CD)" \ >> >> -boot cd \ >> >> -enable-kvm \ >> >> -vnc 0.0.0.0:$VNC \ >> >> -smp 2 \ >> >> -m $MEM \ >> >> -no-hpet \ >> >> -localtime \ >> >> -drive file=$HDD,if=ide,index=0 \ >> >> -drive file=$CD,media=cdrom,if=ide,index=2 \ >> >> -vga std >> >> When I start it looks like the VM starts normally: >> >> # ./mds-kvm.sh.tmp >> Start bios (version 0.6.1.2-20110201_165504-titi) >> Ram Size=0xe0000000 (0x0000000020000000 high) >> CPU Mhz=2096 >> PCI: pci_bios_init_bus_rec bus = 0x0 >> PIIX3/PIIX4 init: elcr=00 0c >> PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237 >> PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000 >> PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010 >> region 4: 0x0000c000 >> >> <---skipped---> >> >> Booting from Hard Disk... >> Boot failed: not a bootable disk >> >> enter handle_18: >> NULL >> Booting from DVD/CD... >> 3714MB medium detected >> Booting from 0000:7c00 >> >> In the same time I can't connect to VM console using VNC: OS X native >> client hangs in loop and Real VNC Viewer client just exits. It's log says: >> >> <14> 2016-12-02T12:15:23.963Z Fingolfin vncviewer[2568]: Child: >> CConnection: close: [EndOfStream] The connection closed unexpectedly. >> >> What could be the reason of this problem? >> >> >> Daniil >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at omniti.com Fri Dec 2 15:51:47 2016 From: danmcd at omniti.com (Dan McDonald) Date: Fri, 2 Dec 2016 10:51:47 -0500 Subject: [OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days In-Reply-To: References: <5F8422A7-850F-4008-A4AF-FC9B1A5E4136@lji.org> Message-ID: <09E54637-A4C5-4F2E-B272-08C634358767@omniti.com> > On Dec 2, 2016, at 3:05 AM, Natxo Asenjo wrote: > > So I guess this has fixed it. Thanks! Thanks Rafael for bringing that up. Naxto --> most network configurations need / these days. Maybe for 022 I can have the zonecfg CHECK for this? Or at least I need to document it better in lx(5). This is the sort of feedback I'm hoping for as part of 020's "LX Beta". Thanks! Dan From danmcd at omniti.com Fri Dec 2 19:26:10 2016 From: danmcd at omniti.com (Dan McDonald) Date: Fri, 2 Dec 2016 14:26:10 -0500 Subject: [OmniOS-discuss] Anyone using USB3/xhci? Message-ID: <2B74A891-5016-4C85-A93F-830ED18C1E4F@omniti.com> Are there any people in the audience using the USB3/xhci special repo? Anyone using the install media with USB3/xhci on it? Curious, Dan From cfraire at fishnet.cf Fri Dec 2 19:43:31 2016 From: cfraire at fishnet.cf (Chris Fraire) Date: Fri, 2 Dec 2016 13:43:31 -0600 Subject: [OmniOS-discuss] VNC access to KVM In-Reply-To: References: Message-ID: <40529E11-E73A-4E7C-8C48-339C345EA09A@fishnet.cf> Daniil, If you do want to use RealVNC Viewer to connect to QEMU, you have to set the Expert option "FullColor" to true. https://support.realvnc.com/knowledgebase/article/View/422/12/problems-connecting-to-vmware-qemu-xens-built-in-or-other-third-party-vnc-compatible-server-software ?CF > On Dec 2, 2016, at 09:25, Daniil V. Landau wrote: > > Nahum, thank you! > Chicken client resolved the problem! > > 2016-12-02 17:45 GMT+03:00 Nahum Shalman >: > Have you tried Chicken of the VNC? > I seem to recall people in the SmartOS community having to be particular about which VNC client worked. > Since the code is pretty much the same, I think OmniOS has the same issue... > > -Nahum > > On Fri, Dec 2, 2016 at 7:18 AM, Daniil V. Landau > wrote: > Hi! > > I have a clearly installed OmniOS r151020 and trying to setup a KVM virtual machine but can't connect to it's console using VNC client. > > I created a simple script to start my VM following the instructions on the OmniOS site: > > #!/usr/bin/bash > HDD=/dev/zvol/rdsk/rpool/vmdisks/mds-system > CD=/export/vm-distr/CentOS-6.7-x86_64-bin-DVD1.iso > VNC=0 > MEM=4096 > > mac1=`dladm show-vnic -po macaddress $VNIC1` > mac2=`dladm show-vnic -po macaddress $VNIC2` > > /usr/bin/qemu-system-x86_64 \ > -name "$(basename $CD)" \ > -boot cd \ > -enable-kvm \ > -vnc 0.0.0.0:$VNC \ > -smp 2 \ > -m $MEM \ > -no-hpet \ > -localtime \ > -drive file=$HDD,if=ide,index=0 \ > -drive file=$CD,media=cdrom,if=ide,index=2 \ > -vga std > > When I start it looks like the VM starts normally: > > # ./mds-kvm.sh.tmp > Start bios (version 0.6.1.2-20110201_165504-titi) > Ram Size=0xe0000000 (0x0000000020000000 high) > CPU Mhz=2096 > PCI: pci_bios_init_bus_rec bus = 0x0 > PIIX3/PIIX4 init: elcr=00 0c > PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237 > PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000 > PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010 > region 4: 0x0000c000 > > <---skipped---> > > Booting from Hard Disk... > Boot failed: not a bootable disk > > enter handle_18: > NULL > Booting from DVD/CD... > 3714MB medium detected > Booting from 0000:7c00 > > In the same time I can't connect to VM console using VNC: OS X native client hangs in loop and Real VNC Viewer client just exits. It's log says: > > <14> 2016-12-02T12:15:23.963Z Fingolfin vncviewer[2568]: Child: CConnection: close: [EndOfStream] The connection closed unexpectedly. > > What could be the reason of this problem? > > > Daniil > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at marzocchi.net Sun Dec 4 22:52:49 2016 From: lists at marzocchi.net (Olaf Marzocchi) Date: Sun, 4 Dec 2016 23:52:49 +0100 Subject: [OmniOS-discuss] OpenSSH and reverse DNS In-Reply-To: <20161129115056.GB229@kekkonen.niksula.hut.fi> References: <20161129113017.GA229@kekkonen.niksula.hut.fi> <20161129115056.GB229@kekkonen.niksula.hut.fi> Message-ID: <55d301ec-1c6b-1140-17fe-a8a6d592ce94@marzocchi.net> On 29/11/2016 12:50, Lauri Tirkkonen wrote: > Another interesting thing to note is that this particular log message > was changed in 7.3: > https://github.com/openssh/openssh-portable/commit/e690fe85750e93fca1fb7c7c8587d4130a4f7aba > > So it actually may be the *client* that is calling > get_canonical_hostname (which is strange, because only sshd should be > doing that). And so it is: > https://github.com/omniti-labs/omnios-build/blob/master/build/openssh/patches/0015-GSS-API-key-exchange-support.patch#L1652 > > The culprit is thus the GSSAPI patch (which I personally don't even > agree with, but oh well). I think the option you need to disable in the > client's ssh_config is GSSAPIKeyExchange. Changing that option in ssh_config solved the issue. sshd_config on both client and server are back to standard values for UseDNS and GSSAPIAuthentication but still no messages. Thanks Olaf From stephan.budach at jvm.de Mon Dec 5 12:41:33 2016 From: stephan.budach at jvm.de (Stephan Budach) Date: Mon, 5 Dec 2016 13:41:33 +0100 Subject: [OmniOS-discuss] format doesn't show all disks in the system Message-ID: Hi, I do have two r018 systems, which are equipped with three different types of disks. When I run format it doesn't show all of the connected disks and leaves out the Intel 3700 SSDs. OmniOS 5.11 omnios-r151018-ae3141d April 2016 root at nfsvmpool06:/root# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c2t4d0 /pci at 0,0/pci15d9,821 at 1f,2/disk at 4,0 1. c6t55CD2E404B42A367d0 /scsi_vhci/disk at g55cd2e404b42a367 2. c6t5000C5008ED5D24Fd0 /scsi_vhci/disk at g5000c5008ed5d24f 3. c6t5000C5008ED6CB33d0 /scsi_vhci/disk at g5000c5008ed6cb33 4. c6t5000C5008ED44FE7d0 /scsi_vhci/disk at g5000c5008ed44fe7 5. c6t50025388A06DB530d0 /scsi_vhci/disk at g50025388a06db530 6. c6t50025388A0140B43d0 /scsi_vhci/disk at g50025388a0140b43 7. c6t50025388A0140B48d0 /scsi_vhci/disk at g50025388a0140b48 Specify disk (enter its number): However, cfgadm does show the Intel SSDs? root at nfsvmpool06:/root# cfgadm -a Ap_Id Type Receptacle Occupant Condition c3 scsi-sas connected unconfigured unknown c4 scsi-sas connected unconfigured unknown c5 scsi-sas connected configured unknown c5::w55cd2e404c0f0734,0 disk-path connected configured unknown c7 scsi-sas connected configured unknown c7::w55cd2e404c0f0717,0 disk-path connected configured unknown c8 scsi-sas connected configured unknown c8::w55cd2e404c0f0722,0 disk-path connected configured unknown c9 scsi-sas connected configured unknown c9::w55cd2e404c0f06f1,0 disk-path connected configured unknown c10 scsi-sas connected configured unknown c10::w55cd2e404c0f072b,0 disk-path connected configured unknown c11 scsi-sas connected configured unknown c11::w55cd2e404c0f06ff,0 disk-path connected configured unknown c12 scsi-sas connected configured unknown c12::w55cd2e404c0f0744,0 disk-path connected configured unknown c13 scsi-sas connected configured unknown c13::w55cd2e404c0f07ce,0 disk-path connected configured unknown c15 scsi-sas connected configured unknown c15::w5000c5008ed5d24d,0 disk-path connected configured unknown c16 scsi-sas connected configured unknown c16::w5000c5008ed44fe5,0 disk-path connected configured unknown c17 scsi-sas connected configured unknown c17::w5000c5008ed6cb31,0 disk-path connected configured unknown c19 scsi-sas connected configured unknown c19::w50025388a0140b48,0 disk-path connected configured unknown c20 scsi-sas connected configured unknown c20::w50025388a06db530,0 disk-path connected configured unknown c21 scsi-sas connected configured unknown c21::w50025388a0140b43,0 disk-path connected configured unknown c22 scsi-sas connected configured unknown c22::w55cd2e404b42a367,0 disk-path connected configured unknown E.g. w50025388a06db530 is one of the Intel SSDs, what doesn't format doesn?t show. What am I missing? Thanks, Stephan From danmcd at omniti.com Mon Dec 5 15:11:29 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 5 Dec 2016 10:11:29 -0500 Subject: [OmniOS-discuss] format doesn't show all disks in the system In-Reply-To: References: Message-ID: <26BB348F-BE57-4F2D-A0CF-6A97ED4C2AD1@omniti.com> Are you attaching SATA disks to a SCSI expander? Doing so is discouraged for reliability reasons (and might explain why format(1M) is missing them). Dan From stephan.budach at jvm.de Mon Dec 5 15:22:25 2016 From: stephan.budach at jvm.de (Stephan Budach) Date: Mon, 5 Dec 2016 16:22:25 +0100 Subject: [OmniOS-discuss] format doesn't show all disks in the system In-Reply-To: <26BB348F-BE57-4F2D-A0CF-6A97ED4C2AD1@omniti.com> References: <26BB348F-BE57-4F2D-A0CF-6A97ED4C2AD1@omniti.com> Message-ID: <90ec245f-1b71-f2fa-55bb-6a08c8189a86@jvm.de> Am 05.12.16 um 16:11 schrieb Dan McDonald: > Are you attaching SATA disks to a SCSI expander? Doing so is discouraged for reliability reasons (and might explain why format(1M) is missing them). > > Dan > I don't think so. Afaik, these Supermicro systems have a backplane, which connects the drives to the two HBAs, but there's no expander involved. Also, I remember that format had shown these disks back when I installed the system and set up the iSCSI target/LUNs. If I remember correctly, all I did was to perform some partitioning on those SSDs, as I did with all drives, in that system. That setup has also been rock-solid in terms of reliability and performance, so no complaints there. Those are my work-horses for my OVM cluster and any issue regarding reliability or stability would not have gone unnoticed. ;) Thank, Stephan From daleg at omniti.com Mon Dec 5 15:29:52 2016 From: daleg at omniti.com (Dale Ghent) Date: Mon, 5 Dec 2016 10:29:52 -0500 Subject: [OmniOS-discuss] format doesn't show all disks in the system In-Reply-To: References: Message-ID: What does running: devfsadm -v tell you? It could be that you added this drive and the dev links weren't made for some reason. /dale > On Dec 5, 2016, at 7:41 AM, Stephan Budach wrote: > > Hi, > > I do have two r018 systems, which are equipped with three different types of disks. When I run format it doesn't show all of the connected disks and leaves out the Intel 3700 SSDs. > > OmniOS 5.11 omnios-r151018-ae3141d April 2016 > root at nfsvmpool06:/root# format > Searching for disks...done > > > AVAILABLE DISK SELECTIONS: > 0. c2t4d0 > /pci at 0,0/pci15d9,821 at 1f,2/disk at 4,0 > 1. c6t55CD2E404B42A367d0 > /scsi_vhci/disk at g55cd2e404b42a367 > 2. c6t5000C5008ED5D24Fd0 > /scsi_vhci/disk at g5000c5008ed5d24f > 3. c6t5000C5008ED6CB33d0 > /scsi_vhci/disk at g5000c5008ed6cb33 > 4. c6t5000C5008ED44FE7d0 > /scsi_vhci/disk at g5000c5008ed44fe7 > 5. c6t50025388A06DB530d0 > /scsi_vhci/disk at g50025388a06db530 > 6. c6t50025388A0140B43d0 > /scsi_vhci/disk at g50025388a0140b43 > 7. c6t50025388A0140B48d0 > /scsi_vhci/disk at g50025388a0140b48 > Specify disk (enter its number): > > However, cfgadm does show the Intel SSDs? > > root at nfsvmpool06:/root# cfgadm -a > Ap_Id Type Receptacle Occupant Condition > c3 scsi-sas connected unconfigured unknown > c4 scsi-sas connected unconfigured unknown > c5 scsi-sas connected configured unknown > c5::w55cd2e404c0f0734,0 disk-path connected configured unknown > c7 scsi-sas connected configured unknown > c7::w55cd2e404c0f0717,0 disk-path connected configured unknown > c8 scsi-sas connected configured unknown > c8::w55cd2e404c0f0722,0 disk-path connected configured unknown > c9 scsi-sas connected configured unknown > c9::w55cd2e404c0f06f1,0 disk-path connected configured unknown > c10 scsi-sas connected configured unknown > c10::w55cd2e404c0f072b,0 disk-path connected configured unknown > c11 scsi-sas connected configured unknown > c11::w55cd2e404c0f06ff,0 disk-path connected configured unknown > c12 scsi-sas connected configured unknown > c12::w55cd2e404c0f0744,0 disk-path connected configured unknown > c13 scsi-sas connected configured unknown > c13::w55cd2e404c0f07ce,0 disk-path connected configured unknown > c15 scsi-sas connected configured unknown > c15::w5000c5008ed5d24d,0 disk-path connected configured unknown > c16 scsi-sas connected configured unknown > c16::w5000c5008ed44fe5,0 disk-path connected configured unknown > c17 scsi-sas connected configured unknown > c17::w5000c5008ed6cb31,0 disk-path connected configured unknown > c19 scsi-sas connected configured unknown > c19::w50025388a0140b48,0 disk-path connected configured unknown > c20 scsi-sas connected configured unknown > c20::w50025388a06db530,0 disk-path connected configured unknown > c21 scsi-sas connected configured unknown > c21::w50025388a0140b43,0 disk-path connected configured unknown > c22 scsi-sas connected configured unknown > c22::w55cd2e404b42a367,0 disk-path connected configured unknown > > E.g. w50025388a06db530 is one of the Intel SSDs, what doesn't format doesn?t show. What am I missing? > > Thanks, > Stephan > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From stephan.budach at jvm.de Mon Dec 5 15:34:02 2016 From: stephan.budach at jvm.de (Stephan Budach) Date: Mon, 5 Dec 2016 16:34:02 +0100 Subject: [OmniOS-discuss] format doesn't show all disks in the system In-Reply-To: References: Message-ID: Hi Dale, Am 05.12.16 um 16:29 schrieb Dale Ghent: > What does running: > > devfsadm -v > > tell you? It could be that you added this drive and the dev links weren't made for some reason. > > /dale > >> On Dec 5, 2016, at 7:41 AM, Stephan Budach wrote: >> >> Hi, >> >> I do have two r018 systems, which are equipped with three different types of disks. When I run format it doesn't show all of the connected disks and leaves out the Intel 3700 SSDs. >> >> OmniOS 5.11 omnios-r151018-ae3141d April 2016 >> root at nfsvmpool06:/root# format >> Searching for disks...done >> >> >> AVAILABLE DISK SELECTIONS: >> 0. c2t4d0 >> /pci at 0,0/pci15d9,821 at 1f,2/disk at 4,0 >> 1. c6t55CD2E404B42A367d0 >> /scsi_vhci/disk at g55cd2e404b42a367 >> 2. c6t5000C5008ED5D24Fd0 >> /scsi_vhci/disk at g5000c5008ed5d24f >> 3. c6t5000C5008ED6CB33d0 >> /scsi_vhci/disk at g5000c5008ed6cb33 >> 4. c6t5000C5008ED44FE7d0 >> /scsi_vhci/disk at g5000c5008ed44fe7 >> 5. c6t50025388A06DB530d0 >> /scsi_vhci/disk at g50025388a06db530 >> 6. c6t50025388A0140B43d0 >> /scsi_vhci/disk at g50025388a0140b43 >> 7. c6t50025388A0140B48d0 >> /scsi_vhci/disk at g50025388a0140b48 >> Specify disk (enter its number): >> >> However, cfgadm does show the Intel SSDs? >> >> root at nfsvmpool06:/root# cfgadm -a >> Ap_Id Type Receptacle Occupant Condition >> c3 scsi-sas connected unconfigured unknown >> c4 scsi-sas connected unconfigured unknown >> c5 scsi-sas connected configured unknown >> c5::w55cd2e404c0f0734,0 disk-path connected configured unknown >> c7 scsi-sas connected configured unknown >> c7::w55cd2e404c0f0717,0 disk-path connected configured unknown >> c8 scsi-sas connected configured unknown >> c8::w55cd2e404c0f0722,0 disk-path connected configured unknown >> c9 scsi-sas connected configured unknown >> c9::w55cd2e404c0f06f1,0 disk-path connected configured unknown >> c10 scsi-sas connected configured unknown >> c10::w55cd2e404c0f072b,0 disk-path connected configured unknown >> c11 scsi-sas connected configured unknown >> c11::w55cd2e404c0f06ff,0 disk-path connected configured unknown >> c12 scsi-sas connected configured unknown >> c12::w55cd2e404c0f0744,0 disk-path connected configured unknown >> c13 scsi-sas connected configured unknown >> c13::w55cd2e404c0f07ce,0 disk-path connected configured unknown >> c15 scsi-sas connected configured unknown >> c15::w5000c5008ed5d24d,0 disk-path connected configured unknown >> c16 scsi-sas connected configured unknown >> c16::w5000c5008ed44fe5,0 disk-path connected configured unknown >> c17 scsi-sas connected configured unknown >> c17::w5000c5008ed6cb31,0 disk-path connected configured unknown >> c19 scsi-sas connected configured unknown >> c19::w50025388a0140b48,0 disk-path connected configured unknown >> c20 scsi-sas connected configured unknown >> c20::w50025388a06db530,0 disk-path connected configured unknown >> c21 scsi-sas connected configured unknown >> c21::w50025388a0140b43,0 disk-path connected configured unknown >> c22 scsi-sas connected configured unknown >> c22::w55cd2e404b42a367,0 disk-path connected configured unknown >> >> E.g. w50025388a06db530 is one of the Intel SSDs, what doesn't format doesn?t show. What am I missing? >> >> Thanks, >> Stephan >> _______________________________________________ devfsadm -v returns nothing Thanks, Stephan >> From Dirk.Willems at exitas.be Mon Dec 5 15:54:55 2016 From: Dirk.Willems at exitas.be (Willems Dirk) Date: Mon, 5 Dec 2016 15:54:55 +0000 Subject: [OmniOS-discuss] unable to add second nic on KVM In-Reply-To: <9DE482A4-ECC7-4D44-BE15-1362AE2FDCE4@omniti.com> References: <71c6fa3e-aede-2dd8-30e3-53e008c4aa58@exitas.be> <642d26ab-6da6-e94b-0a71-e71423dca908@exitas.be> <9DE482A4-ECC7-4D44-BE15-1362AE2FDCE4@omniti.com> Message-ID: <8219c894-9f83-7fd4-5e59-8d04f8458670@exitas.be> On 2016-11-28 16:40, Dan McDonald wrote: >> On Nov 25, 2016, at 7:49 AM, Willems Dirk wrote: >> >>> Hello, >>> >>> First of all Thank you for this wonderful OS. >>> >>> I'm using it for Home virtualization and have the same server also running on my Work for testing purpose and want to use it for Production servers by my clients. >>> >>> But I've a small problem. >>> I'm trying to add a second nic to the KVM image but when I start the KVM I can't connect anymore over ssh or ping the global zone and have to kill the KVM process. > I think I just reproduced this on an older OmniOS (r151014). > > I may need to consult Joyent, as they maintain the KVM code, but also have other things in their MAC/GLDv3 layer that upstream illumos doesn't, which may be interacting poorly. > > Sorry I can't help immediately, > Dan > Hello Dan, Did you already receive any news about the KVM issue by Joyent? Also a second question : Which hardware you recommend for running Omnios, I want to replace the VM env of my customer to Omnios with KVM. Also My customer can have a Enterprise support contract like we have with Oracle? I was checking out supermicro systems which seems very Lovely and Trustable. Thanks in advance. Kind Regards, Dirk From danmcd at omniti.com Mon Dec 5 15:59:05 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 5 Dec 2016 10:59:05 -0500 Subject: [OmniOS-discuss] unable to add second nic on KVM In-Reply-To: <8219c894-9f83-7fd4-5e59-8d04f8458670@exitas.be> References: <71c6fa3e-aede-2dd8-30e3-53e008c4aa58@exitas.be> <642d26ab-6da6-e94b-0a71-e71423dca908@exitas.be> <9DE482A4-ECC7-4D44-BE15-1362AE2FDCE4@omniti.com> <8219c894-9f83-7fd4-5e59-8d04f8458670@exitas.be> Message-ID: <5C24EF10-C759-4ECC-B021-A76E2A2AD6A6@omniti.com> > On Dec 5, 2016, at 10:54 AM, Willems Dirk wrote: > > Did you already receive any news about the KVM issue by Joyent? I have not. Given it's getting toward the end of the year, I'm not sure if I will, either. > Also a second question : > > Which hardware you recommend for running Omnios, I want to replace the > VM env of my customer to Omnios with KVM. See here: https://www.illumos.org/hcl/ And in general, go with Intel and SuperMicro. NOTE that USB3 isn't supported yet, so you may need to go with a pre-Skylake Intel system. > Also My customer can have a Enterprise support contract like we have > with Oracle? OmniTI offers OmniOS support, but it may not be quite what Oracle has: https://omniti.com/does/omnios > I was checking out supermicro systems which seems very Lovely and Trustable. Yes, and the archives of this mailing list have SuperMicro recommendations all over the place. Dan From danmcd at omniti.com Tue Dec 6 15:30:48 2016 From: danmcd at omniti.com (Dan McDonald) Date: Tue, 6 Dec 2016 10:30:48 -0500 Subject: [OmniOS-discuss] Increase default maximum NFS server threads? Message-ID: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> I got a link to this commit from the Delphix illumos repo a while back: https://github.com/openzfs/openzfs/pull/186/ I was curious if NFS-using people in the audience here would like to see this one Just Land (TM) in illumos-omnios or not? Dan From richard.elling at richardelling.com Tue Dec 6 15:51:06 2016 From: richard.elling at richardelling.com (Richard Elling) Date: Tue, 6 Dec 2016 07:51:06 -0800 Subject: [OmniOS-discuss] Increase default maximum NFS server threads? In-Reply-To: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> References: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> Message-ID: > On Dec 6, 2016, at 7:30 AM, Dan McDonald wrote: > > I got a link to this commit from the Delphix illumos repo a while back: > > https://github.com/openzfs/openzfs/pull/186/ > > I was curious if NFS-using people in the audience here would like to see this one Just Land (TM) in illumos-omnios or not? just land it, no real downside ? richard From ikaufman at eng.ucsd.edu Tue Dec 6 15:55:13 2016 From: ikaufman at eng.ucsd.edu (Ian Kaufman) Date: Tue, 6 Dec 2016 07:55:13 -0800 Subject: [OmniOS-discuss] Increase default maximum NFS server threads? In-Reply-To: References: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> Message-ID: I agree, and, it really has been a long time coming. Those defaults were set ages ago, systems and networking have vastly improved since then. Might as well set defaults accordingly. Ian On Tue, Dec 6, 2016 at 7:51 AM, Richard Elling < richard.elling at richardelling.com> wrote: > > > On Dec 6, 2016, at 7:30 AM, Dan McDonald wrote: > > > > I got a link to this commit from the Delphix illumos repo a while back: > > > > https://github.com/openzfs/openzfs/pull/186/ > > > > I was curious if NFS-using people in the audience here would like to see > this one Just Land (TM) in illumos-omnios or not? > > just land it, no real downside > ? richard > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -- Ian Kaufman Research Systems Administrator UC San Diego, Jacobs School of Engineering ikaufman AT ucsd DOT edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cks at cs.toronto.edu Tue Dec 6 15:58:51 2016 From: cks at cs.toronto.edu (Chris Siebenmann) Date: Tue, 06 Dec 2016 10:58:51 -0500 Subject: [OmniOS-discuss] Increase default maximum NFS server threads? In-Reply-To: Your message of Tue, 06 Dec 2016 10:30:48 -0500. <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> Message-ID: <20161206155851.1476F5A0A39@apps1.cs.toronto.edu> > I got a link to this commit from the Delphix illumos repo a while back: > > https://github.com/openzfs/openzfs/pull/186/ > > I was curious if NFS-using people in the audience here would like to > see this one Just Land (TM) in illumos-omnios or not? I think that modernizing these NFS server parameters is a good thing, especially when the old values date from decades ago. I assume that the Delphix people have done their homework and testing on what the new values should be, so I don't see any reason not to take this as-is unless people have some burning desire to (re)do their own testing. - cks From danmcd at omniti.com Tue Dec 6 16:01:47 2016 From: danmcd at omniti.com (Dan McDonald) Date: Tue, 6 Dec 2016 11:01:47 -0500 Subject: [OmniOS-discuss] Increase default maximum NFS server threads? In-Reply-To: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> References: <3436A5C9-F0D6-430F-B7D0-3B0BA64717A3@omniti.com> Message-ID: Three enthusiastic answers within 30 mins tells me this is a Good Idea (TM). Unless I can convince upstream to have that land there, I'll land this in master before COB today. As for backports... well, I think 014 will get one more big illumos-omnios refresh before 022 ships, so I'll need to make sure this guy land in there as well. Thanks! Dan From peter.tribble at gmail.com Tue Dec 6 16:04:16 2016 From: peter.tribble at gmail.com (Peter Tribble) Date: Tue, 6 Dec 2016 16:04:16 +0000 Subject: [OmniOS-discuss] Zone lo interfaces out of order Message-ID: I got a bunch of errors on some of our systems yesterday, and they appear to be related to the following oddity. We have a bunch of zones running on r151014. Looking at the lo virtual interfaces assigned to two of the zones, this is what they look like for IPv4: lo0:10: flags=2001000849 mtu 8232 index 1 zone wilma inet 127.0.0.1 netmask ff000000 lo0:11: flags=2001000849 mtu 8232 index 1 zone fred inet 127.0.0.1 netmask ff000000 And this for IPv6: lo0:10: flags=2002000849 mtu 8252 index 1 zone fred inet6 ::1/128 lo0:11: flags=2002000849 mtu 8252 index 1 zone wilma inet6 ::1/128 Notice that lo:10 and lo:11 have been swapped over. The IPv4 version of lo:10 is assigned to wilma, but the IPv6 version is assigned to fred. And vice versa with lo:11. This is what it looks like in one of the zones: lo0:11: flags=2001000849 mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 lo0:10: flags=2002000849 mtu 8252 index 1 inet6 ::1/128 This doesn't look quite right to me, and it's not something I've ever seen before. This begs some questions: Is there a real problem here? Is it just us? (I've spotted it on more than one system, although it seems to be our new fast machines and not the old slow ones.) What's going to be affected? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniil.landau at gmail.com Tue Dec 6 22:39:00 2016 From: daniil.landau at gmail.com (=?utf-8?B?0JTQsNC90LjQuNC7INCb0LDQvdC00LDRgw==?=) Date: Wed, 7 Dec 2016 01:39:00 +0300 Subject: [OmniOS-discuss] unable to add second nic on KVM Message-ID: <166CB11C-4DE9-4B6D-BC2C-4FE7BBAD3493@gmail.com> I had a very similar problem a couple of days ago. I solved it by using unique vlan numbers for each nic/vnic pair in the qemu arguments, i.e.: /usr/bin/qemu-system-x86_64 \ -name "$(basename $NAME)" \ -boot cd \ -enable-kvm \ -vnc 0.0.0.0:$VNC \ -smp 2 \ -m $MEM \ -no-hpet \ -localtime \ -drive file=$HDD,if=ide,index=0 \ -drive file=$CD,media=cdrom,if=ide,index=2 \ -net nic,vlan=0,name=net0,model=e1000,macaddr=$mac1 \ -net vnic,vlan=0,name=net0,ifname=$VNIC1,macaddr=$mac1, \ -net nic,vlan=1,name=net1,model=e1000,macaddr=$mac2 \ -net vnic,vlan=1,name=net1,ifname=$VNIC2,macaddr=$mac2, \ -vga std \ -daemonize Daniil -------------- next part -------------- An HTML attachment was scrubbed... URL: From paladinemishakal at gmail.com Wed Dec 7 04:16:48 2016 From: paladinemishakal at gmail.com (Lawrence Giam) Date: Wed, 7 Dec 2016 12:16:48 +0800 Subject: [OmniOS-discuss] Large infolog_hival file In-Reply-To: References: Message-ID: Hi All, Also to note that I have another running OpenIndiana 151a7 and this is also a SuperMicro server, this has the same behaviour which is the system keep generating the resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast message and getting logged into infolog_hival but one thing different is that the logadm is doing it's job of rotating the log. On the system running OmniOS, I have compare the logadm.conf on both OpenIndiana and OmniOS and there are identical but OmniOS is not rotating this particular log. Is there any way I can check what is wrong? Why logadm is not rotating the infolog_hival when the filesize reach greater than 10m ? This is the setting of logadm.conf from OpenIndiana 151a7: /var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile' Looking into /var/logadm/timestamps # This file holds internal data for logadm(1M). # Do not edit. /var/log/syslog -P 'Sat Dec 3 19:10:00 2016' /var/adm/messages -P 'Wed Oct 26 19:10:00 2016' /var/cron/log -P 'Sat Jun 25 19:10:00 2016' /var/fm/fmd/infolog_hival -P 'Mon Dec 5 19:10:00 2016' /var/adm/wtmpx -P 'Wed Oct 5 19:10:00 2016' This is the setting of logadm.conf from OmniOS R151014: /var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile' Looking into /var/logadm/timestamps # This file holds internal data for logadm(1M). # Do not edit. /var/adm/messages -P 'Tue Dec 6 19:10:00 2016' /var/cron/log -P 'Thu Nov 24 19:10:00 2016' /var/svc/log/system-idmap:default.log -P 'Tue Dec 8 19:10:00 2015' Cron is set to run logadm everyday at 03:10 am. Regards. On Tue, Nov 29, 2016 at 12:16 PM, Lawrence Giam wrote: > Hi All, > > I have a Supermicro box running OmniOS R151014 build 170cea2. > I am getting a lot of entries in infolog_hival about resource.sysevent.EC_ > hba.ESC_sas_hba_port_broadcast > > lawrence at sgsan1n2:/var/fm/fmd$ fmdump -I > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > > lawrence at sgsan1n2:/var/fm/fmd$ fmdump -IV > Nov 29 2016 03:12:20.907712302 (absent) > nvlist version: 0 > driver_instance = 0 > port_address = w500304800bfc5c02 > devfs_path = /pci at 0,0/pci8086,340c at 5/pci15d9,400 at 0 > PhyIdentifier = 0x2 > event_type = port_broadcast_ses > class = resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > version = 0x0 > __ttl = 0x1 > __tod = 0x583c8194 0x361a972e > > Nov 29 2016 03:12:20.907718074 (absent) > nvlist version: 0 > driver_instance = 0 > port_address = w500304800bfc5c03 > devfs_path = /pci at 0,0/pci8086,340c at 5/pci15d9,400 at 0 > PhyIdentifier = 0x3 > event_type = port_broadcast_ses > class = resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > version = 0x0 > __ttl = 0x1 > __tod = 0x583c8194 0x361aadba > > > This is a chassic with 2 motherboard sharing a single backbone, each > motherboard accessing it's own set of disks and we have a HA solution to > auto-mount the disks to the other motherboard should there be a problem > with the motherboard. > > IS it possible to disable them? > > Thanks & Regards. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.elling at richardelling.com Wed Dec 7 05:58:39 2016 From: richard.elling at richardelling.com (Richard Elling) Date: Tue, 6 Dec 2016 21:58:39 -0800 Subject: [OmniOS-discuss] Large infolog_hival file In-Reply-To: References: Message-ID: > On Dec 6, 2016, at 8:16 PM, Lawrence Giam wrote: > > Hi All, > > Also to note that I have another running OpenIndiana 151a7 and this is also a SuperMicro server, this has the same behaviour which is the system keep generating the resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast message and getting logged into infolog_hival but one thing different is that the logadm is doing it's job of rotating the log. > > On the system running OmniOS, I have compare the logadm.conf on both OpenIndiana and OmniOS and there are identical but OmniOS is not rotating this particular log. Is there any way I can check what is wrong? Why logadm is not rotating the infolog_hival when the filesize reach greater than 10m ? Under heavy writes, logadm won?t rotate the logs. You might need to disable the port. We?ve seen cases where miswired SAS connections that are not disabled by default in the firmware cause spurious interrupts. This can be done with various tools, depending on which port is complaining. For example, in smp_utils, smp_phy_control allows you to send link control commands to expanders. However, the only real cure is hardware/firmware. ? richard > > This is the setting of logadm.conf from OpenIndiana 151a7: > /var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile' > > Looking into /var/logadm/timestamps > # This file holds internal data for logadm(1M). > # Do not edit. > /var/log/syslog -P 'Sat Dec 3 19:10:00 2016' > /var/adm/messages -P 'Wed Oct 26 19:10:00 2016' > /var/cron/log -P 'Sat Jun 25 19:10:00 2016' > /var/fm/fmd/infolog_hival -P 'Mon Dec 5 19:10:00 2016' > /var/adm/wtmpx -P 'Wed Oct 5 19:10:00 2016' > > > This is the setting of logadm.conf from OmniOS R151014: > /var/fm/fmd/infolog_hival -N -A 2y -S 50m -s 10m -M '/usr/sbin/fmadm -q rotate infolog_hival && mv /var/fm/fmd/infolog_hival.0- $nfile' > > Looking into /var/logadm/timestamps > # This file holds internal data for logadm(1M). > # Do not edit. > /var/adm/messages -P 'Tue Dec 6 19:10:00 2016' > /var/cron/log -P 'Thu Nov 24 19:10:00 2016' > /var/svc/log/system-idmap:default.log -P 'Tue Dec 8 19:10:00 2015' > > Cron is set to run logadm everyday at 03:10 am. > > Regards. > > > On Tue, Nov 29, 2016 at 12:16 PM, Lawrence Giam > wrote: > Hi All, > > I have a Supermicro box running OmniOS R151014 build 170cea2. > I am getting a lot of entries in infolog_hival about resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > > lawrence at sgsan1n2:/var/fm/fmd$ fmdump -I > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > Nov 29 08:45:33.0893 resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > > lawrence at sgsan1n2:/var/fm/fmd$ fmdump -IV > Nov 29 2016 03:12:20.907712302 (absent) > nvlist version: 0 > driver_instance = 0 > port_address = w500304800bfc5c02 > devfs_path = /pci at 0,0/pci8086,340c at 5/pci15d9,400 at 0 > PhyIdentifier = 0x2 > event_type = port_broadcast_ses > class = resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > version = 0x0 > __ttl = 0x1 > __tod = 0x583c8194 0x361a972e > > Nov 29 2016 03:12:20.907718074 (absent) > nvlist version: 0 > driver_instance = 0 > port_address = w500304800bfc5c03 > devfs_path = /pci at 0,0/pci8086,340c at 5/pci15d9,400 at 0 > PhyIdentifier = 0x3 > event_type = port_broadcast_ses > class = resource.sysevent.EC_hba.ESC_sas_hba_port_broadcast > version = 0x0 > __ttl = 0x1 > __tod = 0x583c8194 0x361aadba > > > This is a chassic with 2 motherboard sharing a single backbone, each motherboard accessing it's own set of disks and we have a HA solution to auto-mount the disks to the other motherboard should there be a problem with the motherboard. > > IS it possible to disable them? > > Thanks & Regards. > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafapi at gmail.com Wed Dec 7 10:49:51 2016 From: rafapi at gmail.com (Rafael Pardinas) Date: Wed, 07 Dec 2016 10:49:51 +0000 Subject: [OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days In-Reply-To: <09E54637-A4C5-4F2E-B272-08C634358767@omniti.com> References: <5F8422A7-850F-4008-A4AF-FC9B1A5E4136@lji.org> <09E54637-A4C5-4F2E-B272-08C634358767@omniti.com> Message-ID: Better documentation would be definitely useful, I find it lacking on many areas (that includes IllumOS as a whole). For instance, the confusion around capped/shared/dedicated-cpu is impressive. Having the zonecfg checking for things could perhaps lead to making the tool too rigid? Thanks On Fri, 2 Dec 2016 at 15:53 Dan McDonald wrote: > > > On Dec 2, 2016, at 3:05 AM, Natxo Asenjo wrote: > > > > So I guess this has fixed it. Thanks! > > Thanks Rafael for bringing that up. > > Naxto --> most network configurations need / these days. Maybe > for 022 I can have the zonecfg CHECK for this? Or at least I need to > document it better in lx(5). > > This is the sort of feedback I'm hoping for as part of 020's "LX Beta". > > Thanks! > Dan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at omniti.com Wed Dec 7 16:23:41 2016 From: danmcd at omniti.com (Dan McDonald) Date: Wed, 7 Dec 2016 11:23:41 -0500 Subject: [OmniOS-discuss] plex on lx zone (centos 6.8) stops working after 2/3 days In-Reply-To: References: <5F8422A7-850F-4008-A4AF-FC9B1A5E4136@lji.org> <09E54637-A4C5-4F2E-B272-08C634358767@omniti.com> Message-ID: <9B29BAAE-10B1-4E0B-A75B-19A74C7DEE88@omniti.com> > On Dec 7, 2016, at 5:49 AM, Rafael Pardinas wrote: > > Better documentation would be definitely useful, I find it lacking on many areas (that includes IllumOS as a whole). We take PRs and issues on man pages: https://github.com/omniti-labs/illumos-omnios Dan From Dirk.Willems at exitas.be Wed Dec 7 16:59:58 2016 From: Dirk.Willems at exitas.be (Willems Dirk) Date: Wed, 7 Dec 2016 16:59:58 +0000 Subject: [OmniOS-discuss] unable to add second nic on KVM In-Reply-To: <166CB11C-4DE9-4B6D-BC2C-4FE7BBAD3493@gmail.com> References: <166CB11C-4DE9-4B6D-BC2C-4FE7BBAD3493@gmail.com> Message-ID: <3e2aa185-4de6-5261-58a3-cd4c6fec4b29@exitas.be> On 06-12-16 23:39, ?????? ?????? wrote: I had a very similar problem a couple of days ago. I solved it by using unique vlan numbers for each nic/vnic pair in the qemu arguments, i.e.: /usr/bin/qemu-system-x86_64 \ -name "$(basename $NAME)" \ -boot cd \ -enable-kvm \ -vnc 0.0.0.0:$VNC \ -smp 2 \ -m $MEM \ -no-hpet \ -localtime \ -drive file=$HDD,if=ide,index=0 \ -drive file=$CD,media=cdrom,if=ide,index=2 \ -net nic,vlan=0,name=net0,model=e1000,macaddr=$mac1 \ -net vnic,vlan=0,name=net0,ifname=$VNIC1,macaddr=$mac1, \ -net nic,vlan=1,name=net1,model=e1000,macaddr=$mac2 \ -net vnic,vlan=1,name=net1,ifname=$VNIC2,macaddr=$mac2, \ -vga std \ -daemonize Daniil _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss Thank you very much Daniil it's working perfect. This make my day :) Kind Regards, Dirk -------------- next part -------------- An HTML attachment was scrubbed... URL: From glush at jet.msk.su Mon Dec 12 13:28:12 2016 From: glush at jet.msk.su (=?utf-8?B?0JTQvNC40YLRgNC40Lkg0JPQu9GD0YjQtdC90L7Qug==?=) Date: Mon, 12 Dec 2016 16:28:12 +0300 Subject: [OmniOS-discuss] NFS server in zones Message-ID: <38BF5174-F5B5-44E0-BA48-886364AD1135@jet.msk.su> Hello, Does anybody knows about any plans to add NFS support in non-global zones? I see Nexenta (?) was trying to do that (https://github.com/dkruchinin/illumos-gate/commits/nfs-zones ), but it was 4 years ago and nfsd in OmniOS still cannot be zoned. -- Dmitry Glushenok Jet Infosystems -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at omniti.com Mon Dec 12 13:47:13 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 12 Dec 2016 08:47:13 -0500 Subject: [OmniOS-discuss] NFS server in zones In-Reply-To: <38BF5174-F5B5-44E0-BA48-886364AD1135@jet.msk.su> References: <38BF5174-F5B5-44E0-BA48-886364AD1135@jet.msk.su> Message-ID: > On Dec 12, 2016, at 8:28 AM, ??????? ???????? wrote: > > Hello, > > Does anybody knows about any plans to add NFS support in non-global zones? From what I can tell the answer right now is no. You may wish to ping the greater illumos lists to see if anyone can elaborate or correct me, though. Dan From youzhong at gmail.com Mon Dec 12 15:37:57 2016 From: youzhong at gmail.com (Youzhong Yang) Date: Mon, 12 Dec 2016 10:37:57 -0500 Subject: [OmniOS-discuss] NFS server in zones In-Reply-To: References: <38BF5174-F5B5-44E0-BA48-886364AD1135@jet.msk.su> Message-ID: We looked into this last week. No, nfs/server can't be run inside a zone. By the way, Oracle Solaris 11.3 can do it, but that's not what we want :-) -Youzhong On Mon, Dec 12, 2016 at 8:47 AM, Dan McDonald wrote: > > > On Dec 12, 2016, at 8:28 AM, ??????? ???????? wrote: > > > > Hello, > > > > Does anybody knows about any plans to add NFS support in non-global > zones? > > From what I can tell the answer right now is no. You may wish to ping the > greater illumos lists to see if anyone can elaborate or correct me, though. > > Dan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at omniti.com Mon Dec 12 16:15:50 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 12 Dec 2016 11:15:50 -0500 Subject: [OmniOS-discuss] Silly very-long-term question Message-ID: How many folks in the audience are running 32-bit binaries that HAVE to be 32-bit for whatever reason? The Y2038 problem crossed my mind today, and the easy permanent cure is to cut off support for 32-bit userland. Don't worry, this isn't a question that'll affect bloody or r151022... heck it probably won't affect r151030 (SUBSEQUENT LTS), but I am curious. Thanks, Dan From bfriesen at simple.dallas.tx.us Mon Dec 12 16:46:27 2016 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Mon, 12 Dec 2016 10:46:27 -0600 (CST) Subject: [OmniOS-discuss] Silly very-long-term question In-Reply-To: References: Message-ID: On Mon, 12 Dec 2016, Dan McDonald wrote: > How many folks in the audience are running 32-bit binaries that HAVE to be 32-bit for whatever reason? The Y2038 problem crossed my mind today, and the easy permanent cure is to cut off support for 32-bit userland. Default compilation in Solaris has historically been 32 bit. Switching to 64bit is eased if the compilation toolchain also defaults (and perhaps only supports) 64bit so that build processes do not need to change. Large amounts of user-compiled software will be 32bit due to the very long history. If OmniOS supports only 64-bit then it will be a bit of work to re-create the installed software as 64-bit. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From peter.tribble at gmail.com Mon Dec 12 17:00:24 2016 From: peter.tribble at gmail.com (Peter Tribble) Date: Mon, 12 Dec 2016 17:00:24 +0000 Subject: [OmniOS-discuss] Silly very-long-term question In-Reply-To: References: Message-ID: On Mon, Dec 12, 2016 at 4:15 PM, Dan McDonald wrote: > How many folks in the audience are running 32-bit binaries that HAVE to > be 32-bit for whatever reason? The Y2038 problem crossed my mind today, > and the easy permanent cure is to cut off support for 32-bit userland. > I'm pretty sure that the day job doesn't have anything that is irredeemably 32-bit. We build what we use from source anyway, and virtually everything is 64-bit already. (Speaking from a wider context, there's a huge amount of stuff that needs fixing, and it's a pile of work.) Don't worry, this isn't a question that'll affect bloody or r151022... heck > it probably won't affect r151030 (SUBSEQUENT LTS), but I am curious. > But r151102 then... -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From skeltonr at btconnect.com Mon Dec 12 17:11:31 2016 From: skeltonr at btconnect.com (Richard Skelton) Date: Mon, 12 Dec 2016 17:11:31 +0000 Subject: [OmniOS-discuss] MPT Firmware Fault, code: 2810 Message-ID: <584EDA43.8020006@btconnect.com> Hi All, I have a Avago SAS 9300-16i Host Bus Adapter (LSI00447) in my Intel Corporation S2600WTTR and I see:- Dec 12 15:13:21 myhost scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,6f08 at 3/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas0): Dec 12 15:13:21 myhost MPT Firmware Fault, code: 2810 Dec 12 15:13:23 myhost scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,6f08 at 3/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas0): Dec 12 15:13:23 myhost MPT Firmware version v5.0.0.0 (SAS3008) Dec 12 15:13:23 myhost scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,6f08 at 3/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas0): Dec 12 15:13:23 myhost mpt_sas0 SAS 3 Supported Dec 12 15:13:23 myhost scsi: [ID 365881 kern.info] /pci at 0,0/pci8086,6f08 at 3/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas0): Dec 12 15:13:23 myhost mpt0: IOC Operational. Dec 12 15:13:31 myhost scsi: [ID 243001 kern.info] w5000cca01830a3e1 FastPath Capable and Enabled Dec 12 15:13:31 myhost scsi: [ID 243001 kern.info] w5000cca018356271 FastPath Capable and Enabled Dec 12 15:13:31 myhost scsi: [ID 243001 kern.info] w5000cca018364819 FastPath Capable and Enabled Dec 12 15:13:31 myhost scsi: [ID 243001 kern.info] w5000cca0387184fd FastPath Capable and Enabled I am running OmniOS r151020 What does it mean? Cheers Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: From daleg at omniti.com Mon Dec 12 18:06:06 2016 From: daleg at omniti.com (Dale Ghent) Date: Mon, 12 Dec 2016 13:06:06 -0500 Subject: [OmniOS-discuss] MPT Firmware Fault, code: 2810 In-Reply-To: <584EDA43.8020006@btconnect.com> References: <584EDA43.8020006@btconnect.com> Message-ID: > On Dec 12, 2016, at 12:11 PM, Richard Skelton wrote: > > Hi All, > I have a Avago SAS 9300-16i Host Bus Adapter (LSI00447) in my Intel Corporation S2600WTTR and I see:- > Dec 12 15:13:21 myhost scsi: [ID 107833 kern.warning] WARNING: /pci at 0,0/pci8086,6f08 at 3/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas0): > Dec 12 15:13:21 myhost MPT Firmware Fault, code: 2810 > I am running OmniOS r151020 > What does it mean? According to LSI's documentation, 2810 refers to "IFAULT_EXCEPTION_IRQ_UNKNOWN", or in slightly more human terms, "Unknown IRQ Interrupt". These are internal errors reported by the MPT2 controller chip /to/ the driver; so these are generally low-level issues which tend to already exist before the OS starts - problems with the card, the PCI slot, the interaction between the card's firmware and the BIOS during initial setup, and so-forth. What's happening in your specific case is that the driver checks the MPT controller for any extant fault conditions, sees that there is one, reports it, and then issues a full reset to the controller which appears to correct the problem and life carries on. My first inclination would be to see if the MPT controller firmware is updated to the latest (you will want the IT variant, of course, not the IR one.) You may also wish to review any interrupt configuration-type settings in your system's BIOS, especially if they aren't defaulted. /dale From mtalbott at lji.org Mon Dec 12 19:43:08 2016 From: mtalbott at lji.org (Michael Talbott) Date: Mon, 12 Dec 2016 11:43:08 -0800 Subject: [OmniOS-discuss] Silly very-long-term question In-Reply-To: References: Message-ID: <9EE240CD-A49C-4D5D-A485-96FD93BCDACF@lji.org> This brings up an interesting issue I've ran into. I've found that compiling and using samba with winbind on OmniOS must be 32 bit in order for winbind to resolve user ids. After some digging it appears some of the core system utilities are only available as 32 bit versions and can't look up ids with 64 bit libs. For instance the built in "id" command is 32-bit only, hence, can't use a 64 bit version of winbind :( # file /usr/bin/id /usr/bin/id: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, not stripped, no debugging information available ________________________ Michael Talbott Systems Administrator La Jolla Institute > On Dec 12, 2016, at 8:15 AM, Dan McDonald wrote: > > How many folks in the audience are running 32-bit binaries that HAVE to be 32-bit for whatever reason? The Y2038 problem crossed my mind today, and the easy permanent cure is to cut off support for 32-bit userland. > > Don't worry, this isn't a question that'll affect bloody or r151022... heck it probably won't affect r151030 (SUBSEQUENT LTS), but I am curious. > > Thanks, > Dan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at omniti.com Mon Dec 12 19:46:44 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 12 Dec 2016 14:46:44 -0500 Subject: [OmniOS-discuss] Silly very-long-term question In-Reply-To: <9EE240CD-A49C-4D5D-A485-96FD93BCDACF@lji.org> References: <9EE240CD-A49C-4D5D-A485-96FD93BCDACF@lji.org> Message-ID: <7B1F2B33-C2BB-4429-8EBC-65FE7A769E1B@omniti.com> > On Dec 12, 2016, at 2:43 PM, Michael Talbott wrote: > > This brings up an interesting issue I've ran into. I've found that compiling and using samba with winbind on OmniOS must be 32 bit in order for winbind to resolve user ids. After some digging it appears some of the core system utilities are only available as 32 bit versions and can't look up ids with 64 bit libs. For instance the built in "id" command is 32-bit only, hence, can't use a 64 bit version of winbind :( > > # file /usr/bin/id > /usr/bin/id: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, not stripped, no debugging information available Doing a check on just the /usr/bin/entry is misleading. Check: /usr/bin/i86 (illumos) /usr/bin/i386 (OmniOS-specific) /usr/bin/amd64 (both, 64-bit) prior to declaring a binary is just 32-bit. In this case, however, id is 32-bit only: bloody(~)[0]% ls /usr/bin/*/id ls-F: No match. bloody(~)[1]% ls /usr/bin/*/digest /usr/bin/amd64/digest* /usr/bin/i86/digest* bloody(~)[0]% ls /usr/bin/*/python2.6 /usr/bin/amd64/python2.6* /usr/bin/i386/python2.6* bloody(~)[0]% You can certainly, BTW, file an RFE in illumos to get id(1) to be 64-bit happy, or even go into the source and fix it yourself. Dan From nrhuff at umn.edu Mon Dec 12 20:44:50 2016 From: nrhuff at umn.edu (Nathan R Huff) Date: Mon, 12 Dec 2016 13:44:50 -0700 Subject: [OmniOS-discuss] Silly very-long-term question In-Reply-To: References: Message-ID: <20161212204449.GM3146@discord.localdomain> You can run a 64bit version of the winbind daemon. You do however need the 32bit nss_winbind library installed. You may also need the 32bit pam library. I run all 64bit samba daemons and the 32bit binaries talk to them just fine as long as the 32 bit libraries are installed. That being said I would be totally fine with everything going 64bit so I wouldn't need to build both the 32 and 64 bit versions. > This brings up an interesting issue I've ran into. I've found that compiling and using samba with winbind on OmniOS must be 32 bit in order for winbind to resolve user ids. After some digging it appears some of the core system utilities are only available as 32 bit versions and can't look up ids with 64 bit libs. For instance the built in "id" command is 32-bit only, hence, can't use a 64 bit version of winbind :( > > # file /usr/bin/id > /usr/bin/id: ELF 32-bit LSB executable 80386 Version 1, dynamically linked, not stripped, no debugging information available > > > ________________________ > Michael Talbott > Systems Administrator > La Jolla Institute > -- Nathan Huff System Administrator Academic Health Center Information Systems University of Minnesota 612-626-9136 From dain.bentley at gmail.com Tue Dec 13 02:22:27 2016 From: dain.bentley at gmail.com (Dain Bentley) Date: Mon, 12 Dec 2016 21:22:27 -0500 Subject: [OmniOS-discuss] Can't install OniOS on Intel PSL 5000 Message-ID: <0ada01d254e7$bff18220$3fd48660$@gmail.com> It's an older board, but I've run Open Indiana and OmniOS on it before. I can't get it to install, it just reboots at random. I only have the one hard drive in it so far, nothing on the logs, it wants me to bypass long and says login services cannot run for some reason. From jdg117 at elvis.arl.psu.edu Tue Dec 13 13:46:26 2016 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Tue, 13 Dec 2016 08:46:26 -0500 Subject: [OmniOS-discuss] Can't install OniOS on Intel PSL 5000 In-Reply-To: Your message of "Mon, 12 Dec 2016 21:22:27 EST." <0ada01d254e7$bff18220$3fd48660$@gmail.com> References: <0ada01d254e7$bff18220$3fd48660$@gmail.com> Message-ID: <201612131346.uBDDkQsv011131@elvis.arl.psu.edu> In message <0ada01d254e7$bff18220$3fd48660$@gmail.com>, "Dain Bentley" writes: >It's an older board, but I've run Open Indiana and OmniOS on it before. I >can't get it to install, it just reboots at random. I only have the one >hard drive in it so far, nothing on the logs, it wants me to bypass long and >says login services cannot run for some reason. Random reboots (and random stack traces when boot under the kernel debugger) point to hardware, not software errors, often cooling (CPU, GPU, spinning rust) and bad memory. Al Hopper's guide is an oldy, but goody: Add -k option to the GRUB boot options: John groenveld at acm.org From hasslerd at gmx.li Wed Dec 14 13:45:09 2016 From: hasslerd at gmx.li (Dominik Hassler) Date: Wed, 14 Dec 2016 14:45:09 +0100 Subject: [OmniOS-discuss] pre-release: lxadm Message-ID: <301cce39-f38f-aa09-6327-a8b4bb9d9ed5@gmx.li> Hi, just wanted to spread the word about lxadm. Its aim is to ease creation/editing/duplication of LX zones. Like kvmadm all the configuration can be done w/ a single JSON config. The tool is not very well tested, yet so I am sure there are lots of bugs and it lacks tons of features but some of you might want to try it already. By now it only works w/ images from Joyent's images repository (images get cached locally) but supporting individual images is on the roadmap. basic usage: * list all available images: # lxadm list-images * creating a LX zone using e.g. the latest debian 8 (jessie) can be done w/ a one-liner # lxadm create $(lxadm list-images |grep debian-8 |tail -1 |awk '{print $1}') lxadm can be found on Github: https://github.com/hadfl/lxadm To avoid further noise on the mailing list please report issues, feature requests on Github only. Cheers Dominik From danmcd at omniti.com Wed Dec 14 15:55:34 2016 From: danmcd at omniti.com (Dan McDonald) Date: Wed, 14 Dec 2016 10:55:34 -0500 Subject: [OmniOS-discuss] pre-release: lxadm In-Reply-To: <301cce39-f38f-aa09-6327-a8b4bb9d9ed5@gmx.li> References: <301cce39-f38f-aa09-6327-a8b4bb9d9ed5@gmx.li> Message-ID: Thank you for doing this! Dan From gearboxes at outlook.com Thu Dec 15 17:02:39 2016 From: gearboxes at outlook.com (Machine Man) Date: Thu, 15 Dec 2016 17:02:39 +0000 Subject: [OmniOS-discuss] Smartmontools - JBOD chassis Message-ID: Can the smartmontools be used on OmniOS to collect JBOD enclosure status, FANs voltages etc. ? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From daleg at omniti.com Thu Dec 15 19:47:46 2016 From: daleg at omniti.com (Dale Ghent) Date: Thu, 15 Dec 2016 14:47:46 -0500 Subject: [OmniOS-discuss] Smartmontools - JBOD chassis In-Reply-To: References: Message-ID: <6438F1AC-FF45-4E89-846D-FEFB8FB23CF5@omniti.com> > On Dec 15, 2016, at 12:02 PM, Machine Man wrote: > > Can the smartmontools be used on OmniOS to collect JBOD enclosure status, FANs voltages etc. ? SMARTmontools is a disk device monitoring tool that pulls SMART telemetry from the actual disks themselves. What I think you're referring to is something different, called SCSI Enclosure Services (SES), which to my knowledge SMARTmontools doesn't really concern itself with. There is a ses driver in OmniOS, however it's fairly dated and basic; and there are no utilities which directly consume it in userland. I might be mistaken, but the ses driver was mainly used back in the day by unbunbled Sun storage products, such as software that interfaced with the StorEDGE line of JBODs and RAID arrays. Nexenta reportedly has a much improved ses driver with userland utility to query enclosure status and manipulate service lights on drive slots, but they haven't upstreamed this. /dale From adam.stevko at gmail.com Thu Dec 15 20:23:41 2016 From: adam.stevko at gmail.com (=?utf-8?Q?Adam_=C5=A0tevko?=) Date: Thu, 15 Dec 2016 21:23:41 +0100 Subject: [OmniOS-discuss] Ansible modules for managing illumos networking - help with review/testing needed Message-ID: <6D662975-B347-4993-A51E-A3E86320A63A@gmail.com> Hello, this might matter to people who use Ansible to manage any illumos distributions. I have opened a PR on Ansible's Github (https://github.com/ansible/ansible/pull/19396), which brings in these modules: dladm_iptun dladm_linkprop dladm_vlan ipadm_addr ipadm_addrprop ipadm_ifprop I would like to ask people using Ansible to have a look at these modules, test them and review them, so they can be merged into Ansible before 2.3 is released (January/February). With these modules, 90% of illumos networking can be configured via Ansible. The review is as easy as writing ?shipit? in the PR discussion. After these modules are merged, only remaining network-related pieces missing to be contributed are: - link aggregations - I don?t have an access to a machine where I could test this (if somebody is interested in this and is able to provide testing environment, feel free to contact me privately) - bridges - I have never needed to use them on illumos. (If there is interest, I can implement this as it quite simple to do). - routeadm - to manage ipv(4|6)-(forwarding|routing) options via routeadm command. In the upcoming months, I want to work on more modules and making illumos based systems much easier to automate via Ansible. I have created a repository (https://github.com/xen0l/ansible-illumos-modules), where I have collected all the ideas for modules I want to develop. I am always interested in getting new ideas about modules, so if people have any, feel free to send me a PR with the idea! I also plan to fix any illumos-related bug that appears in Ansible. Those, who might review networking PR, might be also interested in reviewing these PRs: - Gather uptime and device facts from Solarish systems (https://github.com/ansible/ansible/pull/18733) These PRs have already been reviewed, but more reviews will speed up inclusion: - Add module for managing boot environments on FreeBSD/Solaris/illumos systems (https://github.com/ansible/ansible/pull/19180) - Modules for gathering facts about ZFS datasets and pools (https://github.com/ansible/ansible/pull/19181) I would like to thank everyone in advance for helping me test/review/contributing new module ideas. Cheers, Adam From Kevin.Swab at ColoState.EDU Thu Dec 15 21:10:22 2016 From: Kevin.Swab at ColoState.EDU (Kevin Swab) Date: Thu, 15 Dec 2016 14:10:22 -0700 Subject: [OmniOS-discuss] Smartmontools - JBOD chassis In-Reply-To: <6438F1AC-FF45-4E89-846D-FEFB8FB23CF5@omniti.com> References: <6438F1AC-FF45-4E89-846D-FEFB8FB23CF5@omniti.com> Message-ID: <02cc12ca-b852-7a42-44de-c12524729ad8@ColoState.EDU> The 'sg_ses' tool from the sg3_utils package may be able to give you the information you're looking for. It's not bundled with the OS or available in any repos that I've seen, but it builds without any fuss on OmniOS. You can download the source here: http://sg.danny.cz/sg/sg3_utils.html Kevin On 12/15/2016 12:47 PM, Dale Ghent wrote: > >> On Dec 15, 2016, at 12:02 PM, Machine Man wrote: >> >> Can the smartmontools be used on OmniOS to collect JBOD enclosure status, FANs voltages etc. ? > > SMARTmontools is a disk device monitoring tool that pulls SMART telemetry from the actual disks themselves. What I think you're referring to is something different, called SCSI Enclosure Services (SES), which to my knowledge SMARTmontools doesn't really concern itself with. > > There is a ses driver in OmniOS, however it's fairly dated and basic; and there are no utilities which directly consume it in userland. I might be mistaken, but the ses driver was mainly used back in the day by unbunbled Sun storage products, such as software that interfaced with the StorEDGE line of JBODs and RAID arrays. > > Nexenta reportedly has a much improved ses driver with userland utility to query enclosure status and manipulate service lights on drive slots, but they haven't upstreamed this. > > /dale > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > -- From hp at pawaq.at Thu Dec 15 21:42:57 2016 From: hp at pawaq.at (Harald Paier) Date: Thu, 15 Dec 2016 22:42:57 +0100 (CET) Subject: [OmniOS-discuss] Smartmontools - JBOD chassis In-Reply-To: References: Message-ID: <1839996127.223864.1481838177276.JavaMail.zimbra@pawaq.at> I fetch information about disks, power supplies, fans, temperatures, etc. from my JBOD enclosue (HP D2700) by simply using: /usr/lib/fm/fmd/fmtopo -V hc://:product-id=HP-D2700-SAS-\* You can also use fmtopo to set or clear drive bay leds on that JBOD harald From: "Machine Man" To: omnios-discuss at lists.omniti.com Sent: Thursday, December 15, 2016 6:02:39 PM Subject: [OmniOS-discuss] Smartmontools - JBOD chassis Can the smartmontools be used on OmniOS to collect JBOD enclosure status, FANs voltages etc. ? Thanks _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard.elling at richardelling.com Fri Dec 16 01:36:28 2016 From: richard.elling at richardelling.com (Richard Elling) Date: Thu, 15 Dec 2016 17:36:28 -0800 Subject: [OmniOS-discuss] Smartmontools - JBOD chassis In-Reply-To: <6438F1AC-FF45-4E89-846D-FEFB8FB23CF5@omniti.com> References: <6438F1AC-FF45-4E89-846D-FEFB8FB23CF5@omniti.com> Message-ID: <21E29F15-FCBF-4F6E-B3F6-D9D3FD77C9E8@richardelling.com> > On Dec 15, 2016, at 11:47 AM, Dale Ghent wrote: > > >> On Dec 15, 2016, at 12:02 PM, Machine Man wrote: >> >> Can the smartmontools be used on OmniOS to collect JBOD enclosure status, FANs voltages etc. ? > > SMARTmontools is a disk device monitoring tool that pulls SMART telemetry from the actual disks themselves. What I think you're referring to is something different, called SCSI Enclosure Services (SES), which to my knowledge SMARTmontools doesn't really concern itself with. fmtopo and sestopo allow you to interface with SES devices, the UI is butugly. I'd recommend the sg3_utils and smp_utils combo since they have a marginally better UI and are available on multiple OSes. -- richard > > There is a ses driver in OmniOS, however it's fairly dated and basic; and there are no utilities which directly consume it in userland. I might be mistaken, but the ses driver was mainly used back in the day by unbunbled Sun storage products, such as software that interfaced with the StorEDGE line of JBODs and RAID arrays. > > Nexenta reportedly has a much improved ses driver with userland utility to query enclosure status and manipulate service lights on drive slots, but they haven't upstreamed this. > > /dale > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From martijn at fennis.tk Sat Dec 17 12:58:02 2016 From: martijn at fennis.tk (Martijn Fennis) Date: Sat, 17 Dec 2016 12:58:02 +0000 Subject: [OmniOS-discuss] stuck in maintenace Message-ID: Hi, During zfs rebuild, memory got used untill i had to unplug the host. Added the arc memory limit. After a second or third reboot, the box only returns in maintenance mode. Did some googling and found to : svcadm clear system/boot-archive but it returns with the same: svc.startd[10]: svc:/system/boot-archive:default: Method or service exit timed out. Killing contract # number Is there a way to fix this? Thanks, Martijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijn at fennis.tk Sat Dec 17 13:41:03 2016 From: martijn at fennis.tk (Martijn Fennis) Date: Sat, 17 Dec 2016 13:41:03 +0000 Subject: [OmniOS-discuss] stuck in maintenace In-Reply-To: References: Message-ID: I?ve found: SMF-8000-KS & SMF-8000-5H Shown when svcs -vx Verzonden vanuit Mail voor Windows 10 Van: Martijn Fennis Verzonden: zaterdag 17 december 2016 14:09 Aan: omnios-discuss at lists.omniti.com Onderwerp: [OmniOS-discuss] stuck in maintenace Hi, During zfs rebuild, memory got used untill i had to unplug the host. Added the arc memory limit. After a second or third reboot, the box only returns in maintenance mode. Did some googling and found to : svcadm clear system/boot-archive but it returns with the same: svc.startd[10]: svc:/system/boot-archive:default: Method or service exit timed out. Killing contract # number Is there a way to fix this? Thanks, Martijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimklimov at cos.ru Sun Dec 18 19:01:26 2016 From: jimklimov at cos.ru (Jim Klimov) Date: Sun, 18 Dec 2016 20:01:26 +0100 Subject: [OmniOS-discuss] stuck in maintenace In-Reply-To: References: Message-ID: 17 ??????? 2016??. 13:58:02 CET, Martijn Fennis ?????: >Hi, > > >During zfs rebuild, memory got used untill i had to unplug the host. > >Added the arc memory limit. > >After a second or third reboot, the box only returns in maintenance >mode. > > >Did some googling and found to : > > >svcadm clear system/boot-archive > >but it returns with the same: > >svc.startd[10]: svc:/system/boot-archive:default: Method or service >exit timed out. Killing contract # number > > >Is there a way to fix this? > > >Thanks, > >Martijn > > >------------------------------------------------------------------------ > >_______________________________________________ >OmniOS-discuss mailing list >OmniOS-discuss at lists.omniti.com >http://lists.omniti.com/mailman/listinfo/omnios-discuss This sounds reminiscent of issues I had some 6-7 years ago on opensolaris lists (back then). In particular, the seeming culprit was that zfs under-the-hood activities like large pool deletions needed more kernel ram than i had physically available, so after processing some queued operations, the box halted with no mem available (under 32M for several minutes in a row). It took 2 weeks of reboots for the box to complete its queue of operations (which it did progress, monitorable with zdb -DD IIRC) and a nujber of worried emails to the lists ;) Not sure your case is similar, but try to track any delayed operations (maybe nowadays via 'zpool get all rpool') to see if progress is being made across reboots. Maybe younjust heec to be patient... Jim -- Typos courtesy of K-9 Mail on my Samsung Android From danmcd at omniti.com Mon Dec 19 19:27:32 2016 From: danmcd at omniti.com (Dan McDonald) Date: Mon, 19 Dec 2016 14:27:32 -0500 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? Message-ID: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> OpenSSH 7.4 is coming soon. The maintainer of the illumos patch set is curious about the need for GSSAPI key exchanges in OpenSSH, now that it has completely replaced SunSSH. I think some of you may use this. Is it mission critical for you? Please provide feedback on here. I'm not sure what will happen, but knowing the fallout one way or the other would help. Thanks, Dan From alex at cooperi.net Mon Dec 19 19:31:15 2016 From: alex at cooperi.net (Alex Wilson) Date: Mon, 19 Dec 2016 11:31:15 -0800 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> Message-ID: <680dbec2-33be-fd60-d2fd-72b25fb4f543@cooperi.net> On 12/19/16 11:27 AM, Dan McDonald wrote: > OpenSSH 7.4 is coming soon. The maintainer of the illumos patch set is curious about the need for GSSAPI key exchanges in OpenSSH, now that it has completely replaced SunSSH. > > I think some of you may use this. Is it mission critical for you? Please provide feedback on here. I'm not sure what will happen, but knowing the fallout one way or the other would help. > And to clarify, before we get confusion, this is ONLY about the krb5 *key exchange* feature, not about krb5 authentication. The two are independent of each other. You can still log in to a machine using krb5 auth without krb5-kex, but you will get prompted about trusting the host key you're connecting to (instead of automatically trusting it based on krb5). From mir at miras.org Mon Dec 19 19:36:33 2016 From: mir at miras.org (Michael Rasmussen) Date: Mon, 19 Dec 2016 20:36:33 +0100 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> Message-ID: <20161219203633.31230201@sleipner.datanom.net> On Mon, 19 Dec 2016 14:27:32 -0500 Dan McDonald wrote: > OpenSSH 7.4 is coming soon. The maintainer of the illumos patch set is curious about the need for GSSAPI key exchanges in OpenSSH, now that it has completely replaced SunSSH. > > I think some of you may use this. Is it mission critical for you? Please provide feedback on here. I'm not sure what will happen, but knowing the fallout one way or the other would help. > If people wants to integrate Omnios in a Windows AD environment with native kerberos login GSSAPI is a crucial component. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: A kiss is a course of procedure, cunningly devised, for the mutual stoppage of speech at a moment when words are superfluous. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From alexander.r.eremin at gmail.com Mon Dec 19 19:37:51 2016 From: alexander.r.eremin at gmail.com (Alexander) Date: Mon, 19 Dec 2016 21:37:51 +0200 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> Message-ID: For Nexenta we specifically put GSSAPIAuthentication no GSSAPIKeyExchange no to reduce connection time (~ 60s). +1 for removing Yst?v?llisin terveisin, Alexander > On 19 Dec 2016, at 21.27, Dan McDonald wrote: > > OpenSSH 7.4 is coming soon. The maintainer of the illumos patch set is curious about the need for GSSAPI key exchanges in OpenSSH, now that it has completely replaced SunSSH. > > I think some of you may use this. Is it mission critical for you? Please provide feedback on here. I'm not sure what will happen, but knowing the fallout one way or the other would help. > > Thanks, > Dan > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at miras.org Mon Dec 19 20:11:10 2016 From: mir at miras.org (Michael Rasmussen) Date: Mon, 19 Dec 2016 21:11:10 +0100 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> Message-ID: <20161219211110.4a631648@sleipner.datanom.net> On Mon, 19 Dec 2016 21:37:51 +0200 Alexander wrote: > For Nexenta we specifically put > GSSAPIAuthentication no > GSSAPIKeyExchange no > to reduce connection time (~ 60s). > +1 for removing > Instead of removing it it could be default configured to be disabled. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: Each kiss is as the first. -- Miramanee, Kirk's wife, "The Paradise Syndrome", stardate 4842.6 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From alex at cooperi.net Mon Dec 19 21:13:19 2016 From: alex at cooperi.net (Alex Wilson) Date: Mon, 19 Dec 2016 13:13:19 -0800 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <20161219203633.31230201@sleipner.datanom.net> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> <20161219203633.31230201@sleipner.datanom.net> Message-ID: On 12/19/16 11:36 AM, Michael Rasmussen wrote: > On Mon, 19 Dec 2016 14:27:32 -0500 > Dan McDonald wrote: > >> OpenSSH 7.4 is coming soon. The maintainer of the illumos patch set is curious about the need for GSSAPI key exchanges in OpenSSH, now that it has completely replaced SunSSH. >> >> I think some of you may use this. Is it mission critical for you? Please provide feedback on here. I'm not sure what will happen, but knowing the fallout one way or the other would help. >> > If people wants to integrate Omnios in a Windows AD environment with > native kerberos login GSSAPI is a crucial component. > Please note my reply further up the thread. Turning GSSAPI Key Exchange off does *not* disable GSSAPI *authentication*, which is an entirely separate feature. Are you using GSS key exchange with an AD environment? If so, is that part as critical as the authentication for your use case? I'd be curious to hear any details of your setup if you wouldn't mind sharing. From mir at miras.org Mon Dec 19 21:52:00 2016 From: mir at miras.org (Michael Rasmussen) Date: Mon, 19 Dec 2016 22:52:00 +0100 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> <20161219203633.31230201@sleipner.datanom.net> Message-ID: <20161219225200.7cf35d29@sleipner.datanom.net> On Mon, 19 Dec 2016 13:13:19 -0800 Alex Wilson wrote: > > Are you using GSS key exchange with an AD environment? If so, is that > part as critical as the authentication for your use case? I'd be curious > to hear any details of your setup if you wouldn't mind sharing. > key exchange is required to be a first class citizen in an AD realm. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: sillema sillema nika su -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From alex at cooperi.net Mon Dec 19 22:56:18 2016 From: alex at cooperi.net (Alex Wilson) Date: Mon, 19 Dec 2016 14:56:18 -0800 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <20161219225200.7cf35d29@sleipner.datanom.net> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> <20161219203633.31230201@sleipner.datanom.net> <20161219225200.7cf35d29@sleipner.datanom.net> Message-ID: On 12/19/16 1:52 PM, Michael Rasmussen wrote: > On Mon, 19 Dec 2016 13:13:19 -0800 > Alex Wilson wrote: > >> >> Are you using GSS key exchange with an AD environment? If so, is that >> part as critical as the authentication for your use case? I'd be curious >> to hear any details of your setup if you wouldn't mind sharing. >> > key exchange is required to be a first class citizen in an AD realm. > Do you have any links to explanations as to why this is? Or further hints for what I should look at? I can easily understand why GSSAPI authentication (at least gssapi-with-mic) is needed, but I can't seem to find anything by Googling about gssapi-keyex and AD and why it would be required. I have set up SSH servers in AD environments before myself and only used gssapi-with-mic, but I certainly don't claim to be an expert in it. In your deployment, do you still generate host keys for your machines? >From what I've read about it, the only advantage of the gssapi-keyex method is that you don't need host keys (i.e. /etc/ssh/ssh_host_*_key files) and you never see "The authenticity of host 'blah (1.2.3.4)' can't be established. Are you sure you want to continue connecting (yes/no)?" prompts. Is there something I'm missing here? I apologise if it feels like I'm wasting your time on this, but I genuinely would like to understand the issues here. From mir at miras.org Mon Dec 19 23:35:14 2016 From: mir at miras.org (Michael Rasmussen) Date: Tue, 20 Dec 2016 00:35:14 +0100 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> <20161219203633.31230201@sleipner.datanom.net> <20161219225200.7cf35d29@sleipner.datanom.net> Message-ID: <20161220003514.426f71cb@sleipner.datanom.net> On Mon, 19 Dec 2016 14:56:18 -0800 Alex Wilson wrote: > > Do you have any links to explanations as to why this is? Or further > hints for what I should look at? I can easily understand why GSSAPI > authentication (at least gssapi-with-mic) is needed, but I can't seem to > find anything by Googling about gssapi-keyex and AD and why it would be > required. I have set up SSH servers in AD environments before myself and > only used gssapi-with-mic, but I certainly don't claim to be an expert > in it. > In my understanding (I am certainly no windows guru either :-) to be able to request kerberos/service tickets from the KDC (AD) you need to be able to receive and send tickets so for this to work when login in via SSH the SSH login process must be able to fetch a TGT from the KDC which to the best of my knowledge requires the SSH key exchange feature. Read more here: https://technet.microsoft.com/en-us/library/cc772815(v=ws.10).aspx > In your deployment, do you still generate host keys for your machines? > From what I've read about it, the only advantage of the gssapi-keyex > method is that you don't need host keys (i.e. /etc/ssh/ssh_host_*_key > files) and you never see "The authenticity of host 'blah (1.2.3.4)' > can't be established. Are you sure you want to continue connecting > (yes/no)?" prompts. Is there something I'm missing here? > No, when using SSH key exchange feature the "host key map" is maintained automatically by the AD and globally shared between all members of the AD realm. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: If you are too busy to read, then you are too busy. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From henson at acm.org Tue Dec 20 01:49:54 2016 From: henson at acm.org (Paul B. Henson) Date: Mon, 19 Dec 2016 17:49:54 -0800 Subject: [OmniOS-discuss] Disabling GSSAPI Key Exchange from future OpenSSH? In-Reply-To: <20161220003514.426f71cb@sleipner.datanom.net> References: <4C9F4C6B-A614-4B00-B372-21E8C980D3A2@omniti.com> <20161219203633.31230201@sleipner.datanom.net> <20161219225200.7cf35d29@sleipner.datanom.net> <20161220003514.426f71cb@sleipner.datanom.net> Message-ID: <20161220014954.GB17276@bender.unx.cpp.edu> On Tue, Dec 20, 2016 at 12:35:14AM +0100, Michael Rasmussen wrote: > KDC which to the best of my knowledge requires the SSH key exchange > feature. Read more here: [...] > No, when using SSH key exchange feature the "host key map" is > maintained automatically by the AD and globally shared between all > members of the AD realm. Eh, I could be mistaken, but I'm reasonably confident that ssh key exchange and ssh authentication protocols are orthogonal. You could use GSSAPI key exchange and then authenticate with a public key, or use key exchange via host keys in known_hosts and then authenticate via GSSAPI. There's no requirement to have done key exchange via GSSAPI to do authentication using Kerberos via GSSAPI, whether your Kerberos server is MIT, AD, or Heimdal. It is true that if you use GSSAPI key exchange you don't need to maintain known_hosts files or distribute host keys, as that method avails of the principals in the KDC and that trust framework to verify the authenticity of the server. Back to the original question - we use GSSAPI authentication and credential forwarding extensively, but do not use and don't have any plans to use GSSAPI key exchange. From hazzino at gmail.com Tue Dec 20 23:06:36 2016 From: hazzino at gmail.com (=?UTF-8?Q?cristian_panci=C3=A0?=) Date: Wed, 21 Dec 2016 00:06:36 +0100 Subject: [OmniOS-discuss] Bhyve Hyper Message-ID: Hi there does anyone installed smartos omnios under those virt. Like bhyve and hyper-v? If yes any suggestions,Tut's. As a home server and virtual lab for pentesting and video streaming for my family,I need some tips about a medium high motherboard ,what CPU and RAM type max 1300euro Thank you in advance -------------- next part -------------- An HTML attachment was scrubbed... URL: From alka at hfg-gmuend.de Tue Dec 20 23:16:00 2016 From: alka at hfg-gmuend.de (=?UTF-8?Q?G=c3=bcnther_Alka?=) Date: Wed, 21 Dec 2016 00:16:00 +0100 Subject: [OmniOS-discuss] [smartos-discuss] Bhyve Hyper In-Reply-To: References: Message-ID: <310e04a2-c4be-b0d3-da58-61b4b1d364f7@hfg-gmuend.de> I use ESXi (free) as base due the best of all support for any guests and pass-through of a real HBA with disks and OmniOS ontop see http://napp-it.org/doc/downloads/napp-in-one.pdf some build examples http://www.napp-it.org/doc/downloads/napp-it_build_examples.pdf Gea Am 21.12.2016 um 00:06 schrieb cristian panci?: > Hi there does anyone installed smartos omnios under those virt. Like > bhyve and hyper-v? > If yes any suggestions,Tut's. > As a home server and virtual lab for pentesting and video streaming > for my family,I need some tips about a medium high motherboard ,what > CPU and RAM type max 1300euro > Thank you in advance > > *smartos-discuss* | Archives > > > | Modify > > Your Subscription [Powered by Listbox] > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kiv at kiv.pp.ru Wed Dec 21 09:47:18 2016 From: kiv at kiv.pp.ru (=?UTF-8?B?0JjQu9GM0Y8g0JrRg9C70LDQs9C40L0=?=) Date: Wed, 21 Dec 2016 12:47:18 +0300 Subject: [OmniOS-discuss] About block disk devices in lx-branded zone Message-ID: Hi all. Unfortunately, I cannot read C code, especially in kernel sources. If anybody knows and can confirm or deny, please reply with your opinion - is this some kind of my error or desired/supported behaviour. I've just created centos 6 zone and, additionally to usual config, add there 2 raw disk devices: ==== add device set match=/dev/rdsk/vol0 end add device set match=/dev/rdsk/vol1 end ==== Both these are in fact ZVOLs (but created manually by `mknod` inside /dev/rdsk - because zoneadm only allows device nodes from /dev filesystem to pass into zone): ==== root at omnios:/root# ls -lL /dev/rdsk/vol* /dev/zvol/dsk/rpool/vol* brw-r--r-- 1 root root 268, 3 Dec 21 15:05 /dev/rdsk/vol0 brw-r--r-- 1 root root 268, 4 Dec 21 14:25 /dev/rdsk/vol1 brw------- 1 root sys 268, 3 Dec 21 14:24 /dev/zvol/dsk/rpool/vol0 brw------- 1 root sys 268, 4 Dec 21 14:24 /dev/zvol/dsk/rpool/vol1 ==== From inside zone I can dd from and to these devices: ==== [root at centos ~]# dd if=/dev/urandom of=/dev/rdsk/vol0 bs=1024k count=64 64+0 records in 64+0 records out 67108864 bytes (67 MB) copied, 10.0342 s, 6.7 MB/s [root at centos ~]# dd if=/dev/rdsk/vol0 of=/dev/rdsk/vol1 bs=1024k 10240+0 records in 10240+0 records out 10737418240 bytes (11 GB) copied, 436.127 s, 24.6 MB/s ==== Then I compare these ZVOLs content visible from global zone with dump visible in lx zone - `diff` says nothing. `zpool scrub` in global zone also is happy. It seems that I can use block disk devices in lx-branded zone - as I can do it in native zones. But is this really so? -- ? ?????????, ???? ??????? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3808 bytes Desc: Firma criptogr??fica S/MIME URL: From danmcd at omniti.com Wed Dec 21 15:17:50 2016 From: danmcd at omniti.com (Dan McDonald) Date: Wed, 21 Dec 2016 10:17:50 -0500 Subject: [OmniOS-discuss] About block disk devices in lx-branded zone In-Reply-To: References: Message-ID: <43A30FAD-9488-43AF-9A5D-E5C302C3A1AB@omniti.com> > On Dec 21, 2016, at 4:47 AM, ???? ??????? wrote: You can pass zvol entries straight into your zone, but it does require some indirection. Create a subdirectory from your pool... in my example it's "zvol". In your zonecfg, have an entry like this: add device set match=/dev/zvol/dsk/rpool/zvol/* end And you can pass them in directly. > It seems that I can use block disk devices in lx-branded zone - as I can > do it in native zones. But is this really so? Now this is a more interesting question. The scope of what LX zones can and cannot do comes into play. Raw disks in LX zones can probably work with basic read/write ops, but I suspect once you get into ANYTHING mildly tricky with dkio(7I) it breaks down. A linux app will try ioctls on the raw drives that will return errors because an LX zone still has an illumos kernel underneath at the end of the day. Before I go down this further, and even suggest you ping another mailing list, I need to know: What problem are you REALLY trying to solve? Or why do you need raw disks in an LX zone? Thanks, Dan From danmcd at omniti.com Wed Dec 21 15:39:47 2016 From: danmcd at omniti.com (Dan McDonald) Date: Wed, 21 Dec 2016 10:39:47 -0500 Subject: [OmniOS-discuss] Curl now at 7.52 Message-ID: <0B612542-F4BA-4310-9479-53A4B9D58BD8@omniti.com> All supported OmniOS releases: r151014 (LTS) r151018 (old Stable) r151020 (current Stable) now have their cURL updated to 7.52. This is a(nother) security update, so please "pkg update" quickly. If you are not using linked-image zones (ipkg vs. lipkg), make sure your zones get updated appropriately as well. Dan From daleg at omniti.com Wed Dec 21 21:02:57 2016 From: daleg at omniti.com (Dale Ghent) Date: Wed, 21 Dec 2016 16:02:57 -0500 Subject: [OmniOS-discuss] ANN: tun/tap driver now available Message-ID: <46D3DB92-F6D0-434C-A0E6-4264F73D61DD@omniti.com> As a result of some internal needs, we have decided to provide an official package for the Universal TUN/TAP driver - http://vtun.sourceforge.net/tun/ The new pkg://omnios/driver/tuntap package (and accompanying update to the omnios-userland incorporation) is now available for OmniOS r151014 (LTS), r151018, and r151020. It will also be available on Bloody shortly. This is an optional package and not installed by default. /dale From feigin at iis.ee.ethz.ch Fri Dec 23 10:22:29 2016 From: feigin at iis.ee.ethz.ch (Adam Feigin) Date: Fri, 23 Dec 2016 11:22:29 +0100 Subject: [OmniOS-discuss] OmniOS FreeIPA Integration Message-ID: <971dcf49-55f5-49b7-8dad-3b1942d4216c@iis.ee.ethz.ch> Has anyone managed to get OmniOS bound and working to a FreeIPA (version 4.4 LDAP) server ? So far, I've managed to get it to bind correctly, I get kerberos tickets without problems, and I can see entries with ldaplist/getent/id but actual logins do not work, either console or ssh These pages were vaguely helpful https://asenjo.nl/wiki/index.php/Omnios_ipa_client http://etcfstab.com/oraclelinux/solaris_n_freeipa.html If anyone has actually managed to get this working, I'd appreciate any pointers. TIA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From danmcd at omniti.com Fri Dec 23 11:46:47 2016 From: danmcd at omniti.com (Dan McDonald) Date: Fri, 23 Dec 2016 06:46:47 -0500 Subject: [OmniOS-discuss] Curl now at 7.52.1 (was Re: Curl now at 7.52) In-Reply-To: <0B612542-F4BA-4310-9479-53A4B9D58BD8@omniti.com> References: <0B612542-F4BA-4310-9479-53A4B9D58BD8@omniti.com> Message-ID: <0065CCCD-6843-426D-BF90-14130221DC3A@omniti.com> > On Dec 21, 2016, at 10:39 AM, Dan McDonald wrote: > > All supported OmniOS releases: > > r151014 (LTS) > r151018 (old Stable) > r151020 (current Stable) > > now have their cURL updated to 7.52. This is a(nother) security update, so please "pkg update" quickly. If you are not using linked-image zones (ipkg vs. lipkg), make sure your zones get updated appropriately as well. Turns out there was one missing bug to fix (as part of an overall 7.52 improvement in random number usage.. it was overlooked). Everything above still holds true, but you'll have to update again, this time to 7.52.1. Thanks, Dan p.s. I'm officially on break today, so pardon any latency until January 4th or so. From Dirk.Willems at exitas.be Fri Dec 23 19:41:18 2016 From: Dirk.Willems at exitas.be (Willems Dirk) Date: Fri, 23 Dec 2016 19:41:18 +0000 Subject: [OmniOS-discuss] ipadm: unknown subcommand 'create-ipmp' Message-ID: <86696f70-d081-8d6d-8a47-691e5beeebf7@exitas.be> Hello OmniOS, I tried to create an ipmp group but it seems it's not there ? I get ipadm: unknown subcommand 'create-ipmp' Tried also with add-ipmp the same error, and in the man I don't see anything about ipmp ? How do you guy's make an ipmp group or only use aggregraat ? And what about dlmp is there something for the future ? Thank you. Kind Regards, Dirk -- [cid:part1.08F181D0.1C277E05 at exitas.be] Dirk Willems System Engineer [cid:part3.9E964CA8.C96124C0 at exitas.be] +32 (0)3 443 12 38 [cid:part5.A7332B7F.E7066BB0 at exitas.be] dirk.willems at exitas.be [cid:part7.BFFBF82C.D6E91BF7 at exitas.be] Veldkant 31 - 2550 Kontich [cid:part9.17B213F4.88C63D99 at exitas.be] www.exitas.be Disclaimer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: exitas_PMS.png Type: image/png Size: 8486 bytes Desc: exitas_PMS.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm.png Type: image/png Size: 524 bytes Desc: gsm.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mail.png Type: image/png Size: 791 bytes Desc: Mail.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: plaats.png Type: image/png Size: 803 bytes Desc: plaats.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: huis.png Type: image/png Size: 796 bytes Desc: huis.png URL: From peter.tribble at gmail.com Fri Dec 23 20:14:05 2016 From: peter.tribble at gmail.com (Peter Tribble) Date: Fri, 23 Dec 2016 20:14:05 +0000 Subject: [OmniOS-discuss] ipadm: unknown subcommand 'create-ipmp' In-Reply-To: <86696f70-d081-8d6d-8a47-691e5beeebf7@exitas.be> References: <86696f70-d081-8d6d-8a47-691e5beeebf7@exitas.be> Message-ID: On Fri, Dec 23, 2016 at 7:41 PM, Willems Dirk wrote: > Hello OmniOS, > > > I tried to create an ipmp group > but it seems it's not there ? > > I get ipadm: unknown subcommand 'create-ipmp' > > Tried also with add-ipmp the same error, and in the man I don't see > anything about ipmp ? > > How do you guy's make an ipmp group or only use aggregraat ? > Configuring IPMP in OmniOS is done like Solaris 10 (which involves much fiddling with /etc/hostname.* files), not like Solaris 11 (which your ipadm command would be correct for). I have old servers (which I didn't set up) using IPMP; my newer systems use link aggregations which I've always found *much* easier, but it does need support on the switch side. > And what about dlmp is there something for the future ? > Again, I believe that dlmp is something that Oracle Solaris 11 has, we just have regular link aggregation. > Thank you. > > > Kind Regards, > > > Dirk > > -- > > > > *Dirk Willems * > System Engineer > > > > *+32 (0)3 443 12 38* <003234431238> > > dirk.willems at exitas.be > > *Veldkant 31 - 2550 Kontich* > > www.exitas.be > > *Disclaimer* > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > > -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: exitas_PMS.png Type: image/png Size: 8486 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mail.png Type: image/png Size: 791 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm.png Type: image/png Size: 524 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: plaats.png Type: image/png Size: 803 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: huis.png Type: image/png Size: 796 bytes Desc: not available URL: From Dirk.Willems at exitas.be Fri Dec 23 20:34:25 2016 From: Dirk.Willems at exitas.be (Willems Dirk) Date: Fri, 23 Dec 2016 20:34:25 +0000 Subject: [OmniOS-discuss] ipadm: unknown subcommand 'create-ipmp' In-Reply-To: References: <86696f70-d081-8d6d-8a47-691e5beeebf7@exitas.be> Message-ID: Thank you Peter for explaining. Normally I also use only aggregation, but was wondering when like you said if the switch is not supporting it. I met Solaris 4 years ago and loved the system but the visions from Oracle don't reflect on mine and with the hoax of Solaris 12, I've decided that all my energy goes to illumos and where I can I will help. I hope I will met you guy's on 4 and 5 Feb on Brussels, I'm very excited for talking to you. Btw: Your jkstat helped me a couple of times for troubleshooting really great Tool !!! Thank you very much. Kind Regards Dirk On 23-12-16 21:14, Peter Tribble wrote: On Fri, Dec 23, 2016 at 7:41 PM, Willems Dirk > wrote: Hello OmniOS, I tried to create an ipmp group but it seems it's not there ? I get ipadm: unknown subcommand 'create-ipmp' Tried also with add-ipmp the same error, and in the man I don't see anything about ipmp ? How do you guy's make an ipmp group or only use aggregraat ? Configuring IPMP in OmniOS is done like Solaris 10 (which involves much fiddling with /etc/hostname.* files), not like Solaris 11 (which your ipadm command would be correct for). I have old servers (which I didn't set up) using IPMP; my newer systems use link aggregations which I've always found *much* easier, but it does need support on the switch side. And what about dlmp is there something for the future ? Again, I believe that dlmp is something that Oracle Solaris 11 has, we just have regular link aggregation. Thank you. Kind Regards, Dirk -- [cid:part2.D6F4FBC7.5E906549 at exitas.be] Dirk Willems System Engineer [cid:part4.1EF4E285.60C8F2FC at exitas.be] +32 (0)3 443 12 38 [cid:part6.C8731DB4.F60CC461 at exitas.be] dirk.willems at exitas.be [cid:part9.8B18CDA5.4EC9A106 at exitas.be] Veldkant 31 - 2550 Kontich [cid:part11.FBB03E2C.6DFF68FB at exitas.be] www.exitas.be Disclaimer _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss at lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00001.png Type: image/png Size: 8486 bytes Desc: ATT00001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00002.png Type: image/png Size: 524 bytes Desc: ATT00002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00003.png Type: image/png Size: 791 bytes Desc: ATT00003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00004.png Type: image/png Size: 803 bytes Desc: ATT00004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT00005.png Type: image/png Size: 796 bytes Desc: ATT00005.png URL: From natxo.asenjo at gmail.com Fri Dec 23 20:57:42 2016 From: natxo.asenjo at gmail.com (Natxo Asenjo) Date: Fri, 23 Dec 2016 21:57:42 +0100 Subject: [OmniOS-discuss] OmniOS FreeIPA Integration In-Reply-To: <971dcf49-55f5-49b7-8dad-3b1942d4216c@iis.ee.ethz.ch> References: <971dcf49-55f5-49b7-8dad-3b1942d4216c@iis.ee.ethz.ch> Message-ID: hi, On Fri, Dec 23, 2016 at 11:22 AM, Adam Feigin wrote: > Has anyone managed to get OmniOS bound and working to a FreeIPA (version > 4.4 LDAP) server ? > > So far, I've managed to get it to bind correctly, I get kerberos > tickets without problems, and I can see entries with ldaplist/getent/id > but actual logins do not work, either console or ssh > > These pages were vaguely helpful > https://asenjo.nl/wiki/index.php/Omnios_ipa_client > http://etcfstab.com/oraclelinux/solaris_n_freeipa.html > When I wrote the first link I really just used omnios as a file server (NFS). So ipa users can mount the shares, we can apply ace's, etc. I realize the title is a bit unclear about it, I will modify the page. As to your question: did you try using pam_ldap.so.1 or pam_krb5.so.1 in /etc/pam.conf (take a look at https://wiki.openindiana.org/oi/Kerberos+and+LDAP)? Hopefully it will work, do let me know. -- regards, Natxo -------------- next part -------------- An HTML attachment was scrubbed... URL: From bauernfeind at ipk-gatersleben.de Thu Dec 29 23:18:28 2016 From: bauernfeind at ipk-gatersleben.de (Jens Bauernfeind) Date: Thu, 29 Dec 2016 23:18:28 +0000 Subject: [OmniOS-discuss] ms.omniti.com Publisher tuntap manifest missing Message-ID: Hello, the tuntap package from ms.omniti.com is missing the manifest: pkg info -r -g http://pkg.omniti.com/omniti-ms/ms.omniti.com tuntap pkg: http protocol error: code: 404 reason: Not Found URL: 'http://pkg.omniti.com/omniti-ms/ms.omniti.com/manifest/0/omniti%2Fnetwork%2Ftuntap at 1.3.3%2C5.11-0.151014%3A20161213T171835Z' (happened 4 times) Greetings Jens -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimklimov at cos.ru Sat Dec 31 11:55:43 2016 From: jimklimov at cos.ru (Jim Klimov) Date: Sat, 31 Dec 2016 12:55:43 +0100 Subject: [OmniOS-discuss] ipadm: unknown subcommand 'create-ipmp' In-Reply-To: References: <86696f70-d081-8d6d-8a47-691e5beeebf7@exitas.be> Message-ID: 23 ??????? 2016??. 21:34:25 CET, Willems Dirk ?????: >Thank you Peter for explaining. > >Normally I also use only aggregation, but was wondering when like you >said if the switch is not supporting it. > >I met Solaris 4 years ago and loved the system but the visions from >Oracle don't reflect on mine and with the hoax of Solaris 12, I've >decided that all my energy goes to illumos and where I can I will help. > >I hope I will met you guy's on 4 and 5 Feb on Brussels, I'm very >excited for talking to you. > >Btw: Your jkstat helped me a couple of times for troubleshooting really >great Tool !!! > >Thank you very much. > >Kind Regards > >Dirk > > >On 23-12-16 21:14, Peter Tribble wrote: >On Fri, Dec 23, 2016 at 7:41 PM, Willems Dirk >> wrote: > >Hello OmniOS, > > >I tried to create an ipmp group ipmp0> but it seems it's not there ? > >I get ipadm: unknown subcommand 'create-ipmp' > >Tried also with add-ipmp the same error, and in the man I don't see >anything about ipmp ? > >How do you guy's make an ipmp group or only use aggregraat ? > >Configuring IPMP in OmniOS is done like Solaris 10 (which involves much >fiddling with /etc/hostname.* files), not like Solaris 11 (which your >ipadm >command would be correct for). > >I have old servers (which I didn't set up) using IPMP; my newer systems >use link aggregations which I've always found *much* easier, but it >does need >support on the switch side. > >And what about dlmp is there something for the future ? > >Again, I believe that dlmp is something that Oracle Solaris 11 has, >we just have regular link aggregation. > > >Thank you. > > >Kind Regards, > > >Dirk > >-- >[cid:part2.D6F4FBC7.5E906549 at exitas.be] > > >Dirk Willems >System Engineer > > > >[cid:part4.1EF4E285.60C8F2FC at exitas.be] > >+32 (0)3 443 12 38 > >[cid:part6.C8731DB4.F60CC461 at exitas.be] > >dirk.willems at exitas.be > >[cid:part9.8B18CDA5.4EC9A106 at exitas.be] > >Veldkant 31 - 2550 Kontich > >[cid:part11.FBB03E2C.6DFF68FB at exitas.be] > >www.exitas.be > > >Disclaimer > > >_______________________________________________ >OmniOS-discuss mailing list >OmniOS-discuss at lists.omniti.com >http://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > >-- >-Peter Tribble >http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ > > > >------------------------------------------------------------------------ > >_______________________________________________ >OmniOS-discuss mailing list >OmniOS-discuss at lists.omniti.com >http://lists.omniti.com/mailman/listinfo/omnios-discuss FWIW, I set up ipmp on an OI laptop once, trying to have a virtual interface that stands for 'currently active connection media' (wifi, eth, or virtual eth when dualbooted as a virtual OS from a neighboring other OS) so there is some single logical interface for configs that I can bind services and zones to. The setup is now in another house, so i can't say OTOH if I got vnics to work over that too - but remember at least trying to and swearing that it could be better and friendlier integrated via CLI tools rather than editing dladm.conf and rebooting ;) Jim -- Typos courtesy of K-9 Mail on my Samsung Android From daleg at omniti.com Sat Dec 31 17:36:04 2016 From: daleg at omniti.com (Dale Ghent) Date: Sat, 31 Dec 2016 12:36:04 -0500 Subject: [OmniOS-discuss] [ANN] Updates for 014, 018, 020, Bloody Message-ID: <730FB7A2-CFD8-4718-AFC9-F58FFDA9DEEC@omniti.com> Hello, Updates have been published for the following versions of OmniOS: r151014 (LTS) r151018 (Previous Stable) r151020 (Current Stable) r151021 (Bloody) These updates provide minor security updates in tmpfs and procfs, and also adds support for NICs using the Chelsio Terminator 5 10/40Gb ASIC in the cxgbe driver. As these are updates to the kernel, they do require a reboot in order for the new BE to become active. Per the usual, the new packages may be applied using: 'pkg update' On behalf of the OmniOS team and OmniTI, I wish you a happy New Year! /dale From daleg at omniti.com Sat Dec 31 18:15:43 2016 From: daleg at omniti.com (Dale Ghent) Date: Sat, 31 Dec 2016 13:15:43 -0500 Subject: [OmniOS-discuss] ms.omniti.com Publisher tuntap manifest missing In-Reply-To: References: Message-ID: Hello, Jens Just closing the loop on this - the tuntap driver is now part of OmniOS-proper, from 014 onwards. As such, the tuntap package in the ms.omniti.com repo has been removed, and I've corrected the issue you reported. Thanks /dale > On Dec 29, 2016, at 6:18 PM, Jens Bauernfeind wrote: > > Hello, the tuntap package from ms.omniti.com is missing the manifest: > pkg info -r -g http://pkg.omniti.com/omniti-ms/ms.omniti.com tuntap > pkg: http protocol error: code: 404 reason: Not Found > URL: 'http://pkg.omniti.com/omniti-ms/ms.omniti.com/manifest/0/omniti%2Fnetwork%2Ftuntap at 1.3.3%2C5.11-0.151014%3A20161213T171835Z' (happened 4 times) > > Greetings > Jens > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss