From kloczko.tomasz at gmail.com Tue Aug 1 11:18:30 2017 From: kloczko.tomasz at gmail.com (=?UTF-8?Q?Tomasz_K=C5=82oczko?=) Date: Tue, 1 Aug 2017 12:18:30 +0100 Subject: [OmniOS-discuss] Omios, hvm and AWS In-Reply-To: <69e3cbfe-4cc4-d630-b953-133cc0be8aab@scluk.com> References: <530a2705-2a3f-05a1-68f0-f3b83d695be4@scluk.com> <88df57e7-1849-5d65-6137-587c57940974@scluk.com> <16c1350b-7284-e4f6-40ad-1a66b03b484a@scluk.com> <69e3cbfe-4cc4-d630-b953-133cc0be8aab@scluk.com> Message-ID: I'll share my method of importing images :) AWS API provides uploading VHD image (for some reasons using other formats is not working). All what you need is create such image. On top of the Solaris is it quite easy. All what you need is VBox. Such method is quite handy because using VboxManage command is possible to create, setup blank VM and boot it in batch mode. Below is fragment of my script which could be used as template. It is for install Linux inside but it can be adapted to install any OS (Solaris as well) -- # http://www.perkin.org.uk/posts/create-virtualbox-vm-from-the-command-line.html VBoxManage setproperty hwvirtexclusive off VM=$1 MAC_ADDR="$2" echo "Unregister $VM" VBoxManage unregistervm $VM \ --delete rm -rf $VM.vhd echo "Create $VM.vhd image" VBoxManage createmedium disk \ --size 5120 \ --format VHD \ --filename $VM.vhd echo "Register $VM.vmdk image as Linux_64 VM" VBoxManage createvm \ --name $VM \ --ostype "Linux_64" \ --register echo "Add SATA controller to $VM" VBoxManage storagectl $VM \ --name "SATA Controller" \ --add sata \ --controller IntelAHCI VBoxManage storageattach $VM \ --storagectl "SATA Controller" \ --port 0 \ --device 0 \ --type hdd \ --medium $VM.vhd echo "Add APIC" VBoxManage modifyvm $VM --ioapic on echo "Add boot sequence order" VBoxManage modifyvm $VM --boot1 net --boot2 disk echo "Add RAM, VRAM and enable RDP access" VBoxManage modifyvm $VM \ --memory 4096 \ --vram 128 \ --vrde on echo "Create $VM0 VNIC with exact MAC: $MAC_ADDR" dladm create-vnic -l aggr0 -m $MAC_ADDR $VM0 echo "Network card" VBoxManage modifyvm $VM \ --nic1 bridged \ --bridgeadapter1 $VM0 \ --macaddress1 080027f3399d VBoxHeadless -startvm $VM echo "Delete VM0 VNIC" dladm delete-vnic $VM0 echo "Unregister $VM" VBoxManage unregistervm $VM mv $VM.vhd ready ec2-import-instance $VM.vhd ?f VHD -t m3.xlarge -a x86_64 -b myawsbucket -o AKIAIOSFODNN7EXAMPLE ?w wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY -p Linux -- If kickstart file or AI manifest at the end of installation will be powering off VM "VBoxHeadless -startvm $VM" command will be able to finish and next steps can be done in batch mode like uploading just generated image to VMware, OVM, Azure or AWS. BTW ec2-import-instance command: this command is a bit odd because you need to pass two keys. First one is account key and second one is AWS bucket key (even if AWS account has RW access to bucket). http://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#upload-image Real advantage of using this method is sharing the same Linux KS or Solaris AI manifest/profile (or even Windows install profiles) with bare metal installation descriptions in form of native install descriptions. Knowing exact MAC address of the VM used to create exact image is possible on install server side associate those MAC addresses with KS or AI files. So .. you don't need to sit down upside down on you chair or use ISO images :) All what is needed is possible to do in batch mode and/or using regular/native OS install services. kloczek Tomasz K?oczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH * On 31 July 2017 at 21:51, Al Slater wrote: > On 31/07/17 21:30, Eric Sproul wrote: > > On Mon, Jul 31, 2017 at 4:05 PM, Al Slater wrote: > >> One more question though, is there any way to enable an SMF service for > >> the next reboot, but not immediately. Specifically, I want to enable > >> the initial-boot service with a .initialboot file in place, then create > >> a new AMI. > >> > >> I wist to use .initialboot to grab the instance configuration from > >> amazon (hostname, root keys etc) and configure appropriately when the > >> new instance starts. > > > > Hi Al, > > The initial-boot service isn't really suitable for this sort of thing. > > You might want to check out > > pkg://omnios/system/management/ec2-credential which specifically > > handles setting up the credentials at first boot. That could be > > trivially extended[1] to set the system hostname and probably any > > other "standard" thing that operators want. > > > > Eric > > > > [1] https://github.com/omniosorg/omnios-build/blob/master/ > build/ec2-credential/files/install-ec2-credential > > Thanks for the pointer Eric. > > -- > Al Slater > > _______________________________________________ > 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 peter.tribble at gmail.com Tue Aug 1 11:37:53 2017 From: peter.tribble at gmail.com (Peter Tribble) Date: Tue, 1 Aug 2017 12:37:53 +0100 Subject: [OmniOS-discuss] Omios, hvm and AWS In-Reply-To: References: <530a2705-2a3f-05a1-68f0-f3b83d695be4@scluk.com> <88df57e7-1849-5d65-6137-587c57940974@scluk.com> <16c1350b-7284-e4f6-40ad-1a66b03b484a@scluk.com> <69e3cbfe-4cc4-d630-b953-133cc0be8aab@scluk.com> Message-ID: On Tue, Aug 1, 2017 at 12:18 PM, Tomasz K?oczko wrote: > I'll share my method of importing images :) > > AWS API provides uploading VHD image (for some reasons using other formats > is not working). > Works for VMDK as well. With VirtualBox, you get the somewhat misleading "unsupported compression algorithm 0" error, which actually means that the VMDK is in OVA format whereas the AWS API only supports the OVF format. > All what you need is create such image. On top of the Solaris is it quite > easy. All what you need is VBox. > Such method is quite handy because using VboxManage command is possible to > create, setup blank VM and boot it in batch mode. > > Below is fragment of my script which could be used as template. It is for > install Linux inside but it can be adapted to install any OS (Solaris as > well) > Have you tried this with Solaris or illumos? It doesn't work, because the root ZFS pool embeds the physical paths to the disk inside the pool, and the emulated disk devices that VBox provides don't match what comes in an EC2 instance. So yes, you can create an image, but at some point you need to fix the pool to have the correct metadata. > -- > # http://www.perkin.org.uk/posts/create-virtualbox-vm- > from-the-command-line.html > VBoxManage setproperty hwvirtexclusive off > > VM=$1 > MAC_ADDR="$2" > > echo "Unregister $VM" > VBoxManage unregistervm $VM \ > --delete > rm -rf $VM.vhd > > echo "Create $VM.vhd image" > VBoxManage createmedium disk \ > --size 5120 \ > --format VHD \ > --filename $VM.vhd > > echo "Register $VM.vmdk image as Linux_64 VM" > VBoxManage createvm \ > --name $VM \ > --ostype "Linux_64" \ > --register > > echo "Add SATA controller to $VM" > VBoxManage storagectl $VM \ > --name "SATA Controller" \ > --add sata \ > --controller IntelAHCI > > VBoxManage storageattach $VM \ > --storagectl "SATA Controller" \ > --port 0 \ > --device 0 \ > --type hdd \ > --medium $VM.vhd > > echo "Add APIC" > VBoxManage modifyvm $VM --ioapic on > > echo "Add boot sequence order" > VBoxManage modifyvm $VM --boot1 net --boot2 disk > > echo "Add RAM, VRAM and enable RDP access" > VBoxManage modifyvm $VM \ > --memory 4096 \ > --vram 128 \ > --vrde on > > echo "Create $VM0 VNIC with exact MAC: $MAC_ADDR" > dladm create-vnic -l aggr0 -m $MAC_ADDR $VM0 > > echo "Network card" > VBoxManage modifyvm $VM \ > --nic1 bridged \ > --bridgeadapter1 $VM0 \ > --macaddress1 080027f3399d > > VBoxHeadless -startvm $VM > > echo "Delete VM0 VNIC" > dladm delete-vnic $VM0 > > echo "Unregister $VM" > VBoxManage unregistervm $VM > mv $VM.vhd ready > > ec2-import-instance $VM.vhd ?f VHD -t m3.xlarge -a x86_64 -b myawsbucket > -o AKIAIOSFODNN7EXAMPLE ?w wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY -p > Linux > -- > > If kickstart file or AI manifest at the end of installation will be > powering off VM "VBoxHeadless -startvm $VM" command will be able to finish > and next steps can be done in batch mode like uploading just generated > image to VMware, OVM, Azure or AWS. > BTW ec2-import-instance command: this command is a bit odd because you > need to pass two keys. First one is account key and second one is AWS > bucket key (even if AWS account has RW access to bucket). > http://docs.aws.amazon.com/vm-import/latest/userguide/ > vmimport-image-import.html#upload-image > > Real advantage of using this method is sharing the same Linux KS or > Solaris AI manifest/profile (or even Windows install profiles) with bare > metal installation descriptions in form of native install descriptions. > Knowing exact MAC address of the VM used to create exact image is possible > on install server side associate those MAC addresses with KS or AI files. > > So .. you don't need to sit down upside down on you chair or use ISO > images :) > All what is needed is possible to do in batch mode and/or using > regular/native OS install services. > > kloczek > > Tomasz K?oczko | Tel: 0774 1209067 | LinkedIn: *http://lnkd.in/FXPWxH > * > > On 31 July 2017 at 21:51, Al Slater wrote: > >> On 31/07/17 21:30, Eric Sproul wrote: >> > On Mon, Jul 31, 2017 at 4:05 PM, Al Slater wrote: >> >> One more question though, is there any way to enable an SMF service for >> >> the next reboot, but not immediately. Specifically, I want to enable >> >> the initial-boot service with a .initialboot file in place, then create >> >> a new AMI. >> >> >> >> I wist to use .initialboot to grab the instance configuration from >> >> amazon (hostname, root keys etc) and configure appropriately when the >> >> new instance starts. >> > >> > Hi Al, >> > The initial-boot service isn't really suitable for this sort of thing. >> > You might want to check out >> > pkg://omnios/system/management/ec2-credential which specifically >> > handles setting up the credentials at first boot. That could be >> > trivially extended[1] to set the system hostname and probably any >> > other "standard" thing that operators want. >> > >> > Eric >> > >> > [1] https://github.com/omniosorg/omnios-build/blob/master/build/ >> ec2-credential/files/install-ec2-credential >> >> Thanks for the pointer Eric. >> >> -- >> Al Slater >> >> _______________________________________________ >> 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 > > -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kloczko.tomasz at gmail.com Tue Aug 1 11:56:04 2017 From: kloczko.tomasz at gmail.com (=?UTF-8?Q?Tomasz_K=C5=82oczko?=) Date: Tue, 1 Aug 2017 12:56:04 +0100 Subject: [OmniOS-discuss] Omios, hvm and AWS In-Reply-To: References: <530a2705-2a3f-05a1-68f0-f3b83d695be4@scluk.com> <88df57e7-1849-5d65-6137-587c57940974@scluk.com> <16c1350b-7284-e4f6-40ad-1a66b03b484a@scluk.com> <69e3cbfe-4cc4-d630-b953-133cc0be8aab@scluk.com> Message-ID: On 1 August 2017 at 12:37, Peter Tribble wrote: [..] > All what you need is create such image. On top of the Solaris is it quite >> easy. All what you need is VBox. >> Such method is quite handy because using VboxManage command is possible >> to create, setup blank VM and boot it in batch mode. >> >> Below is fragment of my script which could be used as template. It is for >> install Linux inside but it can be adapted to install any OS (Solaris as >> well) >> > > Have you tried this with Solaris or illumos? > As client OS inside VM? No. > It doesn't work, because the root ZFS pool embeds the physical paths > to the disk inside the pool, and the emulated disk devices that VBox > provides don't match what comes in an EC2 instance. So yes, you can > create an image, but at some point you need to fix the pool to have the > correct metadata. > Still it should be possible to do this somehow after detaching image from VBox and uploading it to AWS bucket or by emulate the same physical path inside VBox instance. IIRC in vmdk image effective image starts from offset 32256 so it should be possible to extract it using dd command -> attach extracted image over lofiadm and import rpool -> correct rpool path -> join corrected image with vmdk header. Do you know what exactly needs to be corrected or what is wrong with this physical path to disk inside zpool? kloczek -- Tomasz K?oczko | LinkedIn: http://lnkd.in/FXPWxH -------------- next part -------------- An HTML attachment was scrubbed... URL: From grzempek at gmail.com Tue Aug 1 19:47:48 2017 From: grzempek at gmail.com (Krzysztof Grzempa) Date: Tue, 1 Aug 2017 21:47:48 +0200 Subject: [OmniOS-discuss] Fwd: OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> Message-ID: ---------- Forwarded message ---------- From: Krzysztof Grzempa Date: 2017-08-01 21:47 GMT+02:00 Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH To: Andries Annema Hi All, @Jens @Davide @Andries I followed your ideas but no go for me.. root at mojvps:/root# pkg install pkg:/package/pkg No updates necessary for this image. root at mojvps:/root# pkg update -nv Creating Plan (Running solver): | pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0. 151022:20170510T210757Z pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151022: 20170510T212740Z pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11- 0.151022:20170511T001737Z Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. root at mojvps:/root# pkg update -nv entire No updates available for this image. root at mojvps:/root# pkg install -nv entire No updates necessary for this image. Regards, Chris 2017-07-31 19:54 GMT+02:00 Andries Annema : > Could this be in any way related to the issue I reported recently ( > http://lists.omniti.com/pipermail/omnios-discuss/2017-July/009079.html) > where I tried to run "pkglint" in order to prepare an IPS package and got a > "MemoryError" with the specific statement that "This is an internal error > in pkg(5) version ..."? > > Not sure if it does, because I got this error on a freshly installed > r151022 "vanilla" system, so no upgrade from r151014 or anything. Also, if > I run "pkg install pkg:/package/pkg" now on that system, it responds with > "No updates necessary for this image", so I doubt it is really related. > However, I couldn't help but ask, as I haven't received any response on > the other matter yet and both are related to "pkg"... > > Andries > > On 2017-07-31 17:14, Davide Poletto wrote: > > Hello all, just a follow up about the upgrade from OmniOS r151014 to > OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my > case...the only additional step it required before the final pkg update > -rv documented step (so the system was still on OmniOS r151022) was the > mandatory update of pkg(5) package: > > /usr/bin/pkg update -rv > WARNING: pkg(5) appears to be out of date, and should be updated before > running update. Please update pkg(5) by executing 'pkg install > pkg:/package/pkg' as a privileged user and then retry the update. > > root at nas01:~# pkg install pkg:/package/pkg > Packages to update: 1 > Create boot environment: No > Create backup boot environment: Yes > > DOWNLOAD PKGS FILES XFER (MB) > SPEED > Completed 1/1 42/42 1.2/1.2 > 430k/s > > PHASE ITEMS > Removing old actions 1/1 > Installing new actions 1/1 > Updating modified actions 43/43 > Updating package state database Done > Updating package cache 1/1 > Updating image state Done > Creating fast lookup database Done > Reading search index Done > Updating search index 1/1 > Updating package cache 1/1 > > I'm pretty sure that, when the system still was on OmniOS r151022 (so when > the publisher was still pkg.omniti.com/omnios/r151022/), the system was > also fully up-to-date...I remember I did a pkg update -nv to check its > status...but no updates were necessary (so the pkg(5) update's > requirement reported above probably is a direct consequence of the > publisher repository change from pkg.omniti.com/omnios/r151022/ to > pkg.omniosce.org/r151022/core/ which is the mandatory step prior of the > final pkg update -rv command execution). > > Worth to mention that additional step on the > https://github.com/omniosorg/omnios-build/blob/r151022/doc/R > eleaseNotes.md#upgrading-from-omniti-released-r151022 paragraph? > > Davide. > > On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa > wrote: > >> Hello Jens >> Currenty im out of home. >> I will try it out tommorow and report results... >> >> Thanks >> Chris >> >> 29.07.2017 00:28 "Jens Bauernfeind" >> napisa?(a): >> >>> Hi, >>> >>> what happens when you just try to update entire? >>> pkg update -nv entire >>> or >>> pkg install -nv entire >>> >>> Best Regards, >>> Jens >>> ________________________________________ >>> From: OmniOS-discuss [omnios-discuss-bounces at lists.omniti.com] on >>> behalf of Krzysztof Grzempa [grzempek at gmail.com] >>> Sent: Friday, July 28, 2017 10:50 >>> To: omnios-discuss at lists.omniti.com >>> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from >>> SunSSH to OpenSSH >>> >>> HI, >>> So, any other ideas ? I would like to avoid plain new installation >>> scenario :) >>> >>> Regards, >>> Kris >>> >>> 2017-07-28 1:29 GMT+02:00 Dan McDonald >> @kebe.com>>: >>> Yeah that's right. Sorry -- had to ask. >>> >>> Dan >>> >>> Sent from my iPhone (typos, autocorrect, and all) >>> >>> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa >> > wrote: >>> >>> Hi Dan, >>> I had done prerequsities before i started: >>> >>> root at mojvps:/root# pkg list -v ca-bundle >>> FMRI >>> IFO >>> pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z >>> i-- >>> >>> there is 'April' certificates..right ? >>> >>> Kris >>> >>> 2017-07-27 22:28 GMT+02:00 Dan McDonald >> @kebe.com>>: >>> You're sure you're on the very latest 014? Could be lack of updated >>> certificates... >>> >>> Dan >>> >>> Sent from my iPhone (typos, autocorrect, and all) >>> >>> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa >> > wrote: >>> >>> Guys, >>> I will grab this thread as it is somehow similiar. I want to upgrade >>> from r151014 to r151022. I went throught all steps of: >>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>> but when Im performing upgrade: >>> >>> # /usr/bin/pkg update --be-name r151022 >>> >>> i got: >>> >>> root at mojvps:/root# /usr/bin/pkg update --be-name r151022 >>> Creating Plan (Running solver): | >>> pkg update: No solution was found to satisfy constraints >>> Plan Creation: Package solver has not found a solution to update to >>> latest available versions. >>> This may indicate an overly constrained set of packages are installed. >>> >>> latest incorporations: >>> >>> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >>> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.15102 >>> 2:20170510T210757Z >>> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11, >>> 5.11-0.151022:20170510T212740Z >>> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.15 >>> 1022:20170511T001737Z >>> Dependency analysis is unable to determine exact cause. >>> Try specifying expected results to obtain more detailed error messages. >>> >>> >>> I set publisher correctly IHMO: >>> >>> root at mojvps:/root# pkg publisher >>> PUBLISHER TYPE STATUS P LOCATION >>> omnios origin online F >>> https://pkg.omniti.com/omnios/r151022/ >>> >>> >>> Any ideas ? >>> >>> I want to upgrade to CE after that. >>> >>> Thanks in advance >>> Kris >>> >>> 2017-07-24 17:01 GMT+02:00 Davide Poletto >> to:davide.poletto at gmail.com>>: >>> Thanks Andy, thanks Peter. >>> >>> So now OpenSSH is installed: >>> >>> root at nas01:/root# pkg list | grep ssh >>> network/openssh 7.4.1-0.151014 >>> i-- >>> network/openssh-server 7.4.1-0.151014 >>> i-- >>> root at nas01:/root# ssh -V >>> OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017 >>> >>> Totally my fault in not following the right Release Notes (I thought I >>> should have followed the destination version - r151022 - Release Notes >>> instead the one from where the upgrade process has to start, r151014 in my >>> case). >>> >>> Thanks again for pointing me on the right track. >>> >>> Best regards, Davide. >>> >>> On Mon, Jul 24, 2017 at 4:21 PM, Peter Tribble >> > wrote: >>> >>> >>> On Mon, Jul 24, 2017 at 2:56 PM, Davide Poletto < >>> davide.poletto at gmail.com> wrote: >>> Hello all, >>> >>> I'm facing a strange issue on a pretty standard OmniOS r151014 LTS box >>> fully updated (only Global Zone), following the "Upgrading to r151022" >>> instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>> required before any jump to OmniOS r151022 (my final target is OmniOS >>> Community Edition r151022i) I found that I'm unable to switch to OpenSSH as >>> per "Upgrading to OpenSSH from SunSSH" instructions on the same page: >>> >>> executing the suggested command: >>> >>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>> pkg:/service/network/ssh --reject pkg:/service/network/ssh-common >>> pkg:/network/openssh pkg:/network/openssh-server >>> >>> fails with the message: >>> >>> pkg install: The following pattern(s) did not match any allowable >>> packages. Try >>> using a different matching pattern, or refreshing publisher information: >>> >>> pkg:/service/network/ssh-common >>> >>> The r151014 release notes >>> >>> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 >>> >>> say >>> >>> /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject >>> pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh >>> pkg:/network/openssh pkg:/network/openssh-server >>> >>> Blindly I tried to omit the specific "ssh-common" package reject >>> >>> I think you were on the right track. >>> >>> but the result is not conforting me (maybe I tried a command in a >>> totally wrong way not understanding what the --reject options really mean): >>> >>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>> pkg:/service/network/ssh --reject pkg:/network/openssh >>> pkg:/network/openssh-server >>> >>> I think you have an extra --reject in there, so you've told it not to >>> install openssh. >>> >>> -- >>> -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 >>> >>> >>> _______________________________________________ >>> 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 >> >> > > > _______________________________________________ > OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://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 gearboxes at outlook.com Thu Aug 3 15:50:32 2017 From: gearboxes at outlook.com (Machine Man) Date: Thu, 3 Aug 2017 15:50:32 +0000 Subject: [OmniOS-discuss] Encryption options Message-ID: Currently I have a few of deployments of OmniOS at remote sites hosing 2 - 7 VMs per site and replicate snapshots of the VMs to a central server at a hosting location. My customers are starting to get pressure that the local and backup data is not encrypted at rest and its becoming critical for them to take on new clients. I know lofi is an option, but I don't know how replicating incremental snapshots is going to work and also it looks like I will have to switch to files for the VMs instead of using block volumes. Does KVM on IllumOS support TPM? I also cant really find any info on this. I dont use ZFS dedup and have no plans really either. Any feedback is appreciated. Sent from Windows Mail -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimklimov at cos.ru Thu Aug 3 17:07:30 2017 From: jimklimov at cos.ru (Jim Klimov) Date: Thu, 03 Aug 2017 17:07:30 +0000 Subject: [OmniOS-discuss] Encryption options In-Reply-To: References: Message-ID: <7A50E907-47DA-477A-BE6C-C067949BAEFE@cos.ru> On August 3, 2017 5:50:32 PM GMT+02:00, Machine Man wrote: >Currently I have a few of deployments of OmniOS at remote sites hosing >2 - 7 VMs per site and replicate snapshots of the VMs to a central >server at a hosting location. >My customers are starting to get pressure that the local and backup >data is not encrypted at rest and its becoming critical for them to >take on new clients. > >I know lofi is an option, but I don't know how replicating incremental >snapshots is going to work and also it looks like I will have to switch >to files for the VMs instead of using block volumes. > >Does KVM on IllumOS support TPM? I also cant really find any info on >this. I dont use ZFS dedup and have no plans really either. > >Any feedback is appreciated. > >Sent from Windows Mail Just wondering: is it an option to have an encrypted lofi in a zfs volume, as the block device for VM storage? Then it's replication of snapshots of this volume, keys not included. For files, you can always dedicate a filesystem dataset per VM (configs, disks, etc) and snapshot/replicate that, individually. -- Typos courtesy of K-9 Mail on my Android From gearboxes at outlook.com Fri Aug 4 00:32:07 2017 From: gearboxes at outlook.com (Machine Man) Date: Fri, 4 Aug 2017 00:32:07 +0000 Subject: [OmniOS-discuss] Encryption options In-Reply-To: <7A50E907-47DA-477A-BE6C-C067949BAEFE@cos.ru> References: , <7A50E907-47DA-477A-BE6C-C067949BAEFE@cos.ru> Message-ID: I didn?t spend too much time researching using lofi as a block device, there isn't much info either. Now add zones to mix since the destination side is zones and no information is available. Encryption remains this stumbling block that seems to be getting bigger and bigger every year based on requirements. I ill have to spend ample time with lofi on my test gear and try to figure something out. Sent from my Windows 10 phone From: Jim Klimov Sent: Thursday, August 3, 2017 13:12 To: omnios-discuss at lists.omniti.com; Machine Man; omnios-discuss at lists.omniti.com Subject: Re: [OmniOS-discuss] Encryption options On August 3, 2017 5:50:32 PM GMT+02:00, Machine Man wrote: >Currently I have a few of deployments of OmniOS at remote sites hosing >2 - 7 VMs per site and replicate snapshots of the VMs to a central >server at a hosting location. >My customers are starting to get pressure that the local and backup >data is not encrypted at rest and its becoming critical for them to >take on new clients. > >I know lofi is an option, but I don't know how replicating incremental >snapshots is going to work and also it looks like I will have to switch >to files for the VMs instead of using block volumes. > >Does KVM on IllumOS support TPM? I also cant really find any info on >this. I dont use ZFS dedup and have no plans really either. > >Any feedback is appreciated. > >Sent from Windows Mail Just wondering: is it an option to have an encrypted lofi in a zfs volume, as the block device for VM storage? Then it's replication of snapshots of this volume, keys not included. For files, you can always dedicate a filesystem dataset per VM (configs, disks, etc) and snapshot/replicate that, individually. -- Typos courtesy of K-9 Mail on my Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobi at oetiker.ch Sun Aug 6 20:35:04 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Sun, 6 Aug 2017 22:35:04 +0200 (CEST) Subject: [OmniOS-discuss] ANNOUNCEMENT OmniOSce r151022l Message-ID: <1164617175.811061.1502051704593.JavaMail.zimbra@oetiker.ch> Dear All This is the weekly update for w/c 7th of August 2017 and contains NO security updates but several bugfixes from upstream illumos and joyent lx. For this update, a reboot is required. We are aware that system reboots pose a problem for many sites, so we are investigating ways to reduce the requirements of reboots associated with update releases of OmniOSce. More on this next week. Any problems or questions, please get in touch via the Lobby at https://gitter.im/omniosorg/Lobby Full release notes can be found at https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md To upgrade, utter: pkg update -r --be-name=r151022l cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gearboxes at outlook.com Thu Aug 10 23:26:13 2017 From: gearboxes at outlook.com (Machine Man) Date: Thu, 10 Aug 2017 23:26:13 +0000 Subject: [OmniOS-discuss] Virtual USB media boot order Message-ID: When I add a USB disk from an image it always shows up as the 1st disk so the boot order using "c" will always select USB. How do I boot from the 1st hard drive without disconnecting USB? -device piix3-usb-uhci,id=uhci \ -drive file=$HDD1,if=virtio,index=0 \ -drive file=$HDD2,if=virtio,index=1 \ -drive file=$CD1,media=cdrom,if=ide,index=2 \ -drive file=$CD2,media=cdrom,if=ide,index=3 \ -drive if=none,id=usb_stick,file=/rpool/virtualmachines/qa-tableau04/usb.img,index=4 \ -device usb-storage,bus=uhci.0,drive=usb_stick \ I have also tried with using the bootindex option in -device but it seems that you have to use -boot "strict" option which is not supported in Illumos. Using the -boot "menu=on" option I can select the correct boot device, but at a loss why index doesnt work and also attaching drives with -device so that I can use the bootindex option doesnt make a difference. I am starting to get the feeling that some aspects may be hard coded. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobi at oetiker.ch Fri Aug 11 18:46:37 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Fri, 11 Aug 2017 20:46:37 +0200 (CEST) Subject: [OmniOS-discuss] ANNOUNCEMENT - OmniOS r151022m - Security Update! Message-ID: <1048852290.999958.1502477197634.JavaMail.zimbra@oetiker.ch> OmniOS Community Edition is releasing OmniOS r151022m three days early as this is an urgent security release. The release contains new versions of git and hg to fix CVE-2017-1000117 CVE-2017-1000116 CVE-2017-1000115 see http://blog.recurity-labs.com/2017-08-10/scm-vulns for details on the vulnerabilities. This release does NOT require a reboot. Full release notes can be found at https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md To upgrade, utter: $ pkg update -r You can also just upgrade the packages $ pkg update -r git mercurial cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 From illumos at cucumber.demon.co.uk Fri Aug 11 21:11:35 2017 From: illumos at cucumber.demon.co.uk (Andrew Gabriel) Date: Fri, 11 Aug 2017 22:11:35 +0100 Subject: [OmniOS-discuss] ANNOUNCEMENT - OmniOS r151022m - Security Update! In-Reply-To: <1048852290.999958.1502477197634.JavaMail.zimbra@oetiker.ch> References: <1048852290.999958.1502477197634.JavaMail.zimbra@oetiker.ch> Message-ID: <59d202f1-005d-d3ba-dafb-6e2af63e0cc0@cucumber.demon.co.uk> Wow - that was fast! On 11/08/2017 19:46, Tobias Oetiker wrote: > OmniOS Community Edition is releasing OmniOS r151022m three days early as this is an urgent security release. The release contains new versions of git and hg to fix > > CVE-2017-1000117 > CVE-2017-1000116 > CVE-2017-1000115 > > see http://blog.recurity-labs.com/2017-08-10/scm-vulns for details > on the vulnerabilities. > > This release does NOT require a reboot. > > Full release notes can be found at > > https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md > > To upgrade, utter: > > $ pkg update -r > > You can also just upgrade the packages > > $ pkg update -r git mercurial > > cheers > tobi > From grzempek at gmail.com Sat Aug 12 12:16:25 2017 From: grzempek at gmail.com (Krzysztof Grzempa) Date: Sat, 12 Aug 2017 14:16:25 +0200 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> Message-ID: Guys, Do you have any other ideas why i cannot upgrade to the damn r151022 or any steps i can do to figure it out? Below please find full command log of my upgrade process: root at mojvps:/root# pkg list | grep ssh network/openssh 7.4.1-0.151014 i-- network/openssh-server 7.4.1-0.151014 i-- root at mojvps:/root# pkg publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F http://pkg.omniti.com/omnios/r151014/ root at mojvps:/root# pkg list -v ca-bundle FMRI IFO pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z i-- root at mojvps:/root# pkg refresh --full root at mojvps:/root# pkg update -nv No updates available for this image. root at mojvps:/root# beadm list BE Active Mountpoint Space Policy Created omnios - - 3,67M static 2017-04-05 17:29 omniosvar - - 19,0K static 2017-04-05 17:29 update_07042017 NR / 4,86G static 2017-04-07 20:40 update_07042017-backup-1 - - 237K static 2017-07-27 21:36 upgrade_from_r151014_backup - - 243K static 2017-07-27 21:56 update_07042017-backup-2 - - 297K static 2017-08-02 20:06 update_07042017-backup-3 - - 308K static 2017-08-12 14:05 upgrade_from_r151014_backup2 - - 315K static 2017-08-12 14:07 root at mojvps:/root# beadm create upgrade_from_r151014_backup3 Created successfully root at mojvps:/root# /usr/bin/pkg set-publisher -G http://pkg.omniti.com/omnios/r151014/ -g https://pkg.omniti.com/omnios/r151022/ omnios root at mojvps:/root# pkg publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniti.com/omnios/r151022/ root at mojvps:/root# /usr/bin/pkg update --be-name r151022 Creating Plan (Running solver): - pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://omnios/incorporation/jeos/illumos-gate at 11 ,5.11-0.151022:20170510T210757Z pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11 ,5.11-0.151022:20170510T212740Z pkg://omnios/incorporation/jeos/omnios-userland at 11 ,5.11-0.151022:20170511T001737Z pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. 2017-08-01 21:47 GMT+02:00 Krzysztof Grzempa : > > ---------- Forwarded message ---------- > From: Krzysztof Grzempa > Date: 2017-08-01 21:47 GMT+02:00 > Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH > to OpenSSH > To: Andries Annema > > > Hi All, > @Jens @Davide @Andries > > I followed your ideas but no go for me.. > > root at mojvps:/root# pkg install pkg:/package/pkg > No updates necessary for this image. > root at mojvps:/root# pkg update -nv > Creating Plan (Running solver): | > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest > available versions. > This may indicate an overly constrained set of packages are installed. > > latest incorporations: > > pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.15102 > 2:20170510T210757Z > pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11, > 5.11-0.151022:20170510T212740Z > pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0. > 151022:20170511T001737Z > Dependency analysis is unable to determine exact cause. > Try specifying expected results to obtain more detailed error messages. > > root at mojvps:/root# pkg update -nv entire > No updates available for this image. > root at mojvps:/root# pkg install -nv entire > No updates necessary for this image. > > > Regards, > Chris > > 2017-07-31 19:54 GMT+02:00 Andries Annema : > >> Could this be in any way related to the issue I reported recently ( >> http://lists.omniti.com/pipermail/omnios-discuss/2017-July/009079.html) >> where I tried to run "pkglint" in order to prepare an IPS package and got a >> "MemoryError" with the specific statement that "This is an internal error >> in pkg(5) version ..."? >> >> Not sure if it does, because I got this error on a freshly installed >> r151022 "vanilla" system, so no upgrade from r151014 or anything. Also, if >> I run "pkg install pkg:/package/pkg" now on that system, it responds with >> "No updates necessary for this image", so I doubt it is really related. >> However, I couldn't help but ask, as I haven't received any response on >> the other matter yet and both are related to "pkg"... >> >> Andries >> >> On 2017-07-31 17:14, Davide Poletto wrote: >> >> Hello all, just a follow up about the upgrade from OmniOS r151014 to >> OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my >> case...the only additional step it required before the final pkg update >> -rv documented step (so the system was still on OmniOS r151022) was the >> mandatory update of pkg(5) package: >> >> /usr/bin/pkg update -rv >> WARNING: pkg(5) appears to be out of date, and should be updated before >> running update. Please update pkg(5) by executing 'pkg install >> pkg:/package/pkg' as a privileged user and then retry the update. >> >> root at nas01:~# pkg install pkg:/package/pkg >> Packages to update: 1 >> Create boot environment: No >> Create backup boot environment: Yes >> >> DOWNLOAD PKGS FILES XFER >> (MB) SPEED >> Completed 1/1 42/42 1.2/1.2 >> 430k/s >> >> PHASE ITEMS >> Removing old actions 1/1 >> Installing new actions 1/1 >> Updating modified actions 43/43 >> Updating package state database Done >> Updating package cache 1/1 >> Updating image state Done >> Creating fast lookup database Done >> Reading search index Done >> Updating search index 1/1 >> Updating package cache 1/1 >> >> I'm pretty sure that, when the system still was on OmniOS r151022 (so >> when the publisher was still pkg.omniti.com/omnios/r151022/), the system >> was also fully up-to-date...I remember I did a pkg update -nv to check its >> status...but no updates were necessary (so the pkg(5) update's >> requirement reported above probably is a direct consequence of the >> publisher repository change from pkg.omniti.com/omnios/r151022/ to >> pkg.omniosce.org/r151022/core/ which is the mandatory step prior of the >> final pkg update -rv command execution). >> >> Worth to mention that additional step on the >> https://github.com/omniosorg/omnios-build/blob/r151022/doc/R >> eleaseNotes.md#upgrading-from-omniti-released-r151022 paragraph? >> >> Davide. >> >> On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa >> wrote: >> >>> Hello Jens >>> Currenty im out of home. >>> I will try it out tommorow and report results... >>> >>> Thanks >>> Chris >>> >>> 29.07.2017 00:28 "Jens Bauernfeind" >>> napisa?(a): >>> >>>> Hi, >>>> >>>> what happens when you just try to update entire? >>>> pkg update -nv entire >>>> or >>>> pkg install -nv entire >>>> >>>> Best Regards, >>>> Jens >>>> ________________________________________ >>>> From: OmniOS-discuss [omnios-discuss-bounces at lists.omniti.com] on >>>> behalf of Krzysztof Grzempa [grzempek at gmail.com] >>>> Sent: Friday, July 28, 2017 10:50 >>>> To: omnios-discuss at lists.omniti.com >>>> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from >>>> SunSSH to OpenSSH >>>> >>>> HI, >>>> So, any other ideas ? I would like to avoid plain new installation >>>> scenario :) >>>> >>>> Regards, >>>> Kris >>>> >>>> 2017-07-28 1:29 GMT+02:00 Dan McDonald >>> @kebe.com>>: >>>> Yeah that's right. Sorry -- had to ask. >>>> >>>> Dan >>>> >>>> Sent from my iPhone (typos, autocorrect, and all) >>>> >>>> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa >>> > wrote: >>>> >>>> Hi Dan, >>>> I had done prerequsities before i started: >>>> >>>> root at mojvps:/root# pkg list -v ca-bundle >>>> FMRI >>>> IFO >>>> pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z >>>> i-- >>>> >>>> there is 'April' certificates..right ? >>>> >>>> Kris >>>> >>>> 2017-07-27 22:28 GMT+02:00 Dan McDonald >>> @kebe.com>>: >>>> You're sure you're on the very latest 014? Could be lack of updated >>>> certificates... >>>> >>>> Dan >>>> >>>> Sent from my iPhone (typos, autocorrect, and all) >>>> >>>> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa >>> > wrote: >>>> >>>> Guys, >>>> I will grab this thread as it is somehow similiar. I want to upgrade >>>> from r151014 to r151022. I went throught all steps of: >>>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>>> but when Im performing upgrade: >>>> >>>> # /usr/bin/pkg update --be-name r151022 >>>> >>>> i got: >>>> >>>> root at mojvps:/root# /usr/bin/pkg update --be-name r151022 >>>> Creating Plan (Running solver): | >>>> pkg update: No solution was found to satisfy constraints >>>> Plan Creation: Package solver has not found a solution to update to >>>> latest available versions. >>>> This may indicate an overly constrained set of packages are installed. >>>> >>>> latest incorporations: >>>> >>>> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >>>> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.15102 >>>> 2:20170510T210757Z >>>> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11, >>>> 5.11-0.151022:20170510T212740Z >>>> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.15 >>>> 1022:20170511T001737Z >>>> Dependency analysis is unable to determine exact cause. >>>> Try specifying expected results to obtain more detailed error messages. >>>> >>>> >>>> I set publisher correctly IHMO: >>>> >>>> root at mojvps:/root# pkg publisher >>>> PUBLISHER TYPE STATUS P LOCATION >>>> omnios origin online F >>>> https://pkg.omniti.com/omnios/r151022/ >>>> >>>> >>>> Any ideas ? >>>> >>>> I want to upgrade to CE after that. >>>> >>>> Thanks in advance >>>> Kris >>>> >>>> 2017-07-24 17:01 GMT+02:00 Davide Poletto >>> >: >>>> Thanks Andy, thanks Peter. >>>> >>>> So now OpenSSH is installed: >>>> >>>> root at nas01:/root# pkg list | grep ssh >>>> network/openssh 7.4.1-0.151014 >>>> i-- >>>> network/openssh-server 7.4.1-0.151014 >>>> i-- >>>> root at nas01:/root# ssh -V >>>> OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017 >>>> >>>> Totally my fault in not following the right Release Notes (I thought I >>>> should have followed the destination version - r151022 - Release Notes >>>> instead the one from where the upgrade process has to start, r151014 in my >>>> case). >>>> >>>> Thanks again for pointing me on the right track. >>>> >>>> Best regards, Davide. >>>> >>>> On Mon, Jul 24, 2017 at 4:21 PM, Peter Tribble >>> > wrote: >>>> >>>> >>>> On Mon, Jul 24, 2017 at 2:56 PM, Davide Poletto < >>>> davide.poletto at gmail.com> wrote: >>>> Hello all, >>>> >>>> I'm facing a strange issue on a pretty standard OmniOS r151014 LTS box >>>> fully updated (only Global Zone), following the "Upgrading to r151022" >>>> instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>>> required before any jump to OmniOS r151022 (my final target is OmniOS >>>> Community Edition r151022i) I found that I'm unable to switch to OpenSSH as >>>> per "Upgrading to OpenSSH from SunSSH" instructions on the same page: >>>> >>>> executing the suggested command: >>>> >>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>>> pkg:/service/network/ssh --reject pkg:/service/network/ssh-common >>>> pkg:/network/openssh pkg:/network/openssh-server >>>> >>>> fails with the message: >>>> >>>> pkg install: The following pattern(s) did not match any allowable >>>> packages. Try >>>> using a different matching pattern, or refreshing publisher information: >>>> >>>> pkg:/service/network/ssh-common >>>> >>>> The r151014 release notes >>>> >>>> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 >>>> >>>> say >>>> >>>> /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject >>>> pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh >>>> pkg:/network/openssh pkg:/network/openssh-server >>>> >>>> Blindly I tried to omit the specific "ssh-common" package reject >>>> >>>> I think you were on the right track. >>>> >>>> but the result is not conforting me (maybe I tried a command in a >>>> totally wrong way not understanding what the --reject options really mean): >>>> >>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>>> pkg:/service/network/ssh --reject pkg:/network/openssh >>>> pkg:/network/openssh-server >>>> >>>> I think you have an extra --reject in there, so you've told it not to >>>> install openssh. >>>> >>>> -- >>>> -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 >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >> >> >> _______________________________________________ >> OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://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 danmcd at kebe.com Sun Aug 13 01:03:09 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sat, 12 Aug 2017 21:03:09 -0400 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> Message-ID: 1. Add "-v" to your "pig update". Might be silent but at least we can eliminate it. 2. Do "pkg update pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z" and see the complaint (and share it here). Dan Sent from my iPhone (typos, autocorrect, and all) > On Aug 12, 2017, at 8:16 AM, Krzysztof Grzempa wrote: > > Guys, > Do you have any other ideas why i cannot upgrade to the damn r151022 or any steps i can do to figure it out? > Below please find full command log of my upgrade process: > > root at mojvps:/root# pkg list | grep ssh > network/openssh 7.4.1-0.151014 i-- > network/openssh-server 7.4.1-0.151014 i-- > > root at mojvps:/root# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F http://pkg.omniti.com/omnios/r151014/ > > root at mojvps:/root# pkg list -v ca-bundle > FMRI IFO > pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z i-- > > root at mojvps:/root# pkg refresh --full > > root at mojvps:/root# pkg update -nv > No updates available for this image. > > root at mojvps:/root# beadm list > BE Active Mountpoint Space Policy Created > omnios - - 3,67M static 2017-04-05 17:29 > omniosvar - - 19,0K static 2017-04-05 17:29 > update_07042017 NR / 4,86G static 2017-04-07 20:40 > update_07042017-backup-1 - - 237K static 2017-07-27 21:36 > upgrade_from_r151014_backup - - 243K static 2017-07-27 21:56 > update_07042017-backup-2 - - 297K static 2017-08-02 20:06 > update_07042017-backup-3 - - 308K static 2017-08-12 14:05 > upgrade_from_r151014_backup2 - - 315K static 2017-08-12 14:07 > > root at mojvps:/root# beadm create upgrade_from_r151014_backup3 > Created successfully > > root at mojvps:/root# /usr/bin/pkg set-publisher -G http://pkg.omniti.com/omnios/r151014/ -g https://pkg.omniti.com/omnios/r151022/ omnios > > root at mojvps:/root# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F https://pkg.omniti.com/omnios/r151022/ > > root at mojvps:/root# /usr/bin/pkg update --be-name r151022 > Creating Plan (Running solver): - > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest available versions. > This may indicate an overly constrained set of packages are installed. > > latest incorporations: > > pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151022:20170510T210757Z > pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151022:20170510T212740Z > pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151022:20170511T001737Z > > Dependency analysis is unable to determine exact cause. > Try specifying expected results to obtain more detailed error messages. > > > 2017-08-01 21:47 GMT+02:00 Krzysztof Grzempa : >> >> ---------- Forwarded message ---------- >> From: Krzysztof Grzempa >> Date: 2017-08-01 21:47 GMT+02:00 >> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH >> To: Andries Annema >> >> >> Hi All, >> @Jens @Davide @Andries >> >> I followed your ideas but no go for me.. >> >> root at mojvps:/root# pkg install pkg:/package/pkg >> No updates necessary for this image. >> root at mojvps:/root# pkg update -nv >> Creating Plan (Running solver): | >> pkg update: No solution was found to satisfy constraints >> Plan Creation: Package solver has not found a solution to update to latest available versions. >> This may indicate an overly constrained set of packages are installed. >> >> latest incorporations: >> >> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151022:20170510T210757Z >> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151022:20170510T212740Z >> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151022:20170511T001737Z >> Dependency analysis is unable to determine exact cause. >> Try specifying expected results to obtain more detailed error messages. >> >> root at mojvps:/root# pkg update -nv entire >> No updates available for this image. >> root at mojvps:/root# pkg install -nv entire >> No updates necessary for this image. >> >> >> Regards, >> Chris >> >> 2017-07-31 19:54 GMT+02:00 Andries Annema : >>> Could this be in any way related to the issue I reported recently (http://lists.omniti.com/pipermail/omnios-discuss/2017-July/009079.html) where I tried to run "pkglint" in order to prepare an IPS package and got a "MemoryError" with the specific statement that "This is an internal error in pkg(5) version ..."? >>> >>> Not sure if it does, because I got this error on a freshly installed r151022 "vanilla" system, so no upgrade from r151014 or anything. Also, if I run "pkg install pkg:/package/pkg" now on that system, it responds with "No updates necessary for this image", so I doubt it is really related. >>> However, I couldn't help but ask, as I haven't received any response on the other matter yet and both are related to "pkg"... >>> >>> Andries >>> >>>> On 2017-07-31 17:14, Davide Poletto wrote: >>>> Hello all, just a follow up about the upgrade from OmniOS r151014 to OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my case...the only additional step it required before the final pkg update -rv documented step (so the system was still on OmniOS r151022) was the mandatory update of pkg(5) package: >>>> >>>> /usr/bin/pkg update -rv >>>> WARNING: pkg(5) appears to be out of date, and should be updated before >>>> running update. Please update pkg(5) by executing 'pkg install >>>> pkg:/package/pkg' as a privileged user and then retry the update. >>>> >>>> root at nas01:~# pkg install pkg:/package/pkg >>>> Packages to update: 1 >>>> Create boot environment: No >>>> Create backup boot environment: Yes >>>> >>>> DOWNLOAD PKGS FILES XFER (MB) SPEED >>>> Completed 1/1 42/42 1.2/1.2 430k/s >>>> >>>> PHASE ITEMS >>>> Removing old actions 1/1 >>>> Installing new actions 1/1 >>>> Updating modified actions 43/43 >>>> Updating package state database Done >>>> Updating package cache 1/1 >>>> Updating image state Done >>>> Creating fast lookup database Done >>>> Reading search index Done >>>> Updating search index 1/1 >>>> Updating package cache 1/1 >>>> >>>> I'm pretty sure that, when the system still was on OmniOS r151022 (so when the publisher was still pkg.omniti.com/omnios/r151022/), the system was also fully up-to-date...I remember I did a pkg update -nv to check its status...but no updates were necessary (so the pkg(5) update's requirement reported above probably is a direct consequence of the publisher repository change from pkg.omniti.com/omnios/r151022/ to pkg.omniosce.org/r151022/core/ which is the mandatory step prior of the final pkg update -rv command execution). >>>> >>>> Worth to mention that additional step on the https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md#upgrading-from-omniti-released-r151022 paragraph? >>>> >>>> Davide. >>>> >>>>> On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa wrote: >>>>> Hello Jens >>>>> Currenty im out of home. >>>>> I will try it out tommorow and report results... >>>>> >>>>> Thanks >>>>> Chris >>>>> >>>>> 29.07.2017 00:28 "Jens Bauernfeind" napisa?(a): >>>>>> Hi, >>>>>> >>>>>> what happens when you just try to update entire? >>>>>> pkg update -nv entire >>>>>> or >>>>>> pkg install -nv entire >>>>>> >>>>>> Best Regards, >>>>>> Jens >>>>>> ________________________________________ >>>>>> From: OmniOS-discuss [omnios-discuss-bounces at lists.omniti.com] on behalf of Krzysztof Grzempa [grzempek at gmail.com] >>>>>> Sent: Friday, July 28, 2017 10:50 >>>>>> To: omnios-discuss at lists.omniti.com >>>>>> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH >>>>>> >>>>>> HI, >>>>>> So, any other ideas ? I would like to avoid plain new installation scenario :) >>>>>> >>>>>> Regards, >>>>>> Kris >>>>>> >>>>>> 2017-07-28 1:29 GMT+02:00 Dan McDonald >: >>>>>> Yeah that's right. Sorry -- had to ask. >>>>>> >>>>>> Dan >>>>>> >>>>>> Sent from my iPhone (typos, autocorrect, and all) >>>>>> >>>>>> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa > wrote: >>>>>> >>>>>> Hi Dan, >>>>>> I had done prerequsities before i started: >>>>>> >>>>>> root at mojvps:/root# pkg list -v ca-bundle >>>>>> FMRI IFO >>>>>> pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z i-- >>>>>> >>>>>> there is 'April' certificates..right ? >>>>>> >>>>>> Kris >>>>>> >>>>>> 2017-07-27 22:28 GMT+02:00 Dan McDonald >: >>>>>> You're sure you're on the very latest 014? Could be lack of updated certificates... >>>>>> >>>>>> Dan >>>>>> >>>>>> Sent from my iPhone (typos, autocorrect, and all) >>>>>> >>>>>> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa > wrote: >>>>>> >>>>>> Guys, >>>>>> I will grab this thread as it is somehow similiar. I want to upgrade from r151014 to r151022. I went throught all steps of: >>>>>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>>>>> but when Im performing upgrade: >>>>>> >>>>>> # /usr/bin/pkg update --be-name r151022 >>>>>> >>>>>> i got: >>>>>> >>>>>> root at mojvps:/root# /usr/bin/pkg update --be-name r151022 >>>>>> Creating Plan (Running solver): | >>>>>> pkg update: No solution was found to satisfy constraints >>>>>> Plan Creation: Package solver has not found a solution to update to latest available versions. >>>>>> This may indicate an overly constrained set of packages are installed. >>>>>> >>>>>> latest incorporations: >>>>>> >>>>>> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >>>>>> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151022:20170510T210757Z >>>>>> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151022:20170510T212740Z >>>>>> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151022:20170511T001737Z >>>>>> Dependency analysis is unable to determine exact cause. >>>>>> Try specifying expected results to obtain more detailed error messages. >>>>>> >>>>>> >>>>>> I set publisher correctly IHMO: >>>>>> >>>>>> root at mojvps:/root# pkg publisher >>>>>> PUBLISHER TYPE STATUS P LOCATION >>>>>> omnios origin online F https://pkg.omniti.com/omnios/r151022/ >>>>>> >>>>>> >>>>>> Any ideas ? >>>>>> >>>>>> I want to upgrade to CE after that. >>>>>> >>>>>> Thanks in advance >>>>>> Kris >>>>>> >>>>>> 2017-07-24 17:01 GMT+02:00 Davide Poletto >: >>>>>> Thanks Andy, thanks Peter. >>>>>> >>>>>> So now OpenSSH is installed: >>>>>> >>>>>> root at nas01:/root# pkg list | grep ssh >>>>>> network/openssh 7.4.1-0.151014 i-- >>>>>> network/openssh-server 7.4.1-0.151014 i-- >>>>>> root at nas01:/root# ssh -V >>>>>> OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017 >>>>>> >>>>>> Totally my fault in not following the right Release Notes (I thought I should have followed the destination version - r151022 - Release Notes instead the one from where the upgrade process has to start, r151014 in my case). >>>>>> >>>>>> Thanks again for pointing me on the right track. >>>>>> >>>>>> Best regards, Davide. >>>>>> >>>>>> On Mon, Jul 24, 2017 at 4:21 PM, Peter Tribble > wrote: >>>>>> >>>>>> >>>>>> On Mon, Jul 24, 2017 at 2:56 PM, Davide Poletto > wrote: >>>>>> Hello all, >>>>>> >>>>>> I'm facing a strange issue on a pretty standard OmniOS r151014 LTS box fully updated (only Global Zone), following the "Upgrading to r151022" instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 required before any jump to OmniOS r151022 (my final target is OmniOS Community Edition r151022i) I found that I'm unable to switch to OpenSSH as per "Upgrading to OpenSSH from SunSSH" instructions on the same page: >>>>>> >>>>>> executing the suggested command: >>>>>> >>>>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh --reject pkg:/service/network/ssh-common pkg:/network/openssh pkg:/network/openssh-server >>>>>> >>>>>> fails with the message: >>>>>> >>>>>> pkg install: The following pattern(s) did not match any allowable packages. Try >>>>>> using a different matching pattern, or refreshing publisher information: >>>>>> >>>>>> pkg:/service/network/ssh-common >>>>>> >>>>>> The r151014 release notes >>>>>> >>>>>> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 >>>>>> >>>>>> say >>>>>> >>>>>> /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh pkg:/network/openssh pkg:/network/openssh-server >>>>>> >>>>>> Blindly I tried to omit the specific "ssh-common" package reject >>>>>> >>>>>> I think you were on the right track. >>>>>> >>>>>> but the result is not conforting me (maybe I tried a command in a totally wrong way not understanding what the --reject options really mean): >>>>>> >>>>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh --reject pkg:/network/openssh pkg:/network/openssh-server >>>>>> >>>>>> I think you have an extra --reject in there, so you've told it not to >>>>>> install openssh. >>>>>> >>>>>> -- >>>>>> -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 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> > > _______________________________________________ > 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 grzempek at gmail.com Sun Aug 13 11:56:46 2017 From: grzempek at gmail.com (Krzysztof Grzempa) Date: Sun, 13 Aug 2017 13:56:46 +0200 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> Message-ID: root at mojvps:/root# pkg publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniti.com/omnios/r151022/ root at mojvps:/root# /usr/bin/pkg update -v --be-name r151022 Creating Plan (Running solver): - pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://omnios/incorporation/jeos/illumos-gate at 11 ,5.11-0.151022:20170510T210757Z pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11 ,5.11-0.151022:20170510T212740Z pkg://omnios/incorporation/jeos/omnios-userland at 11 ,5.11-0.151022:20170511T001737Z pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. root at mojvps:/root# pkg update -v pkg://omnios/entire at 11 ,5.11-0.151022:20170511T002513Z Creating Plan (Solver setup): | pkg update: No matching version of entire can be installed: Reject: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Reason: This version is excluded by installed incorporation pkg:// ms.omniti.com/omniti/library/uuid at 1.41.14,5.11-0.151014:20150508T153803Z This version is excluded by installed incorporation pkg:// ms.omniti.com/omniti/runtime/python-26 at 2.6.9,5.11-0.151014:20150609T202314Z Thanks Dan, Regards, Chris 2017-08-13 3:03 GMT+02:00 Dan McDonald : > 1. Add "-v" to your "pig update". Might be silent but at least we can > eliminate it. > > 2. Do "pkg update pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z" > and see the complaint (and share it here). > > Dan > > Sent from my iPhone (typos, autocorrect, and all) > > On Aug 12, 2017, at 8:16 AM, Krzysztof Grzempa wrote: > > Guys, > Do you have any other ideas why i cannot upgrade to the damn r151022 or > any steps i can do to figure it out? > Below please find full command log of my upgrade process: > > root at mojvps:/root# pkg list | grep ssh > network/openssh > 7.4.1-0.151014 i-- > network/openssh-server > 7.4.1-0.151014 i-- > > root at mojvps:/root# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F > http://pkg.omniti.com/omnios/r151014/ > > root at mojvps:/root# pkg list -v ca-bundle > FMRI > IFO > pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z > i-- > > root at mojvps:/root# pkg refresh --full > > root at mojvps:/root# pkg update -nv > No updates available for this image. > > root at mojvps:/root# beadm list > BE Active Mountpoint Space Policy Created > omnios - - 3,67M static 2017-04-05 > 17:29 > omniosvar - - 19,0K static 2017-04-05 > 17:29 > update_07042017 NR / 4,86G static 2017-04-07 > 20:40 > update_07042017-backup-1 - - 237K static 2017-07-27 > 21:36 > upgrade_from_r151014_backup - - 243K static 2017-07-27 > 21:56 > update_07042017-backup-2 - - 297K static 2017-08-02 > 20:06 > update_07042017-backup-3 - - 308K static 2017-08-12 > 14:05 > upgrade_from_r151014_backup2 - - 315K static 2017-08-12 > 14:07 > > root at mojvps:/root# beadm create upgrade_from_r151014_backup3 > Created successfully > > root at mojvps:/root# /usr/bin/pkg set-publisher -G > http://pkg.omniti.com/omnios/r151014/ -g https://pkg.omniti.com/omnios/ > r151022/ omnios > > root at mojvps:/root# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F > https://pkg.omniti.com/omnios/r151022/ > > root at mojvps:/root# /usr/bin/pkg update --be-name r151022 > Creating Plan (Running solver): - > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest > available versions. > This may indicate an overly constrained set of packages are installed. > > latest incorporations: > > pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0. > 151022:20170510T210757Z > pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5. > 11,5.11-0.151022:20170510T212740Z > pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11- > 0.151022:20170511T001737Z > > Dependency analysis is unable to determine exact cause. > Try specifying expected results to obtain more detailed error messages. > > > 2017-08-01 21:47 GMT+02:00 Krzysztof Grzempa : > >> >> ---------- Forwarded message ---------- >> From: Krzysztof Grzempa >> Date: 2017-08-01 21:47 GMT+02:00 >> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from >> SunSSH to OpenSSH >> To: Andries Annema >> >> >> Hi All, >> @Jens @Davide @Andries >> >> I followed your ideas but no go for me.. >> >> root at mojvps:/root# pkg install pkg:/package/pkg >> No updates necessary for this image. >> root at mojvps:/root# pkg update -nv >> Creating Plan (Running solver): | >> pkg update: No solution was found to satisfy constraints >> Plan Creation: Package solver has not found a solution to update to >> latest available versions. >> This may indicate an overly constrained set of packages are installed. >> >> latest incorporations: >> >> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.15102 >> 2:20170510T210757Z >> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11, >> 5.11-0.151022:20170510T212740Z >> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.15 >> 1022:20170511T001737Z >> Dependency analysis is unable to determine exact cause. >> Try specifying expected results to obtain more detailed error messages. >> >> root at mojvps:/root# pkg update -nv entire >> No updates available for this image. >> root at mojvps:/root# pkg install -nv entire >> No updates necessary for this image. >> >> >> Regards, >> Chris >> >> 2017-07-31 19:54 GMT+02:00 Andries Annema : >> >>> Could this be in any way related to the issue I reported recently ( >>> http://lists.omniti.com/pipermail/omnios-discuss/2017-July/009079.html) >>> where I tried to run "pkglint" in order to prepare an IPS package and got a >>> "MemoryError" with the specific statement that "This is an internal error >>> in pkg(5) version ..."? >>> >>> Not sure if it does, because I got this error on a freshly installed >>> r151022 "vanilla" system, so no upgrade from r151014 or anything. Also, if >>> I run "pkg install pkg:/package/pkg" now on that system, it responds with >>> "No updates necessary for this image", so I doubt it is really related. >>> However, I couldn't help but ask, as I haven't received any response on >>> the other matter yet and both are related to "pkg"... >>> >>> Andries >>> >>> On 2017-07-31 17:14, Davide Poletto wrote: >>> >>> Hello all, just a follow up about the upgrade from OmniOS r151014 to >>> OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my >>> case...the only additional step it required before the final pkg update >>> -rv documented step (so the system was still on OmniOS r151022) was the >>> mandatory update of pkg(5) package: >>> >>> /usr/bin/pkg update -rv >>> WARNING: pkg(5) appears to be out of date, and should be updated before >>> running update. Please update pkg(5) by executing 'pkg install >>> pkg:/package/pkg' as a privileged user and then retry the update. >>> >>> root at nas01:~# pkg install pkg:/package/pkg >>> Packages to update: 1 >>> Create boot environment: No >>> Create backup boot environment: Yes >>> >>> DOWNLOAD PKGS FILES XFER >>> (MB) SPEED >>> Completed 1/1 42/42 >>> 1.2/1.2 430k/s >>> >>> PHASE ITEMS >>> Removing old actions 1/1 >>> Installing new actions 1/1 >>> Updating modified actions 43/43 >>> Updating package state database Done >>> Updating package cache 1/1 >>> Updating image state Done >>> Creating fast lookup database Done >>> Reading search index Done >>> Updating search index 1/1 >>> Updating package cache 1/1 >>> >>> I'm pretty sure that, when the system still was on OmniOS r151022 (so >>> when the publisher was still pkg.omniti.com/omnios/r151022/), the >>> system was also fully up-to-date...I remember I did a pkg update -nv to >>> check its status...but no updates were necessary (so the pkg(5) >>> update's requirement reported above probably is a direct consequence of >>> the publisher repository change from pkg.omniti.com/omnios/r151022/ to >>> pkg.omniosce.org/r151022/core/ which is the mandatory step prior of the >>> final pkg update -rv command execution). >>> >>> Worth to mention that additional step on the >>> https://github.com/omniosorg/omnios-build/blob/r151022/doc/R >>> eleaseNotes.md#upgrading-from-omniti-released-r151022 paragraph? >>> >>> Davide. >>> >>> On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa >>> wrote: >>> >>>> Hello Jens >>>> Currenty im out of home. >>>> I will try it out tommorow and report results... >>>> >>>> Thanks >>>> Chris >>>> >>>> 29.07.2017 00:28 "Jens Bauernfeind" >>>> napisa?(a): >>>> >>>>> Hi, >>>>> >>>>> what happens when you just try to update entire? >>>>> pkg update -nv entire >>>>> or >>>>> pkg install -nv entire >>>>> >>>>> Best Regards, >>>>> Jens >>>>> ________________________________________ >>>>> From: OmniOS-discuss [omnios-discuss-bounces at lists.omniti.com] on >>>>> behalf of Krzysztof Grzempa [grzempek at gmail.com] >>>>> Sent: Friday, July 28, 2017 10:50 >>>>> To: omnios-discuss at lists.omniti.com >>>>> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from >>>>> SunSSH to OpenSSH >>>>> >>>>> HI, >>>>> So, any other ideas ? I would like to avoid plain new installation >>>>> scenario :) >>>>> >>>>> Regards, >>>>> Kris >>>>> >>>>> 2017-07-28 1:29 GMT+02:00 Dan McDonald >>>> @kebe.com>>: >>>>> Yeah that's right. Sorry -- had to ask. >>>>> >>>>> Dan >>>>> >>>>> Sent from my iPhone (typos, autocorrect, and all) >>>>> >>>>> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa >>>> > wrote: >>>>> >>>>> Hi Dan, >>>>> I had done prerequsities before i started: >>>>> >>>>> root at mojvps:/root# pkg list -v ca-bundle >>>>> FMRI >>>>> IFO >>>>> pkg://omnios/web/ca-bundle at 5.11-0.151014:20170414T020006Z >>>>> i-- >>>>> >>>>> there is 'April' certificates..right ? >>>>> >>>>> Kris >>>>> >>>>> 2017-07-27 22:28 GMT+02:00 Dan McDonald >>>> @kebe.com>>: >>>>> You're sure you're on the very latest 014? Could be lack of updated >>>>> certificates... >>>>> >>>>> Dan >>>>> >>>>> Sent from my iPhone (typos, autocorrect, and all) >>>>> >>>>> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa >>>> > wrote: >>>>> >>>>> Guys, >>>>> I will grab this thread as it is somehow similiar. I want to upgrade >>>>> from r151014 to r151022. I went throught all steps of: >>>>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>>>> but when Im performing upgrade: >>>>> >>>>> # /usr/bin/pkg update --be-name r151022 >>>>> >>>>> i got: >>>>> >>>>> root at mojvps:/root# /usr/bin/pkg update --be-name r151022 >>>>> Creating Plan (Running solver): | >>>>> pkg update: No solution was found to satisfy constraints >>>>> Plan Creation: Package solver has not found a solution to update to >>>>> latest available versions. >>>>> This may indicate an overly constrained set of packages are installed. >>>>> >>>>> latest incorporations: >>>>> >>>>> pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z >>>>> pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.15102 >>>>> 2:20170510T210757Z >>>>> pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11, >>>>> 5.11-0.151022:20170510T212740Z >>>>> pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.15 >>>>> 1022:20170511T001737Z >>>>> Dependency analysis is unable to determine exact cause. >>>>> Try specifying expected results to obtain more detailed error messages. >>>>> >>>>> >>>>> I set publisher correctly IHMO: >>>>> >>>>> root at mojvps:/root# pkg publisher >>>>> PUBLISHER TYPE STATUS P LOCATION >>>>> omnios origin online F >>>>> https://pkg.omniti.com/omnios/r151022/ >>>>> >>>>> >>>>> Any ideas ? >>>>> >>>>> I want to upgrade to CE after that. >>>>> >>>>> Thanks in advance >>>>> Kris >>>>> >>>>> 2017-07-24 17:01 GMT+02:00 Davide Poletto >>>> >: >>>>> Thanks Andy, thanks Peter. >>>>> >>>>> So now OpenSSH is installed: >>>>> >>>>> root at nas01:/root# pkg list | grep ssh >>>>> network/openssh 7.4.1-0.151014 >>>>> i-- >>>>> network/openssh-server 7.4.1-0.151014 >>>>> i-- >>>>> root at nas01:/root# ssh -V >>>>> OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017 >>>>> >>>>> Totally my fault in not following the right Release Notes (I thought I >>>>> should have followed the destination version - r151022 - Release Notes >>>>> instead the one from where the upgrade process has to start, r151014 in my >>>>> case). >>>>> >>>>> Thanks again for pointing me on the right track. >>>>> >>>>> Best regards, Davide. >>>>> >>>>> On Mon, Jul 24, 2017 at 4:21 PM, Peter Tribble < >>>>> peter.tribble at gmail.com> wrote: >>>>> >>>>> >>>>> On Mon, Jul 24, 2017 at 2:56 PM, Davide Poletto < >>>>> davide.poletto at gmail.com> wrote: >>>>> Hello all, >>>>> >>>>> I'm facing a strange issue on a pretty standard OmniOS r151014 LTS box >>>>> fully updated (only Global Zone), following the "Upgrading to r151022" >>>>> instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151022 >>>>> required before any jump to OmniOS r151022 (my final target is OmniOS >>>>> Community Edition r151022i) I found that I'm unable to switch to OpenSSH as >>>>> per "Upgrading to OpenSSH from SunSSH" instructions on the same page: >>>>> >>>>> executing the suggested command: >>>>> >>>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>>>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>>>> pkg:/service/network/ssh --reject pkg:/service/network/ssh-common >>>>> pkg:/network/openssh pkg:/network/openssh-server >>>>> >>>>> fails with the message: >>>>> >>>>> pkg install: The following pattern(s) did not match any allowable >>>>> packages. Try >>>>> using a different matching pattern, or refreshing publisher >>>>> information: >>>>> >>>>> pkg:/service/network/ssh-common >>>>> >>>>> The r151014 release notes >>>>> >>>>> https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 >>>>> >>>>> say >>>>> >>>>> /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject >>>>> pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh >>>>> pkg:/network/openssh pkg:/network/openssh-server >>>>> >>>>> Blindly I tried to omit the specific "ssh-common" package reject >>>>> >>>>> I think you were on the right track. >>>>> >>>>> but the result is not conforting me (maybe I tried a command in a >>>>> totally wrong way not understanding what the --reject options really mean): >>>>> >>>>> root at nas01:/root# /usr/bin/pkg install --no-backup-be --reject >>>>> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject >>>>> pkg:/service/network/ssh --reject pkg:/network/openssh >>>>> pkg:/network/openssh-server >>>>> >>>>> I think you have an extra --reject in there, so you've told it not to >>>>> install openssh. >>>>> >>>>> -- >>>>> -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 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>> >>> >>> _______________________________________________ >>> OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://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 >>> >>> >> >> > _______________________________________________ > 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 Sun Aug 13 12:15:54 2017 From: mir at miras.org (Michael Rasmussen) Date: Sun, 13 Aug 2017 14:15:54 +0200 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> Message-ID: <20170813141554.2b056c7a@sleipner.datanom.net> On Sun, 13 Aug 2017 13:56:46 +0200 Krzysztof Grzempa wrote: > root at mojvps:/root# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F > https://pkg.omniti.com/omnios/r151022/ > root at mojvps:/root# /usr/bin/pkg update -v --be-name r151022 > Creating Plan (Running solver): - > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest > available versions. > This may indicate an overly constrained set of packages are installed. > Your problem is that you have installed packages from the ms.omniti.com repro. To be able to upgrade you need to uninstall those packages first. Especially the python 2.6 package is a problem since 141022 is based on python 2.7. So uninstall python-26 before upgrade. -- 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: I'd horsewhip you if I had a horse. -- Groucho Marx -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From an3s.annema at gmail.com Sun Aug 13 13:08:49 2017 From: an3s.annema at gmail.com (Andries Annema) Date: Sun, 13 Aug 2017 15:08:49 +0200 Subject: [OmniOS-discuss] omniosce wiki: sentences incomplete Message-ID: <0a1028de-b78b-1ea6-305e-4fea81684a32@gmail.com> To anyone who maintains the wiki-pages on github/omniosorg, I just stumbled upon some incomplete sentences in the "post-install"-section. Compare this ...: https://github.com/omniosorg/omnios-wiki/blob/master/KayakInteractive.md#post-install ... to this ...: https://omnios.omniti.com/wiki.php/KayakInteractive#Post-install ... and see that the words that, in the page source, are formatted within {{{ }}} are left out. I assume this has happened during the migration process from OmniTI to Github. Although it is a bit odd, as this has not happened to the other sections on that page. Not sure if this has happened elsewhere either. Regards, Andries From grzempek at gmail.com Sun Aug 13 13:30:00 2017 From: grzempek at gmail.com (Krzysztof Grzempa) Date: Sun, 13 Aug 2017 15:30:00 +0200 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: <20170813141554.2b056c7a@sleipner.datanom.net> References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> <20170813141554.2b056c7a@sleipner.datanom.net> Message-ID: root at mojvps:/# pkg uninstall python-26 pkg uninstall: 'python-26' matches multiple packages pkg://omnios/runtime/python-26 pkg://ms.omniti.com/omniti/runtime/python-26 Please provide one of the package FMRIs listed above to the install command. root at mojvps:/# pkg uninstall pkg://ms.omniti.com/omniti/runtime/python-26 Packages to remove: 1 Create boot environment: No Create backup boot environment: No PHASE ITEMS Removing old actions 4111/4111 Updating package state database Done Updating package cache 1/1 Updating image state Done Creating fast lookup database Done root at mojvps:/# pkg publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniti.com/omnios/r151022/ root at mojvps:/# /usr/bin/pkg update -v --be-name r151022 Creating Plan (Running solver): | pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://omnios/incorporation/jeos/illumos-gate at 11 ,5.11-0.151022:20170510T210757Z pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11 ,5.11-0.151022:20170510T212740Z pkg://omnios/incorporation/jeos/omnios-userland at 11 ,5.11-0.151022:20170511T001737Z pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Dependency analysis is unable to determine exact cause. Try specifying expected results to obtain more detailed error messages. root at mojvps:/# pkg update -v pkg://omnios/entire at 11 ,5.11-0.151022:20170511T002513Z Creating Plan (Solver setup): | pkg update: No matching version of entire can be installed: Reject: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z Reason: This version is excluded by installed incorporation pkg:// ms.omniti.com/omniti/library/uuid at 1.41.14,5.11-0.151014:20150508T153803Z Im not pretty sure why should I remove uuid and why it is complaining about it.... Regards, Chris 2017-08-13 14:15 GMT+02:00 Michael Rasmussen : > On Sun, 13 Aug 2017 13:56:46 +0200 > Krzysztof Grzempa wrote: > > > root at mojvps:/root# pkg publisher > > PUBLISHER TYPE STATUS P LOCATION > > omnios origin online F > > https://pkg.omniti.com/omnios/r151022/ > > root at mojvps:/root# /usr/bin/pkg update -v --be-name r151022 > > Creating Plan (Running solver): - > > pkg update: No solution was found to satisfy constraints > > Plan Creation: Package solver has not found a solution to update to > latest > > available versions. > > This may indicate an overly constrained set of packages are installed. > > > Your problem is that you have installed packages from the ms.omniti.com > repro. To be able to upgrade you need to uninstall those packages > first. Especially the python 2.6 package is a problem since 141022 is > based on python 2.7. So uninstall python-26 before upgrade. > > -- > 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: > I'd horsewhip you if I had a horse. > -- Groucho Marx > > _______________________________________________ > 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 kebe.com Sun Aug 13 17:33:53 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sun, 13 Aug 2017 13:33:53 -0400 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> <20170813141554.2b056c7a@sleipner.datanom.net> Message-ID: MANY of the OmniTI-Ms packages have hard coded version dependencies (e.g. ONLY r151014, not at least r151014). I tried to fix this, but many packages there remained unbuilt to the new, looser, dependencies. I'd remove ALL OmniTI-Ms packages before upgrading, and then put them back. Dan Sent from my iPhone (typos, autocorrect, and all) > On Aug 13, 2017, at 9:30 AM, Krzysztof Grzempa wrote: > > root at mojvps:/# pkg uninstall python-26 > > pkg uninstall: 'python-26' matches multiple packages > pkg://omnios/runtime/python-26 > pkg://ms.omniti.com/omniti/runtime/python-26 > > Please provide one of the package FMRIs listed above to the install command. > root at mojvps:/# pkg uninstall pkg://ms.omniti.com/omniti/runtime/python-26 > Packages to remove: 1 > Create boot environment: No > Create backup boot environment: No > > PHASE ITEMS > Removing old actions 4111/4111 > Updating package state database Done > Updating package cache 1/1 > Updating image state Done > Creating fast lookup database Done > root at mojvps:/# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F https://pkg.omniti.com/omnios/r151022/ > root at mojvps:/# /usr/bin/pkg update -v --be-name r151022 > Creating Plan (Running solver): | > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest available versions. > This may indicate an overly constrained set of packages are installed. > > latest incorporations: > > pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0.151022:20170510T210757Z > pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151022:20170510T212740Z > pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11-0.151022:20170511T001737Z > pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > Dependency analysis is unable to determine exact cause. > Try specifying expected results to obtain more detailed error messages. > > root at mojvps:/# pkg update -v pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > Creating Plan (Solver setup): | > pkg update: No matching version of entire can be installed: > Reject: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > Reason: This version is excluded by installed incorporation pkg://ms.omniti.com/omniti/library/uuid at 1.41.14,5.11-0.151014:20150508T153803Z > > > Im not pretty sure why should I remove uuid and why it is complaining about it.... > > Regards, > Chris > > > 2017-08-13 14:15 GMT+02:00 Michael Rasmussen : >> On Sun, 13 Aug 2017 13:56:46 +0200 >> Krzysztof Grzempa wrote: >> >> > root at mojvps:/root# pkg publisher >> > PUBLISHER TYPE STATUS P LOCATION >> > omnios origin online F >> > https://pkg.omniti.com/omnios/r151022/ >> > root at mojvps:/root# /usr/bin/pkg update -v --be-name r151022 >> > Creating Plan (Running solver): - >> > pkg update: No solution was found to satisfy constraints >> > Plan Creation: Package solver has not found a solution to update to latest >> > available versions. >> > This may indicate an overly constrained set of packages are installed. >> > >> Your problem is that you have installed packages from the ms.omniti.com >> repro. To be able to upgrade you need to uninstall those packages >> first. Especially the python 2.6 package is a problem since 141022 is >> based on python 2.7. So uninstall python-26 before upgrade. >> >> -- >> 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: >> I'd horsewhip you if I had a horse. >> -- Groucho Marx >> >> _______________________________________________ >> 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 mailinglists at qutic.com Sun Aug 13 19:43:33 2017 From: mailinglists at qutic.com (qutic development) Date: Sun, 13 Aug 2017 21:43:33 +0200 Subject: [OmniOS-discuss] omniosce wiki: sentences incomplete In-Reply-To: <0a1028de-b78b-1ea6-305e-4fea81684a32@gmail.com> References: <0a1028de-b78b-1ea6-305e-4fea81684a32@gmail.com> Message-ID: Thanks Andries, fixt it. - Stefan > Am 13.08.2017 um 15:08 schrieb Andries Annema : > > To anyone who maintains the wiki-pages on github/omniosorg, > > I just stumbled upon some incomplete sentences in the "post-install"-section. > Compare this ...: > > https://github.com/omniosorg/omnios-wiki/blob/master/KayakInteractive.md#post-install > > ... to this ...: > > https://omnios.omniti.com/wiki.php/KayakInteractive#Post-install > > ... and see that the words that, in the page source, are formatted within {{{ }}} are left out. > I assume this has happened during the migration process from OmniTI to Github. Although it is a bit odd, as this has not happened to the other sections on that page. > Not sure if this has happened elsewhere either. > > Regards, > > Andries > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From moo at wuffers.net Tue Aug 15 17:35:27 2017 From: moo at wuffers.net (wuffers) Date: Tue, 15 Aug 2017 13:35:27 -0400 Subject: [OmniOS-discuss] l2arc 16.0E accounting leak In-Reply-To: References: <65DC5816D4BEE043885A89FD54E273FC71DA3B49@MAIL101.Ellipseinc.com> Message-ID: First of all, thanks to all the hard work of everyone involved in the community edition. I will most likely go from r151022 to the latest when I get a chance to have scheduled maintenance. I hadn't seen a reply to this, so not sure if it has already been resolved, or it's just my installation that's seeing the issue. Is anyone else using l2arc without this issue? On Sun, Jun 4, 2017 at 1:16 AM, wuffers wrote: > I finally pulled the trigger on r151022, and am still experiencing this > after re-adding the cache devices. I had previously removed my l2arc in > r151020. > > I see the bug documented here: > https://www.illumos.org/issues/5701 to https://www.illumos.org/issues/7410 > https://www.illumos.org/issues/7867 > > Is anyone else still seeing this in r151022? > > My cache devices are 400G each: > > # zpool iostat -v > > [snip] > cache - - - - - - > c2t500117310015D579d0 736G 16.0E 46 125 2.07M 7.98M > c2t50011731001631FDd0 735G 16.0E 45 125 2.05M 7.97M > c12t500117310015D59Ed0 735G 16.0E 46 125 2.07M 7.98M > c12t500117310015D54Ed0 736G 16.0E 46 125 2.07M 7.98M > > arcstat output: > read hits miss hit% l2read l2hits l2miss l2hit% arcsz l2size > l2asize > 4.0K 2.7K 1.3K 66 1.3K 134 1.2K 10 223G 4.3T > 2.9T > > > > > > On Fri, May 5, 2017 at 11:30 AM, Dan McDonald wrote: > >> The next stable and LTS, r151022, will arrive this month and it has this >> fix. >> >> Dan >> >> Sent from my iPhone (typos, autocorrect, and all) >> >> On May 5, 2017, at 11:06 AM, Richard Jahnel >> wrote: >> >> Does anyone know if we pulled or backported the >> https://www.illumos.org/issues/7867 into r151020 yet? >> >> >> >> We are suffering from this bug now. I?m pulling out my l2arc devices >> until a fix is in place, which makes me sad. >> >> _______________________________________________ >> 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 grzempek at gmail.com Tue Aug 15 21:33:23 2017 From: grzempek at gmail.com (Krzysztof Grzempa) Date: Tue, 15 Aug 2017 23:33:23 +0200 Subject: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH In-Reply-To: References: <2E9975D3-0B47-469F-928B-0FE7D1D6AA5C@kebe.com> <9932A3BD-813B-42AA-8A02-98E896A1328D@kebe.com> <20170813141554.2b056c7a@sleipner.datanom.net> Message-ID: ok, I uninstalled uuid (and arp and arp-util packages as dependencies) and it went smootly. Thank you, guys Regards, Chris 2017-08-13 19:33 GMT+02:00 Dan McDonald : > MANY of the OmniTI-Ms packages have hard coded version dependencies (e.g. > ONLY r151014, not at least r151014). I tried to fix this, but many > packages there remained unbuilt to the new, looser, dependencies. > > I'd remove ALL OmniTI-Ms packages before upgrading, and then put them back. > > Dan > > Sent from my iPhone (typos, autocorrect, and all) > > On Aug 13, 2017, at 9:30 AM, Krzysztof Grzempa wrote: > > root at mojvps:/# pkg uninstall python-26 > > pkg uninstall: 'python-26' matches multiple packages > pkg://omnios/runtime/python-26 > pkg://ms.omniti.com/omniti/runtime/python-26 > > Please provide one of the package FMRIs listed above to the install > command. > root at mojvps:/# pkg uninstall pkg://ms.omniti.com/omniti/runtime/python-26 > Packages to remove: 1 > Create boot environment: No > Create backup boot environment: No > > PHASE ITEMS > Removing old actions 4111/4111 > Updating package state database Done > Updating package cache 1/1 > Updating image state Done > Creating fast lookup database Done > root at mojvps:/# pkg publisher > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F > https://pkg.omniti.com/omnios/r151022/ > root at mojvps:/# /usr/bin/pkg update -v --be-name r151022 > Creating Plan (Running solver): | > pkg update: No solution was found to satisfy constraints > Plan Creation: Package solver has not found a solution to update to latest > available versions. > This may indicate an overly constrained set of packages are installed. > > latest incorporations: > > pkg://omnios/incorporation/jeos/illumos-gate at 11,5.11-0. > 151022:20170510T210757Z > pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5. > 11,5.11-0.151022:20170510T212740Z > pkg://omnios/incorporation/jeos/omnios-userland at 11,5.11- > 0.151022:20170511T001737Z > pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > Dependency analysis is unable to determine exact cause. > Try specifying expected results to obtain more detailed error messages. > > root at mojvps:/# pkg update -v pkg://omnios/entire at 11,5.11-0. > 151022:20170511T002513Z > Creating Plan (Solver setup): | > pkg update: No matching version of entire can be installed: > Reject: pkg://omnios/entire at 11,5.11-0.151022:20170511T002513Z > Reason: This version is excluded by installed incorporation pkg:// > ms.omniti.com/omniti/library/uuid at 1.41.14,5.11-0.151014:20150508T153803Z > > > Im not pretty sure why should I remove uuid and why it is complaining > about it.... > > Regards, > Chris > > > 2017-08-13 14:15 GMT+02:00 Michael Rasmussen : > >> On Sun, 13 Aug 2017 13:56:46 +0200 >> Krzysztof Grzempa wrote: >> >> > root at mojvps:/root# pkg publisher >> > PUBLISHER TYPE STATUS P LOCATION >> > omnios origin online F >> > https://pkg.omniti.com/omnios/r151022/ >> > root at mojvps:/root# /usr/bin/pkg update -v --be-name r151022 >> > Creating Plan (Running solver): - >> > pkg update: No solution was found to satisfy constraints >> > Plan Creation: Package solver has not found a solution to update to >> latest >> > available versions. >> > This may indicate an overly constrained set of packages are installed. >> > >> Your problem is that you have installed packages from the ms.omniti.com >> repro. To be able to upgrade you need to uninstall those packages >> first. Especially the python 2.6 package is a problem since 141022 is >> based on python 2.7. So uninstall python-26 before upgrade. >> >> -- >> 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: >> I'd horsewhip you if I had a horse. >> -- Groucho Marx >> >> _______________________________________________ >> 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 dirk.willems at exitas.be Fri Aug 18 10:54:17 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Fri, 18 Aug 2017 12:54:17 +0200 Subject: [OmniOS-discuss] install GNUHEALTH Message-ID: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Hello, I try to install GNUHEALTH on OmniOSCE but when I run the install script I got a error on gcc Any suggestions what I'm doing wrong ? I install the package py36-psycopg2-2.7.1 building 'psycopg2._psycopg' extension creating build/temp.solaris-2.11-i86pc.64bit-3.6 creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -fPIC -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.7.3 (dt dec pq3 ext lo64)" -DPG_VERSION_NUM=90412 -DHAVE_LO64=1 -I/opt/local/include/python3.6 -I. -I/opt/local/include -I/opt/local/include/postgresql/server -c psycopg/psycopgmodule.c -o build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg/psycopgmodule.o In file included from /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h:7:0, from /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:34, from /opt/local/include/python3.6/Python.h:11, from ./psycopg/psycopg.h:34, from psycopg/psycopgmodule.c:27: /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:194:15: fatal error: limits.h: No such file or directory #include_next /* recurse down to the real one */ ^~~~~~~~~~ compilation terminated. error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/opt/local/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-68er_27q/psycopg2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-_oz9xywx-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-68er_27q/psycopg2/ 2017-08-18 10:37:17 [INFO] Bailing out ! 2017-08-18 10:37:17 [INFO] Cleaning up temp directories at /tmp/gnuhealth_installer 2017-08-18 10:37:17 [INFO] removing base dir at /export/home/gnuhealth//gnuhealth gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi gnuhealth-setup gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ echo $PATH /opt/local/gcc7/bin:/opt/local/gcc7/lib:/opt/local/sbin:/opt/local/bin:/usr/bin: gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h Thanks in advance Kind Regards, Dirk -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From dirk.willems at exitas.be Fri Aug 18 11:12:16 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Fri, 18 Aug 2017 13:12:16 +0200 Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: Hello, In the file /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h stands #ifdef _GCC_NEXT_LIMITS_H #include_next #endif Can I uncomment the include_next or bad idea ? Thanks KR, Dirk On 18-08-17 12:54, Dirk Willems wrote: > > Hello, > > > I try to install GNUHEALTH on OmniOSCE > > > but when I run the install script I got a error on gcc > > > Any suggestions what I'm doing wrong ? > > > I install the package py36-psycopg2-2.7.1 > > > building 'psycopg2._psycopg' extension > creating build/temp.solaris-2.11-i86pc.64bit-3.6 > creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg > gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 -pipe -O2 > -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses > -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include > -I/opt/local/include -I/opt/local/include/ncurses > -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include > -I/opt/local/include -I/opt/local/include/ncurses > -I/opt/local/include/db4 -fPIC -DPSYCOPG_DEFAULT_PYDATETIME=1 > -DPSYCOPG_VERSION="2.7.3 (dt dec pq3 ext lo64)" -DPG_VERSION_NUM=90412 > -DHAVE_LO64=1 -I/opt/local/include/python3.6 -I. -I/opt/local/include > -I/opt/local/include/postgresql/server -c psycopg/psycopgmodule.c -o > build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg/psycopgmodule.o > In file included from > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h:7:0, > from > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:34, > from /opt/local/include/python3.6/Python.h:11, > from ./psycopg/psycopg.h:34, > from psycopg/psycopgmodule.c:27: > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:194:15: > fatal error: limits.h: No such file or directory > #include_next /* recurse down to the real one */ > ^~~~~~~~~~ > compilation terminated. > error: command 'gcc' failed with exit status 1 > > ---------------------------------------- > Command "/opt/local/bin/python3.6 -u -c "import setuptools, > tokenize;__file__='/tmp/pip-build-68er_27q/psycopg2/setup.py';f=getattr(tokenize, > 'open', open)(__file__);code=f.read().replace('\r\n', > '\n');f.close();exec(compile(code, __file__, 'exec'))" install > --record /tmp/pip-_oz9xywx-record/install-record.txt > --single-version-externally-managed --compile --user --prefix=" failed > with error code 1 in /tmp/pip-build-68er_27q/psycopg2/ > 2017-08-18 10:37:17 [INFO] Bailing out ! > 2017-08-18 10:37:17 [INFO] Cleaning up temp directories at > /tmp/gnuhealth_installer > 2017-08-18 10:37:17 [INFO] removing base dir at > /export/home/gnuhealth//gnuhealth > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > gnuhealth-setup > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ echo $PATH > /opt/local/gcc7/bin:/opt/local/gcc7/lib:/opt/local/sbin:/opt/local/bin:/usr/bin: > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h > > > Thanks in advance > > > Kind Regards, > > > Dirk > > > -- > Dirk Willems > System Engineer > > > +32 (0)3 443 12 38 > Dirk.Willems at exitas.be > > Quality. Passion. Personality > > www.exitas.be | Veldkant 31 | 2550 Kontich > > Illumos OmniOS Installation and Configuration Implementation Specialist. > Oracle Solaris 11 Installation and Configuration Certified > Implementation Specialist. > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From omnios at citrus-it.net Fri Aug 18 11:14:35 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 18 Aug 2017 11:14:35 +0000 (UTC) Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: On Fri, 18 Aug 2017, Dirk Willems wrote: ; Hello, ; ; ; I try to install GNUHEALTH on OmniOSCE ; ; ; fatal error: limits.h: No such file or directory ; #include_next /* recurse down to the real one */ ; ^~~~~~~~~~ ; compilation terminated. ; error: command 'gcc' failed with exit status 1 Have you installed the system/header package? To make sure you have everything needed for compilation check the wiki page at http://wiki.omniosce.org/DevEnv.html Regards, Andy -- For OmniOSce support, please visit the lobby at: https://gitter.im/omniosorg/Lobby -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From peter.tribble at gmail.com Fri Aug 18 11:18:27 2017 From: peter.tribble at gmail.com (Peter Tribble) Date: Fri, 18 Aug 2017 12:18:27 +0100 Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: On Fri, Aug 18, 2017 at 12:12 PM, Dirk Willems wrote: > Hello, > > > In the file /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h > stands > > > #ifdef _GCC_NEXT_LIMITS_H > > #include_next > > #endif > > > Can I uncomment the include_next or bad idea ? > A *much* better idea woul be to remove (or move out of the way) the entire include-fixed directory. You're using pkgsrc here. There may be a good reason, but why not the system compiler? But, you do have the system/header package installed? > Thanks > > > KR, > > > Dirk > > > > On 18-08-17 12:54, Dirk Willems wrote: > > Hello, > > > I try to install GNUHEALTH on OmniOSCE > > > but when I run the install script I got a error on gcc > > > Any suggestions what I'm doing wrong ? > > > I install the package py36-psycopg2-2.7.1 > > > building 'psycopg2._psycopg' extension > creating build/temp.solaris-2.11-i86pc.64bit-3.6 > creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg > gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 -pipe -O2 > -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses > -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include > -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 > -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include > -I/opt/local/include/ncurses -I/opt/local/include/db4 -fPIC > -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.7.3 (dt dec pq3 ext > lo64)" -DPG_VERSION_NUM=90412 -DHAVE_LO64=1 -I/opt/local/include/python3.6 > -I. -I/opt/local/include -I/opt/local/include/postgresql/server -c > psycopg/psycopgmodule.c -o build/temp.solaris-2.11-i86pc. > 64bit-3.6/psycopg/psycopgmodule.o > In file included from /opt/local/gcc7/lib/gcc/x86_ > 64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h:7:0, > from /opt/local/gcc7/lib/gcc/x86_ > 64-sun-solaris2.11/7.1.0/include-fixed/limits.h:34, > from /opt/local/include/python3.6/Python.h:11, > from ./psycopg/psycopg.h:34, > from psycopg/psycopgmodule.c:27: > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:194:15: > fatal error: limits.h: No such file or directory > #include_next /* recurse down to the real one */ > ^~~~~~~~~~ > compilation terminated. > error: command 'gcc' failed with exit status 1 > > ---------------------------------------- > Command "/opt/local/bin/python3.6 -u -c "import setuptools, > tokenize;__file__='/tmp/pip-build-68er_27q/psycopg2/setup.py';f=getattr(tokenize, > 'open', open)(__file__);code=f.read().replace('\r\n', > '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record > /tmp/pip-_oz9xywx-record/install-record.txt --single-version-externally-managed > --compile --user --prefix=" failed with error code 1 in > /tmp/pip-build-68er_27q/psycopg2/ > 2017-08-18 10:37:17 [INFO] Bailing out ! > 2017-08-18 10:37:17 [INFO] Cleaning up temp directories at > /tmp/gnuhealth_installer > 2017-08-18 10:37:17 [INFO] removing base dir at /export/home/gnuhealth// > gnuhealth > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > gnuhealth-setup > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ echo $PATH > /opt/local/gcc7/bin:/opt/local/gcc7/lib:/opt/local/ > sbin:/opt/local/bin:/usr/bin: > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h > > gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ vi > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h > > > Thanks in advance > > > Kind Regards, > > > Dirk > > > -- > Dirk Willems > System Engineer > > > +32 (0)3 443 12 38 <+32%203%20443%2012%2038> > Dirk.Willems at exitas.be > > Quality. Passion. Personality > > www.exitas.be | Veldkant 31 | 2550 Kontich > > Illumos OmniOS Installation and Configuration Implementation Specialist. > Oracle Solaris 11 Installation and Configuration Certified Implementation > Specialist. > > > _______________________________________________ > OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss > > > -- > Dirk Willems > System Engineer > > > +32 (0)3 443 12 38 <+32%203%20443%2012%2038> > Dirk.Willems at exitas.be > > Quality. Passion. Personality > > www.exitas.be | Veldkant 31 | 2550 Kontich > > Illumos OmniOS Installation and Configuration Implementation Specialist. > Oracle Solaris 11 Installation and Configuration Certified Implementation > Specialist. > > _______________________________________________ > 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: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From dirk.willems at exitas.be Fri Aug 18 11:19:06 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Fri, 18 Aug 2017 13:19:06 +0200 Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: <227d7775-d6dd-df3c-015d-c6ca673f97f7@exitas.be> Hello Andy, Thank you very much for you feedback, No I didn't, didn't know it yet so thank you gonna try keep you posting .... Kind Regards, Dirk On 18-08-17 13:14, Andy Fiddaman wrote: > On Fri, 18 Aug 2017, Dirk Willems wrote: > > ; Hello, > ; > ; > ; I try to install GNUHEALTH on OmniOSCE > ; > ; > ; fatal error: limits.h: No such file or directory > ; #include_next /* recurse down to the real one */ > ; ^~~~~~~~~~ > ; compilation terminated. > ; error: command 'gcc' failed with exit status 1 > > Have you installed the system/header package? > > To make sure you have everything needed for compilation check the wiki > page at http://wiki.omniosce.org/DevEnv.html > > Regards, > > Andy > -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From dirk.willems at exitas.be Fri Aug 18 11:31:17 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Fri, 18 Aug 2017 13:31:17 +0200 Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: <8a4fb97b-2648-1ffb-b7d4-8321315b8db4@exitas.be> Hello Peter, How are you, I still have to fix your connection to our T5 I'm still working on it but time is an issue you know right ;) So answer your questions: - Yes I do use pkgsrc from joyent I love that repo is really great - Why not the system compiler because I'm not ready for it I'm still learning and yes you're right I have to start with it - I don't think so if the system/header is installed how can I check it ? Sorry Guy's I'm just try to learn all this great stuff and very much thanks for all your time and feedback Kind Regards, Dirk On 18-08-17 13:18, Peter Tribble wrote: > > > On Fri, Aug 18, 2017 at 12:12 PM, Dirk Willems > wrote: > > Hello, > > > In the file > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h > stands > > > #ifdef _GCC_NEXT_LIMITS_H > > #include_next > > #endif > > > Can I uncomment the include_next or bad idea ? > > > A *much* better idea woul be to remove (or move out of the way) the > entire include-fixed directory. > > You're using pkgsrc here. There may be a good reason, but why not the > system compiler? > > But, you do have the system/header package installed? > > Thanks > > > KR, > > > Dirk > > > > On 18-08-17 12:54, Dirk Willems wrote: >> >> Hello, >> >> >> I try to install GNUHEALTH on OmniOSCE >> >> >> but when I run the install script I got a error on gcc >> >> >> Any suggestions what I'm doing wrong ? >> >> >> I install the package py36-psycopg2-2.7.1 >> >> >> building 'psycopg2._psycopg' extension >> creating build/temp.solaris-2.11-i86pc.64bit-3.6 >> creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg >> gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -fPIC >> -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.7.3 (dt dec >> pq3 ext lo64)" -DPG_VERSION_NUM=90412 -DHAVE_LO64=1 >> -I/opt/local/include/python3.6 -I. -I/opt/local/include >> -I/opt/local/include/postgresql/server -c psycopg/psycopgmodule.c >> -o build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg/psycopgmodule.o >> In file included from >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h:7:0, >> from >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:34, >> from /opt/local/include/python3.6/Python.h:11, >> from ./psycopg/psycopg.h:34, >> from psycopg/psycopgmodule.c:27: >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:194:15: >> fatal error: limits.h: No such file or directory >> #include_next /* recurse down to the real one */ >> ^~~~~~~~~~ >> compilation terminated. >> error: command 'gcc' failed with exit status 1 >> >> ---------------------------------------- >> Command "/opt/local/bin/python3.6 -u -c "import setuptools, >> tokenize;__file__='/tmp/pip-build-68er_27q/psycopg2/setup.py';f=getattr(tokenize, >> 'open', open)(__file__);code=f.read().replace('\r\n', >> '\n');f.close();exec(compile(code, __file__, 'exec'))" install >> --record /tmp/pip-_oz9xywx-record/install-record.txt >> --single-version-externally-managed --compile --user --prefix=" >> failed with error code 1 in /tmp/pip-build-68er_27q/psycopg2/ >> 2017-08-18 10:37:17 [INFO] Bailing out ! >> 2017-08-18 10:37:17 [INFO] Cleaning up temp directories at >> /tmp/gnuhealth_installer >> 2017-08-18 10:37:17 [INFO] removing base dir at >> /export/home/gnuhealth//gnuhealth >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi gnuhealth-setup >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> echo $PATH >> /opt/local/gcc7/bin:/opt/local/gcc7/lib:/opt/local/sbin:/opt/local/bin:/usr/bin: >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h >> >> >> Thanks in advance >> >> >> Kind Regards, >> >> >> Dirk >> >> >> -- >> Dirk Willems >> System Engineer >> >> >> +32 (0)3 443 12 38 >> Dirk.Willems at exitas.be >> >> Quality. Passion. Personality >> >> www.exitas.be | Veldkant 31 | 2550 Kontich >> >> Illumos OmniOS Installation and Configuration Implementation >> Specialist. >> Oracle Solaris 11 Installation and Configuration Certified >> Implementation Specialist. >> >> >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > > -- > Dirk Willems > System Engineer > > > +32 (0)3 443 12 38 > Dirk.Willems at exitas.be > > Quality. Passion. Personality > > www.exitas.be | Veldkant 31 | 2550 Kontich > > Illumos OmniOS Installation and Configuration Implementation > Specialist. > Oracle Solaris 11 Installation and Configuration Certified > Implementation Specialist. > > > _______________________________________________ > 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/ -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From dirk.willems at exitas.be Fri Aug 18 15:08:33 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Fri, 18 Aug 2017 17:08:33 +0200 Subject: [OmniOS-discuss] install GNUHEALTH In-Reply-To: References: <5dc025c9-1cf7-fb45-0ea6-301d35fff5fa@exitas.be> Message-ID: <84db4331-c0f5-16de-2383-ea492997f762@exitas.be> Peter, I started over from scratch and followed http://wiki.omniosce.org/DevEnv.html so now I have the |system/header||:)| | | |And also remember again why I use the pkgsrc source because of the packages like python postgress gpg etc ...| |which I cannot find in the pkg repo.| | | |So pkg gcc is installed | gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/opt/gcc-5.1.0/libexec/gcc/i386-pc-solaris2.11/5.1.0/lto-wrapper Target: i386-pc-solaris2.11 Configured with: ./configure --prefix=/opt/gcc-5.1.0 --host i386-pc-solaris2.11 --build i386-pc-solaris2.11 --target i386-pc-solaris2.11 --with-boot-ldflags=-R/opt/gcc-5.1.0/lib --with-gmp=/opt/gcc-5.1.0 --with-mpfr=/opt/gcc-5.1.0 --with-mpc=/opt/gcc-5.1.0 --enable-languages=c,c++,fortran,lto --without-gnu-ld --with-ld=/bin/ld --with-as=/usr/bin/gas --with-gnu-as --with-build-time-tools=/usr/gnu/i386-pc-solaris2.11/bin Thread model: posix gcc version 5.1.0 (GCC) Tried to install it again with pkg gcc 5.1 hopefully ... building 'psycopg2._psycopg' extension creating build/temp.solaris-2.11-i86pc.64bit-3.6 creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 -pipe -O2 -I/usr/include -I/opt/local/include -I/opt/local/include/ncurses -I/opt/local/include/db4 -fPIC -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.7.3 (dt dec pq3 ext lo64)" -DPG_VERSION_NUM=90412 -DHAVE_LO64=1 -I/opt/local/include/python3.6 -I. -I/opt/local/include -I/opt/local/include/postgresql/server -c psycopg/psycopgmodule.c -o build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg/psycopgmodule.o In file included from /opt/local/include/python3.6/Python.h:50:0, from ./psycopg/psycopg.h:34, from psycopg/psycopgmodule.c:27: /opt/local/include/python3.6/pyport.h:686:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." ^ In file included from ./psycopg/psycopg.h:37:0, from psycopg/psycopgmodule.c:27: ./psycopg/config.h:174:0: warning: "isinf" redefined #define isinf(x) (!finite((x)) && (x)==(x)) ^ In file included from /usr/include/math.h:33:0, from /opt/local/include/python3.6/pyport.h:194, from /opt/local/include/python3.6/Python.h:50, from ./psycopg/psycopg.h:34, from psycopg/psycopgmodule.c:27: /usr/include/iso/math_c99.h:67:0: note: this is the location of the previous definition #define isinf(x) __builtin_isinf(x) ^ error: command 'gcc' failed with exit status 1 ---------------------------------------- Command "/opt/local/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-gd_pv6gq/psycopg2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-cdr8idal-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-build-gd_pv6gq/psycopg2/ 2017-08-18 14:24:57 [INFO] Bailing out ! 2017-08-18 14:24:57 [INFO] Cleaning up temp directories at /tmp/gnuhealth_installer 2017-08-18 14:24:57 [INFO] removing base dir at /export/home/gnuhealth//gnuhealth Getting a different error now it's python who is complaining to bad :( So I was thinking for trying /"//A *much* better idea woul be to remove (or move out of the way) the entire include-fixed directory."/ So I installed the pkgsrc gcc49 changing the PATH gnuhealth at GNUHealth:~$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/opt/local/gcc49/libexec/gcc/x86_64-sun-solaris2.11/4.9.4/lto-wrapper Target: x86_64-sun-solaris2.11 Configured with: ../gcc-4.9.4/configure --disable-libstdcxx-pch --enable-libssp --enable-languages='c obj-c++ objc go fortran c++' --enable-shared --enable-long-long --with-local-prefix=/opt/local --enable-threads=posix --with-boot-ldflags='-static-libstdc++ -static-libgcc -Wl,-R/opt/local/lib ' --disable-nls --with-gxx-include-dir=/opt/local/gcc49/include/c++/ --without-gnu-ld --with-ld=/usr/bin/ld --with-gnu-as --with-as=/opt/local/bin/gas --prefix=/opt/local/gcc49 --build=x86_64-sun-solaris2.11 --host=x86_64-sun-solaris2.11 --infodir=/opt/local/gcc49/info --mandir=/opt/local/gcc49/man Thread model: posix gcc version 4.9.4 (GCC) But before modify something I thought just run it with gcc49 and see what comes So reinstall the script and now it is working great I love this :) so it works with pkgsrc gcc49 Collecting psycopg2 Using cached psycopg2-2.7.3.tar.gz Installing collected packages: psycopg2 Running setup.py install for psycopg2 ... done Successfully installed psycopg2-2.7.3 Collecting vobject Downloading vobject-0.9.5.tar.gz (58kB) 100% |################################| 61kB 1.3MB/s Requirement already up-to-date: python-dateutil>=2.4.0 in /export/home/gnuhealth/.local/lib/python3.6/site-packages (from vobject) Requirement already up-to-date: six>=1.5 in /export/home/gnuhealth/.local/lib/python3.6/site-packages (from python-dateutil>=2.4.0->vobject) Installing collected packages: vobject Running setup.py install for vobject ... done Successfully installed vobject-0.9.5 up to the next problem 2017-08-18 14:57:00 [INFO] OK. 2017-08-18 14:57:00 [INFO] Uncompressing the Tryton server... tar: /tmp/gnuhealth_installer/4.2: No such file or directory 2017-08-18 14:57:00 [INFO] Bailing out ! 2017-08-18 14:57:00 [INFO] Cleaning up temp directories at /tmp/gnuhealth_installer 2017-08-18 14:57:00 [INFO] removing base dir at /export/home/gnuhealth//gnuhealth rm: Cannot remove any directory in the path of the current working directory /export/home/gnuhealth//gnuhealth/tryton/server rm: Unable to remove directory /export/home/gnuhealth//gnuhealth/tryton: Directory not empty rm: Unable to remove directory /export/home/gnuhealth//gnuhealth: Directory not empty Looking if I can fix this ... Thank you very much, I keep posting ... KR, Dirk On 18-08-17 13:18, Peter Tribble wrote: > > > On Fri, Aug 18, 2017 at 12:12 PM, Dirk Willems > wrote: > > Hello, > > > In the file > /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h > stands > > > #ifdef _GCC_NEXT_LIMITS_H > > #include_next > > #endif > > > Can I uncomment the include_next or bad idea ? > > > A *much* better idea woul be to remove (or move out of the way) the > entire include-fixed directory. > > You're using pkgsrc here. There may be a good reason, but why not the > system compiler? > > But, you do have the system/header package installed? > > Thanks > > > KR, > > > Dirk > > > > On 18-08-17 12:54, Dirk Willems wrote: >> >> Hello, >> >> >> I try to install GNUHEALTH on OmniOSCE >> >> >> but when I run the install script I got a error on gcc >> >> >> Any suggestions what I'm doing wrong ? >> >> >> I install the package py36-psycopg2-2.7.1 >> >> >> building 'psycopg2._psycopg' extension >> creating build/temp.solaris-2.11-i86pc.64bit-3.6 >> creating build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg >> gcc -Wno-unused-result -Wsign-compare -DNDEBUG -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -pipe -O2 >> -pipe -O2 -I/usr/include -I/opt/local/include >> -I/opt/local/include/ncurses -I/opt/local/include/db4 -fPIC >> -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.7.3 (dt dec >> pq3 ext lo64)" -DPG_VERSION_NUM=90412 -DHAVE_LO64=1 >> -I/opt/local/include/python3.6 -I. -I/opt/local/include >> -I/opt/local/include/postgresql/server -c psycopg/psycopgmodule.c >> -o build/temp.solaris-2.11-i86pc.64bit-3.6/psycopg/psycopgmodule.o >> In file included from >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h:7:0, >> from >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:34, >> from /opt/local/include/python3.6/Python.h:11, >> from ./psycopg/psycopg.h:34, >> from psycopg/psycopgmodule.c:27: >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h:194:15: >> fatal error: limits.h: No such file or directory >> #include_next /* recurse down to the real one */ >> ^~~~~~~~~~ >> compilation terminated. >> error: command 'gcc' failed with exit status 1 >> >> ---------------------------------------- >> Command "/opt/local/bin/python3.6 -u -c "import setuptools, >> tokenize;__file__='/tmp/pip-build-68er_27q/psycopg2/setup.py';f=getattr(tokenize, >> 'open', open)(__file__);code=f.read().replace('\r\n', >> '\n');f.close();exec(compile(code, __file__, 'exec'))" install >> --record /tmp/pip-_oz9xywx-record/install-record.txt >> --single-version-externally-managed --compile --user --prefix=" >> failed with error code 1 in /tmp/pip-build-68er_27q/psycopg2/ >> 2017-08-18 10:37:17 [INFO] Bailing out ! >> 2017-08-18 10:37:17 [INFO] Cleaning up temp directories at >> /tmp/gnuhealth_installer >> 2017-08-18 10:37:17 [INFO] removing base dir at >> /export/home/gnuhealth//gnuhealth >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi gnuhealth-setup >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> echo $PATH >> /opt/local/gcc7/bin:/opt/local/gcc7/lib:/opt/local/sbin:/opt/local/bin:/usr/bin: >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/limits.h >> >> gnuhealth at GNUHealth:/export/home/gnuhealth/gnuhealth-3.2.1$ >> >> vi >> /opt/local/gcc7/lib/gcc/x86_64-sun-solaris2.11/7.1.0/include-fixed/syslimits.h >> >> >> Thanks in advance >> >> >> Kind Regards, >> >> >> Dirk >> >> >> -- >> Dirk Willems >> System Engineer >> >> >> +32 (0)3 443 12 38 >> Dirk.Willems at exitas.be >> >> Quality. Passion. Personality >> >> www.exitas.be | Veldkant 31 | 2550 Kontich >> >> Illumos OmniOS Installation and Configuration Implementation >> Specialist. >> Oracle Solaris 11 Installation and Configuration Certified >> Implementation Specialist. >> >> >> >> _______________________________________________ >> OmniOS-discuss mailing list >> OmniOS-discuss at lists.omniti.com >> >> http://lists.omniti.com/mailman/listinfo/omnios-discuss >> > > -- > Dirk Willems > System Engineer > > > +32 (0)3 443 12 38 > Dirk.Willems at exitas.be > > Quality. Passion. Personality > > www.exitas.be | Veldkant 31 | 2550 Kontich > > Illumos OmniOS Installation and Configuration Implementation > Specialist. > Oracle Solaris 11 Installation and Configuration Certified > Implementation Specialist. > > > _______________________________________________ > 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/ -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From ergi.thanasko at avsquad.com Fri Aug 18 15:58:56 2017 From: ergi.thanasko at avsquad.com (Ergi Thanasko) Date: Fri, 18 Aug 2017 15:58:56 +0000 Subject: [OmniOS-discuss] Chelsio 100GbE nics driver help Message-ID: <50ED4B99-1C15-4E40-9A28-ADF03A98D76A@avsquad.com> Is anyone working with the Chelsio 100GbE nics, need some help with the drivers and RDMA Offloading From peter at ifm.liu.se Sat Aug 19 20:48:32 2017 From: peter at ifm.liu.se (Peter Eriksson) Date: Sat, 19 Aug 2017 22:48:32 +0200 Subject: [OmniOS-discuss] NFSv4 (client) strange behaviour Message-ID: <91970C9E-33E2-4E56-AF8C-CB77BD3C1B0A@ifm.liu.se> I?m seeing an annoying NFSv4 behaviour on OmniOS (also on Solaris 10 so this is probably an old bug). Setup: Server: FreeBSD 11.0 joined to an AD with Kerberos and stuff serving NFSv4 _only_ with V4 ?root? set to /export which is a ZFS pool/filesystem. Under /export there are a number of additional filesystems with various ?sharenfs? settings: /etc/exports V4: /export -sec=krb5:krb5i:krb5p:sys # zfs list -o name,sharenfs,mountpoint -r -d 1 DATA NAME SHARENFS MOUNTPOINT DATA ro /export DATA/db ro /export/db DATA/liu ro /liu DATA/samarbete no /export/samarbete DATA/software sec=krb5:sys,ro /export/software DATA/staff ro /export/staff DATA/students sec=krb5:krb5i:krb5p /export/students DATA/test sec=sys,ro /export/test DATA/users sec=krb5:krb5i:krb5p /export/users Mounting the root of these filsystems on Linux (CentOS 7), Solaris 10/OmniOS and FreeBSD 11 (using NFSv4, sec=sys) gives slightly different behaviour, but Solaris/OmniOS fails in a different way? Clients: Linux (CentOS 7): > # mount -t nfs -o vers=4,sec=sys,ro testy:/ /mnt > # cd /mnt > # ls > db samarbete software staff students test users > # ls -l > total 7 > drwxr-xr-x 3 root wheel 3 Jul 19 12:38 db > drwxr-xr-x 3 root wheel 3 Aug 19 13:01 samarbete > drwxr-xr-x 3 root wheel 3 Aug 18 13:40 software > drwxr-xr-x 2 root wheel 2 Jun 1 19:59 staff > drwxr-xr-x 88 root wheel 88 Aug 3 13:00 students > drwxr-xr-x 3 root wheel 4 Aug 19 13:15 test > drwxr-xr-x 4 root wheel 4 Jul 16 12:54 users > [root at filifjonkan mnt]# cd students > bash: cd: students: Operation not permitted > > # ls -l > ls: cannot access students: Operation not permitted > ls: cannot access users: Operation not permitted > total 3 > drwxr-xr-x 3 root wheel 3 Jul 19 12:38 db > drwxr-xr-x 3 root wheel 3 Aug 19 13:01 samarbete > drwxr-xr-x 3 root wheel 3 Aug 18 13:40 software > drwxr-xr-x 2 root wheel 2 Jun 1 19:59 staff > d????????? ? ? ? ? ? students > drwxr-xr-x 3 root wheel 4 Aug 19 13:15 test > d????????? ? ? ? ? ? users Ok, not perfect. But doable. FreeBSD 11.0: > # mount -t nfs -o vers=4,sec=sys,ro testy:/ /mnt > # cd /mnt > # ls > db samarbete software staff students test users > # /bin/ls -l > nfsv4 err=10016 > nfsv4 err=10016 > ls: students: Input/output error > ls: users: Input/output error > total 3 > drwxr-xr-x 3 root wheel 3 Jul 19 12:38 db > drwxr-xr-x 3 root wheel 3 Aug 19 13:01 samarbete > drwxr-xr-x 3 root wheel 3 Aug 18 13:40 software > drwxr-xr-x 2 root wheel 2 Jun 1 19:59 staff > drwxr-xr-x 3 root wheel 4 Aug 19 13:15 test OmniOS (basically the same behaviour with Solaris 10): > # mount -F nfs -o vers=4,sec=sys,ro testy:/ /mnt > # cd /mnt > # /bin/ls > db samarbete software staff students test users > # /bin/ls -l > ls: can't read ACL on ./students: Not owner > ls: can't read ACL on ./samarbete: Not owner > ls: can't read ACL on ./users: Not owner > ls: can't read ACL on ./test: Not owner > total 3 > drwxr-xr-x 3 root nobody 3 Jul 19 12:38 db > drwxr-xr-x 3 root nobody 3 Aug 19 13:01 samarbete > drwxr-xr-x 3 root nobody 3 Aug 18 13:40 software > drwxr-xr-x 2 root nobody 2 Jun 1 19:59 staff > drwxr-xr-x 88 root nobody 88 Aug 3 13:00 students > drwxr-xr-x 3 root nobody 4 Aug 19 13:15 test > drwxr-xr-x 4 root nobody 4 Jul 16 12:54 users > # cd students > students: Not owner. > # pwd > /mnt > # ls -l > .: Not owner > total 3 After that any access to /mnt just gives ?Not owner?. Only way out (that I?ve found so far) is to unmount and remount /mnt again. A ?snoop port nfsd? gives this trace: > # filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=409A GETATTR 10111a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4_OK PUTFH NFS4_OK GETATTR NFS4_OK > filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=409A GETATTR 10011a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4_OK PUTFH NFS4_OK GETATTR NFS4_OK > filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=69C4 GETATTR 10111a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4_OK PUTFH NFS4_OK GETATTR NFS4_OK > filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=5E5D GETATTR 10111a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4_OK PUTFH NFS4_OK GETATTR NFS4_OK > filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=7187 GETATTR 10111a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4_OK PUTFH NFS4_OK GETATTR NFS4_OK > filur00.it.liu.se -> testy.it.liu.se NFS C 4 (getattr ) PUTFH FH=69D3 GETATTR 10111a b0a23a > testy.it.liu.se -> filur00.it.liu.se NFS R 4 (getattr ) NFS4ERR_WRONGSEC PUTFH NFS4ERR_WRONGSEC > filur00.it.liu.se -> testy.it.liu.se TCP D=2049 S=1013 Ack=246526621 Seq=3432209847 Len=0 Win=32806 Options= and syslog contains: > Aug 19 22:16:11 filur00 nfs: [ID 236337 kern.info] NOTICE: [NFS4][Server: testy.it.liu.se][Mntpt: /mnt]NFS op OP_GETATTR got error NFS4ERR_WRONGSEC causing recovery action NR_WRONGSEC. > Aug 19 22:16:11 filur00 nfs: [ID 581112 kern.info] NOTICE: [NFS4][Server: testy.it.liu.se][Mntpt: /mnt]NFS Starting recovery for mount /mnt (mi 0xffffd064166f5000 mi_recovflags [0x4]) on server testy.it.liu.se, rnode_pt1 ./students (0xffffd0642f7083e0), rnode_pt2 (0x0) > Aug 19 22:16:11 filur00 nfs: [ID 711378 kern.info] NOTICE: [NFS4][Server: testy.it.liu.se][Mntpt: /mnt]NFS can't recover from NFS4ERR_WRONGSEC. error 1 for server testy.it.liu.se: rnode_pt1 ./students (0xffffd0642f7083e0) rnode_pt2 (0x0) It seems that Solaris/OmniOS handles that ?NFS4ERR_WRONGSEC? error a little bit ?harder? than Linux/FreeBSD does which is annoying. And here I?ve been telling people that Solaris/OmniOS is the ?Gold? standard when it comes to NFS :-). That it ?fails? the whole mount is a bit annoying?. (I suppose I can always work around this by NFS-mounting the sub-shares directly (or always using sec=krb5) but it?s still annoying?) ? [L?.U] System Administrator ITI-NET IT.LiU.SE +46-13-28 2786 -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at kebe.com Sat Aug 19 21:30:24 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sat, 19 Aug 2017 17:30:24 -0400 Subject: [OmniOS-discuss] NFSv4 (client) strange behaviour In-Reply-To: <91970C9E-33E2-4E56-AF8C-CB77BD3C1B0A@ifm.liu.se> References: <91970C9E-33E2-4E56-AF8C-CB77BD3C1B0A@ifm.liu.se> Message-ID: 1.) Which OmniOS release? Make sure it's a recent one before drawing conclusions. 2.) Have you queried the larger illumos mailing list? I know there are several open NFSv4 issues still there, and if you have a reproducible test case, it may be helpful. Dan From peter at ifm.liu.se Sat Aug 19 21:54:47 2017 From: peter at ifm.liu.se (Peter Eriksson) Date: Sat, 19 Aug 2017 23:54:47 +0200 Subject: [OmniOS-discuss] NFSv4 (client) strange behaviour In-Reply-To: References: <91970C9E-33E2-4E56-AF8C-CB77BD3C1B0A@ifm.liu.se> Message-ID: Fairly recent - OmniOS v11 r151022m - omnios-r151022-5e982daae6 :-) But since I see the same behaviour on a stone-age Solaris 10 client I suppose that part of the kernel code hasn?t changed much? I?ll try the Illumos list. ? [L?.U] System Administrator ITI-NET IT.LiU.SE +46-13-28 2786 > On 19 Aug 2017, at 23:30, Dan McDonald wrote: > > 1.) Which OmniOS release? Make sure it's a recent one before drawing conclusions. > > 2.) Have you queried the larger illumos mailing list? I know there are several open NFSv4 issues still there, and if you have a reproducible test case, it may be helpful. > > Dan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabio at fabiorabelo.wiki.br Sun Aug 20 23:02:34 2017 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Sun, 20 Aug 2017 20:02:34 -0300 Subject: [OmniOS-discuss] new boot environment Message-ID: Hi to all There are a way to force the creation of a new boot environment ? Thanks in advance F?bio Rabelo From fabio at fabiorabelo.wiki.br Sun Aug 20 23:28:37 2017 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Sun, 20 Aug 2017 20:28:37 -0300 Subject: [OmniOS-discuss] manteinance mode Message-ID: hi to all A system, with 3 years on line, no issue at all, passed to a power failure today, and when it boots, I have several msg like this : svc.startd[10] : svc:/system/boot-archive:default: method or service exit timed out. killing contract 16. svcadm clear makes any difference ... any help, please !!! F?bio Rabelo From lists at mcintyreweb.com Sun Aug 20 23:39:14 2017 From: lists at mcintyreweb.com (Hugh McIntyre) Date: Sun, 20 Aug 2017 16:39:14 -0700 Subject: [OmniOS-discuss] manteinance mode In-Reply-To: References: Message-ID: <85f880d6-58aa-2c08-bffa-b59bf92a4390@mcintyreweb.com> What does /var/svc/log/system-boot-archive:default.log say near the end? Hugh. On 8/20/17 4:28 PM, F?bio Rabelo wrote: > hi to all > > A system, with 3 years on line, no issue at all, passed to a power > failure today, and when it boots, I have several msg like this : > > svc.startd[10] : svc:/system/boot-archive:default: method or service > exit timed out. killing contract 16. > > svcadm clear makes any difference ... > > any help, please !!! > > > F?bio Rabelo > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > From danmcd at kebe.com Mon Aug 21 00:24:53 2017 From: danmcd at kebe.com (Dan McDonald) Date: Sun, 20 Aug 2017 20:24:53 -0400 Subject: [OmniOS-discuss] new boot environment In-Reply-To: References: Message-ID: "beadm create newBEname" Read the beadm(1M) man page for more details. Dan Sent from my iPhone (typos, autocorrect, and all) > On Aug 20, 2017, at 7:02 PM, F?bio Rabelo wrote: > > Hi to all > > There are a way to force the creation of a new boot environment ? > > > Thanks in advance > > > F?bio Rabelo > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From oliver.weinmann at telespazio-vega.de Mon Aug 21 07:59:36 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Mon, 21 Aug 2017 07:59:36 +0000 Subject: [OmniOS-discuss] Constantly losing nfs shares smb shares? Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BDF787@gedaevw60.a.space.corp> Hi, I have no clue why but on our omnios box (151022k) we are constantly losing all our nfs and smb shares. To fix it I have two shell scripts that just reset the sharenfs and sharesmb options. But this is not really a good fix as it happens at random times. I don't know where to start investigating. I have nothing suspicious in /var/adm/messages. Best Regards, Oliver [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png] Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png URL: From jimklimov at cos.ru Mon Aug 21 08:42:07 2017 From: jimklimov at cos.ru (Jim Klimov) Date: Mon, 21 Aug 2017 08:42:07 +0000 Subject: [OmniOS-discuss] new boot environment In-Reply-To: References: Message-ID: <0037290E-1E9E-4D85-ABDE-EFF1ECEAB944@cos.ru> On August 21, 2017 2:24:53 AM GMT+02:00, Dan McDonald wrote: >"beadm create newBEname" > >Read the beadm(1M) man page for more details. > >Dan > >Sent from my iPhone (typos, autocorrect, and all) > >> On Aug 20, 2017, at 7:02 PM, F?bio Rabelo >wrote: >> >> Hi to all >> >> There are a way to force the creation of a new boot environment ? >> >> >> Thanks in advance >> >> >> F?bio Rabelo >> _______________________________________________ >> 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 Also if you need it in conjunction with installation of packages, see `pkg install --require-new-be --be-name myNewBE pkgnames...` And then you have to reboot into that BE. Also there are backup BEs in the command, where it clones off to freeze the current state, and then changes the "live" current state (assuming packages not requiring a reboot). Jim -- Typos courtesy of K-9 Mail on my Android From al.slater at scluk.com Mon Aug 21 10:22:03 2017 From: al.slater at scluk.com (Al Slater) Date: Mon, 21 Aug 2017 11:22:03 +0100 Subject: [OmniOS-discuss] Problem updating OmniOS machines Message-ID: I have an number of omnios boxes running r151022, all upgraded from r151014. Currently uname says omnios-r151022-f9693432c2 All but one of them are failing to update. The process just stops after "Downloading linked" for each zone with no error message, but with a return code of 1. Each machine said I had to upgrade pkg first, which was done. aslate-admin at mars:/export/home/aslate-admin$ sudo pkg update -r Packages to update: 123 Create boot environment: Yes Create backup boot environment: No Planning linked: 0/8 done; 1 working: zone:qa-redis1 Linked image 'zone:qa-redis1' output: | Packages to update: 14 ` Planning linked: 1/8 done; 1 working: zone:qa-redis3 Linked image 'zone:qa-redis3' output: | Packages to update: 14 ` Planning linked: 2/8 done; 1 working: zone:qa-seclb1 Linked image 'zone:qa-seclb1' output: | Packages to update: 14 ` Planning linked: 3/8 done; 1 working: zone:pg-ugweb01 Linked image 'zone:pg-ugweb01' output: | Packages to update: 14 ` Planning linked: 4/8 done; 1 working: zone:qa-b2cweb05 Linked image 'zone:qa-b2cweb05' output: | Packages to update: 14 ` Planning linked: 5/8 done; 1 working: zone:base Linked image 'zone:base' output: | Packages to update: 14 ` Planning linked: 6/8 done; 1 working: zone:qa-lb1 Linked image 'zone:qa-lb1' output: | Packages to update: 14 ` Planning linked: 7/8 done; 1 working: zone:qa-tseclb1 Linked image 'zone:qa-tseclb1' output: | Packages to update: 14 ` Planning linked: 8/8 done DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 123/123 3553/3553 79.6/79.6 0B/s Downloading linked: 0/8 done; 1 working: zone:qa-redis1 Downloading linked: 1/8 done; 1 working: zone:qa-redis3 Downloading linked: 2/8 done; 1 working: zone:qa-seclb1 Downloading linked: 3/8 done; 1 working: zone:pg-ugweb01 Downloading linked: 4/8 done; 1 working: zone:qa-b2cweb05 Downloading linked: 5/8 done; 1 working: zone:base Downloading linked: 6/8 done; 1 working: zone:qa-lb1 Downloading linked: 7/8 done; 1 working: zone:qa-tseclb1 Linked progress: /aslate-admin at mars:/export/home/aslate-admin$ echo $? 1 Running with -v doesn't give any hints. The machines are updating from my own pkg repo, which is kept in sync with the omniosce repo. Any ideas what is wrong? -- Al Slater From fabio at fabiorabelo.wiki.br Mon Aug 21 10:39:24 2017 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Mon, 21 Aug 2017 07:39:24 -0300 Subject: [OmniOS-discuss] Fwd: manteinance mode In-Reply-To: References: <85f880d6-58aa-2c08-bffa-b59bf92a4390@mcintyreweb.com> <8aff3b53-dd5a-af7b-767b-5c58cc26278a@mcintyreweb.com> Message-ID: sorry, just realise, msg are not beeing forward to forum F?bio Rabelo ---------- Forwarded message ---------- From: F?bio Rabelo Date: 2017-08-21 7:06 GMT-03:00 Subject: Re: [OmniOS-discuss] manteinance mode To: Hugh McIntyre Hi The first link I did not have found, will try . Links 2 and 3 allready tryed, no change . The thing is : nobody changed anything ! history : Electric company warns abou aoutage sunday moring system is shut down late saturday, no msg, no errors, nothing, power off with any event Sunday, late afternoon , system power up . errors ... There are another Solaris system in the same site, same instalation timeframe, no errors .. To sum to history, I created a new BE, tryed to import the pool, msg "no available pool to import" . In maitenance mode, it show pool mounted and health . Complete lost here .... Will try to change boot disk, install evething from scracth, and try impor pool again F?bio Rabelo 2017-08-21 3:20 GMT-03:00 Hugh McIntyre : > Sorry, I can't reliably help beyond this. You should probably post back to > the Illumos or OmniOS lists. > > There are a few on-line search results matching your error, for example: > > https://openindiana.org/pipermail/openindiana-discuss/2012-May/008038.html > > - From 2012: attempts to increase timeout > (may fix your issue but doubtful) > > https://community.oracle.com/thread/3764402?tstart=0 > > - Suggests you changed some configuration which broke things. > - Maybe broken vfstab, or some other config change > > http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html > > - Similar config change > - This suggests to rebuild the boot archive. But not sure > this is safe unless you understand the error > > Hugh. > > > > > On 8/20/17 6:27 PM, F?bio Rabelo wrote: >> >> I rebooted the system, and now the file has a content . >> >> In the attachment >> >> sorry the jpeg, the system do not allow ssh connection, I cannot cut >> and paste anything . >> >> F?bio Rabelo >> >> 2017-08-20 22:19 GMT-03:00 Hugh McIntyre : >>> >>> OK, then probably /var/svc/log/system-boot-archive. >>> >>> Essentially, /var/svc/log should contain logs for the services, hopefully >>> including the reason for any errors. The only exception should be early >>> in >>> the boot process if the root FS is not mounted read/write. >>> >>> I'm not sure why you're seeing the error you are seeing unless there is >>> some >>> other console message referring to a hardware timeout before the >>> svc.startd >>> message below? >>> >>> Hugh. >>> >>> >>> >>> >>> On 8/20/17 5:52 PM, F?bio Rabelo wrote: >>>> >>>> >>>> thanks for you help >>>> >>>> But, the are no file with that name in the folder . >>>> >>>> files startting with boot are : >>>> >>>> system-boot-archive-update >>>> system-boot-archive >>>> system-boot-config >>>> system-initial-boot >>>> >>>> comand run where : >>>> >>>> ls |grep boot >>>> >>>> >>>> F?bio Rabelo >>>> >>>> 2017-08-20 20:39 GMT-03:00 Hugh McIntyre : >>>>> >>>>> >>>>> What does /var/svc/log/system-boot-archive:default.log say near the >>>>> end? >>>>> >>>>> Hugh. >>>>> >>>>> >>>>> >>>>> On 8/20/17 4:28 PM, F?bio Rabelo wrote: >>>>>> >>>>>> >>>>>> >>>>>> hi to all >>>>>> >>>>>> A system, with 3 years on line, no issue at all, passed to a power >>>>>> failure today, and when it boots, I have several msg like this : >>>>>> >>>>>> svc.startd[10] : svc:/system/boot-archive:default: method or service >>>>>> exit timed out. killing contract 16. >>>>>> >>>>>> svcadm clear makes any difference ... >>>>>> >>>>>> any help, please !!! >>>>>> >>>>>> >>>>>> F?bio Rabelo >>>>>> _______________________________________________ >>>>>> 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 From fabio at fabiorabelo.wiki.br Mon Aug 21 10:44:27 2017 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Mon, 21 Aug 2017 07:44:27 -0300 Subject: [OmniOS-discuss] Fwd: manteinance mode In-Reply-To: <8aff3b53-dd5a-af7b-767b-5c58cc26278a@mcintyreweb.com> References: <85f880d6-58aa-2c08-bffa-b59bf92a4390@mcintyreweb.com> <8aff3b53-dd5a-af7b-767b-5c58cc26278a@mcintyreweb.com> Message-ID: just realised, the pool are health, but the log drive shows missing ! Can it be the problem ? Wil try to deatach it . And : > The only thing I can think of is ... did you refresh the active service > manifest? > > e.g. > > svcadm refresh boot-archive:default no effect . F?bio Rabelo ---------- Forwarded message ---------- From: Hugh McIntyre Date: 2017-08-21 3:20 GMT-03:00 Subject: Re: [OmniOS-discuss] manteinance mode To: F?bio Rabelo Sorry, I can't reliably help beyond this. You should probably post back to the Illumos or OmniOS lists. There are a few on-line search results matching your error, for example: https://openindiana.org/pipermail/openindiana-discuss/2012-May/008038.html - From 2012: attempts to increase timeout (may fix your issue but doubtful) https://community.oracle.com/thread/3764402?tstart=0 - Suggests you changed some configuration which broke things. - Maybe broken vfstab, or some other config change http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html - Similar config change - This suggests to rebuild the boot archive. But not sure this is safe unless you understand the error Hugh. On 8/20/17 6:27 PM, F?bio Rabelo wrote: > > I rebooted the system, and now the file has a content . > > In the attachment > > sorry the jpeg, the system do not allow ssh connection, I cannot cut > and paste anything . > > F?bio Rabelo > > 2017-08-20 22:19 GMT-03:00 Hugh McIntyre : >> >> OK, then probably /var/svc/log/system-boot-archive. >> >> Essentially, /var/svc/log should contain logs for the services, hopefully >> including the reason for any errors. The only exception should be early in >> the boot process if the root FS is not mounted read/write. >> >> I'm not sure why you're seeing the error you are seeing unless there is some >> other console message referring to a hardware timeout before the svc.startd >> message below? >> >> Hugh. >> >> >> >> >> On 8/20/17 5:52 PM, F?bio Rabelo wrote: >>> >>> >>> thanks for you help >>> >>> But, the are no file with that name in the folder . >>> >>> files startting with boot are : >>> >>> system-boot-archive-update >>> system-boot-archive >>> system-boot-config >>> system-initial-boot >>> >>> comand run where : >>> >>> ls |grep boot >>> >>> >>> F?bio Rabelo >>> >>> 2017-08-20 20:39 GMT-03:00 Hugh McIntyre : >>>> >>>> >>>> What does /var/svc/log/system-boot-archive:default.log say near the end? >>>> >>>> Hugh. >>>> >>>> >>>> >>>> On 8/20/17 4:28 PM, F?bio Rabelo wrote: >>>>> >>>>> >>>>> >>>>> hi to all >>>>> >>>>> A system, with 3 years on line, no issue at all, passed to a power >>>>> failure today, and when it boots, I have several msg like this : >>>>> >>>>> svc.startd[10] : svc:/system/boot-archive:default: method or service >>>>> exit timed out. killing contract 16. >>>>> >>>>> svcadm clear makes any difference ... >>>>> >>>>> any help, please !!! >>>>> >>>>> >>>>> F?bio Rabelo >>>>> _______________________________________________ >>>>> 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 From fabio at fabiorabelo.wiki.br Mon Aug 21 12:28:46 2017 From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=) Date: Mon, 21 Aug 2017 09:28:46 -0300 Subject: [OmniOS-discuss] manteinance mode In-Reply-To: References: <85f880d6-58aa-2c08-bffa-b59bf92a4390@mcintyreweb.com> <8aff3b53-dd5a-af7b-767b-5c58cc26278a@mcintyreweb.com> Message-ID: OK . The BE with errors still with errors . The new BE, after trying to import the pool with missing log device, is working . So, I will change the default BE . Like all others msg with this error in all forums, this problem have no solution . To finish it, someone can direct me to a doc about how to change default BE ? Thanks everyone F?bio Rabelo 2017-08-21 7:44 GMT-03:00 F?bio Rabelo : > just realised, the pool are health, but the log drive shows missing ! > > Can it be the problem ? > > Wil try to deatach it . > > > And : > >> The only thing I can think of is ... did you refresh the active service >> manifest? >> >> e.g. >> >> svcadm refresh boot-archive:default > > > no effect . > > > F?bio Rabelo > > > > ---------- Forwarded message ---------- > From: Hugh McIntyre > Date: 2017-08-21 3:20 GMT-03:00 > Subject: Re: [OmniOS-discuss] manteinance mode > To: F?bio Rabelo > > > Sorry, I can't reliably help beyond this. You should probably post > back to the Illumos or OmniOS lists. > > There are a few on-line search results matching your error, for example: > > https://openindiana.org/pipermail/openindiana-discuss/2012-May/008038.html > > - From 2012: attempts to increase timeout > (may fix your issue but doubtful) > > https://community.oracle.com/thread/3764402?tstart=0 > > - Suggests you changed some configuration which broke things. > - Maybe broken vfstab, or some other config change > > http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html > > - Similar config change > - This suggests to rebuild the boot archive. But not sure > this is safe unless you understand the error > > Hugh. > > > > > On 8/20/17 6:27 PM, F?bio Rabelo wrote: >> >> I rebooted the system, and now the file has a content . >> >> In the attachment >> >> sorry the jpeg, the system do not allow ssh connection, I cannot cut >> and paste anything . >> >> F?bio Rabelo >> >> 2017-08-20 22:19 GMT-03:00 Hugh McIntyre : >>> >>> OK, then probably /var/svc/log/system-boot-archive. >>> >>> Essentially, /var/svc/log should contain logs for the services, hopefully >>> including the reason for any errors. The only exception should be early in >>> the boot process if the root FS is not mounted read/write. >>> >>> I'm not sure why you're seeing the error you are seeing unless there is some >>> other console message referring to a hardware timeout before the svc.startd >>> message below? >>> >>> Hugh. >>> >>> >>> >>> >>> On 8/20/17 5:52 PM, F?bio Rabelo wrote: >>>> >>>> >>>> thanks for you help >>>> >>>> But, the are no file with that name in the folder . >>>> >>>> files startting with boot are : >>>> >>>> system-boot-archive-update >>>> system-boot-archive >>>> system-boot-config >>>> system-initial-boot >>>> >>>> comand run where : >>>> >>>> ls |grep boot >>>> >>>> >>>> F?bio Rabelo >>>> >>>> 2017-08-20 20:39 GMT-03:00 Hugh McIntyre : >>>>> >>>>> >>>>> What does /var/svc/log/system-boot-archive:default.log say near the end? >>>>> >>>>> Hugh. >>>>> >>>>> >>>>> >>>>> On 8/20/17 4:28 PM, F?bio Rabelo wrote: >>>>>> >>>>>> >>>>>> >>>>>> hi to all >>>>>> >>>>>> A system, with 3 years on line, no issue at all, passed to a power >>>>>> failure today, and when it boots, I have several msg like this : >>>>>> >>>>>> svc.startd[10] : svc:/system/boot-archive:default: method or service >>>>>> exit timed out. killing contract 16. >>>>>> >>>>>> svcadm clear makes any difference ... >>>>>> >>>>>> any help, please !!! >>>>>> >>>>>> >>>>>> F?bio Rabelo >>>>>> _______________________________________________ >>>>>> 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 From oliver.weinmann at telespazio-vega.de Mon Aug 21 12:53:06 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Mon, 21 Aug 2017 12:53:06 +0000 Subject: [OmniOS-discuss] ndmp backups what software are you using? Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> Hi, is anyone doing NDMP backups to tape? And if yes what software are you using? I have semi successfully configured BAREOS to do NDMP backups to disk. The only problem is that the content of zfs subfolders is not backed up. They are all empty. :( [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png] Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png URL: From bfriesen at simple.dallas.tx.us Mon Aug 21 13:11:08 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Mon, 21 Aug 2017 08:11:08 -0500 (CDT) Subject: [OmniOS-discuss] ndmp backups what software are you using? In-Reply-To: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> References: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> Message-ID: On Mon, 21 Aug 2017, Oliver Weinmann wrote: > Hi, > > is anyone doing NDMP backups to tape? And if yes what software are you using? > > I have semi successfully configured BAREOS to do NDMP backups to > disk. The only problem is that the content of zfs subfolders is not > backed up. They are all empty. :( What is a "zfs subfolder"? Are you refering to a distinct zfs filesystem? If so, the problem could be that the software you are using only backs up filesystems and does not recurse into other filesystems. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From oliver.weinmann at telespazio-vega.de Mon Aug 21 13:18:23 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Mon, 21 Aug 2017 13:18:23 +0000 Subject: [OmniOS-discuss] ndmp backups what software are you using? In-Reply-To: References: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BE0A65@gedaevw60.a.space.corp> Hi Bob, What I meant is e.g. root at omnios02:/tank/test# zfs list NAME USED AVAIL REFER MOUNTPOINT tank 187M 193G 23K /tank tank/test 185M 30.0G 25K /tank/test tank/test/sub1 184M 29.8G 184M /tank/test/sub1 tank/test/sub2 23K 30.0G 23K /tank/test/sub2 tank/test/sub3 23K 30.0G 23K /tank/test/sub3 tank/test/sub4 23K 30.0G 23K /tank/test/sub4 Taking a backup of tank I would like to have all it's (zfs) subfolders. I can get all the subfolders by specifying RECUSIVE=y as a meta parameter in bareos but the folders are all empty. No files are backed up this way. I wonder If I'm just missing a setting? Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller-----Original Message----- From: Bob Friesenhahn [mailto:bfriesen at simple.dallas.tx.us] Sent: Montag, 21. August 2017 15:11 To: Oliver Weinmann Cc: omnios-discuss Subject: Re: [OmniOS-discuss] ndmp backups what software are you using? On Mon, 21 Aug 2017, Oliver Weinmann wrote: > Hi, > > is anyone doing NDMP backups to tape? And if yes what software are you using? > > I have semi successfully configured BAREOS to do NDMP backups to disk. > The only problem is that the content of zfs subfolders is not backed > up. They are all empty. :( What is a "zfs subfolder"? Are you refering to a distinct zfs filesystem? If so, the problem could be that the software you are using only backs up filesystems and does not recurse into other filesystems. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From bfriesen at simple.dallas.tx.us Mon Aug 21 13:30:14 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Mon, 21 Aug 2017 08:30:14 -0500 (CDT) Subject: [OmniOS-discuss] ndmp backups what software are you using? In-Reply-To: <767138E0D064A148B03FE8EC1E9325A20138BE0A65@gedaevw60.a.space.corp> References: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> <767138E0D064A148B03FE8EC1E9325A20138BE0A65@gedaevw60.a.space.corp> Message-ID: On Mon, 21 Aug 2017, Oliver Weinmann wrote: > Hi Bob, > > What I meant is e.g. > > root at omnios02:/tank/test# zfs list > NAME USED AVAIL REFER MOUNTPOINT > tank 187M 193G 23K /tank > tank/test 185M 30.0G 25K /tank/test > tank/test/sub1 184M 29.8G 184M /tank/test/sub1 > tank/test/sub2 23K 30.0G 23K /tank/test/sub2 > tank/test/sub3 23K 30.0G 23K /tank/test/sub3 > tank/test/sub4 23K 30.0G 23K /tank/test/sub4 > > Taking a backup of tank I would like to have all it's (zfs) > subfolders. I can get all the subfolders by specifying RECUSIVE=y as > a meta parameter in bareos but the folders are all empty. No files > are backed up this way. I wonder If I'm just missing a setting? It seems like you are asking us a question about Bareos and not OmniOS. Does Bareos have a user support forum or mailing list where you can ask your question? Each zfs filesystem mountpoint will behave the same as if a traditional filesystem was mounted to that path. Traditional archive programs like 'tar' and 'find+cpio' would produce a result similar to what you are seeing from bareos by default. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From oliver.weinmann at telespazio-vega.de Mon Aug 21 13:32:40 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Mon, 21 Aug 2017 13:32:40 +0000 Subject: [OmniOS-discuss] ndmp backups what software are you using? In-Reply-To: References: <767138E0D064A148B03FE8EC1E9325A20138BE0A40@gedaevw60.a.space.corp> <767138E0D064A148B03FE8EC1E9325A20138BE0A65@gedaevw60.a.space.corp> Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BE0A84@gedaevw60.a.space.corp> Hi, Sorry I didn't mean to have support on bareos backup. I have already asked this question on their mailinglist. I just wanted to know if users are doing ndmp backups and what software they are using. << Traditional archive programs like 'tar' and 'find+cpio' would produce a result similar to what you are seeing from bareos by default. >> Thanks for this tip. I'm doing dump. I will now try tar instead. :) Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller-----Original Message----- From: Bob Friesenhahn [mailto:bfriesen at simple.dallas.tx.us] Sent: Montag, 21. August 2017 15:30 To: Oliver Weinmann Cc: omnios-discuss Subject: RE: [OmniOS-discuss] ndmp backups what software are you using? On Mon, 21 Aug 2017, Oliver Weinmann wrote: > Hi Bob, > > What I meant is e.g. > > root at omnios02:/tank/test# zfs list > NAME USED AVAIL REFER MOUNTPOINT > tank 187M 193G 23K /tank > tank/test 185M 30.0G 25K /tank/test > tank/test/sub1 184M 29.8G 184M /tank/test/sub1 > tank/test/sub2 23K 30.0G 23K /tank/test/sub2 > tank/test/sub3 23K 30.0G 23K /tank/test/sub3 > tank/test/sub4 23K 30.0G 23K /tank/test/sub4 > > Taking a backup of tank I would like to have all it's (zfs) > subfolders. I can get all the subfolders by specifying RECUSIVE=y as a > meta parameter in bareos but the folders are all empty. No files are > backed up this way. I wonder If I'm just missing a setting? It seems like you are asking us a question about Bareos and not OmniOS. Does Bareos have a user support forum or mailing list where you can ask your question? Each zfs filesystem mountpoint will behave the same as if a traditional filesystem was mounted to that path. Traditional archive programs like 'tar' and 'find+cpio' would produce a result similar to what you are seeing from bareos by default. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From tobi at oetiker.ch Mon Aug 21 13:42:37 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 21 Aug 2017 15:42:37 +0200 (CEST) Subject: [OmniOS-discuss] ANNOUNCEMENT: Security Update bzip2 Vulnerability Message-ID: <1627656579.1332283.1503322957691.JavaMail.zimbra@oetiker.ch> OmniOS Community Edition has updated the bzip2 Package for r151022 and bloody to fix CVE-2016-3189 A remote user can create a specially crafted bzip2 file that, when processed for recovery by the target application, will trigger a use-after-free memory error in bzip2recover and cause the target application to crash. This release does NOT require a reboot. -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobi at oetiker.ch Mon Aug 21 13:45:53 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 21 Aug 2017 15:45:53 +0200 (CEST) Subject: [OmniOS-discuss] ANNOUNCEMENT: OmniOSce Release Schedule Message-ID: <1259294947.1332469.1503323153856.JavaMail.zimbra@oetiker.ch> In response to our call for someone to step up to take over responsibility to maintain OmniOS LTS releases we received a number of detailed responses, but only from people interested in using the product and none who wanted to help maintain it. After careful consideration of all the input, the OmniOSce Association has decided to continue maintaining LTS releases of OmniOSce. LTS releases will be supported for three years with intervening stable releases being supported for one year. LTS releases will therefore overlap for a year to allow time for validation and upgrade even in complex environments. Regular stable releases will overlap for six months. This results in the following release schedule with r151024 being targeted for the first week of November 2017. cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: release-plan.png Type: image/png Size: 94916 bytes Desc: not available URL: From dirk.willems at exitas.be Mon Aug 21 15:33:01 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Mon, 21 Aug 2017 17:33:01 +0200 Subject: [OmniOS-discuss] tar version of OmniOSCE Message-ID: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> Hello, maybe a strange question but I was looking for the version of tar if its possible ? I tried some things but not exactly what I want, also looked in the pkg list but I didn't seem to find it ? root at GNUHealth:~# strings /bin/tar | grep -i version _lib_version tar: file # %llu: (%s) UTF-8 conversion failed. tar: conversion routines not available for current locale. file # %llu: (%s) UTF-8 conversion failed. tar: invalid character in UTF-8 conversion of '%s' tar: conversion to UTF-8 aborted for '%s'. tar: file # %llu: UTF-8 conversion failed. file (%s): UTF-8 conversion failed. tar: file (%s): UTF-8 conversion failed. _lib_version .SUNW_version Kind Regards, Dirk -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From bfriesen at simple.dallas.tx.us Mon Aug 21 16:08:00 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Mon, 21 Aug 2017 11:08:00 -0500 (CDT) Subject: [OmniOS-discuss] tar version of OmniOSCE In-Reply-To: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> References: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> Message-ID: On Mon, 21 Aug 2017, Dirk Willems wrote: > Hello, > > > maybe a strange question but I was looking for the version of tar if its > possible ? It seems that you are wrongly assuming that /bin/tar is GNU tar and thus is independently versioned and supports an option to report a version. This is a Unix system! Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From eric.sproul at circonus.com Mon Aug 21 16:09:52 2017 From: eric.sproul at circonus.com (Eric Sproul) Date: Mon, 21 Aug 2017 12:09:52 -0400 Subject: [OmniOS-discuss] tar version of OmniOSCE In-Reply-To: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> References: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> Message-ID: On Mon, Aug 21, 2017 at 11:33 AM, Dirk Willems wrote: > Hello, > > > maybe a strange question but I was looking for the version of tar if its > possible ? > > > I tried some things but not exactly what I want, also looked in the pkg > list but I didn't seem to find it ? > > > ?Hi Dirk, /usr/bin/tar ?is part of the core operating system package, pkg://omnios/SUNWcs. It is "Solaris tar", which was derived from version 7 UNIX a long time ago [1]. As such, I'm not aware that it was ever versioned separately from the Solaris OS, nor from illumos, as a fork of OpenSolaris. Someone with deeper Solaris/UNIX history knowledge could probably share some insights. :) Eric [1] https://en.wikipedia.org/wiki/Tar_(computing)#Key_implementations -------------- next part -------------- An HTML attachment was scrubbed... URL: From dirk.willems at exitas.be Mon Aug 21 16:58:22 2017 From: dirk.willems at exitas.be (Dirk Willems) Date: Mon, 21 Aug 2017 18:58:22 +0200 Subject: [OmniOS-discuss] tar version of OmniOSCE In-Reply-To: References: <1f7ab5b5-62f1-f1bd-2d01-7bcae9505c91@exitas.be> Message-ID: <6273bbc2-b0a3-d3f0-15c9-0e23991f3b3e@exitas.be> Thank you very much for clarifying. Kind Regards, Dirk On 21-08-17 18:09, Eric Sproul wrote: > > > On Mon, Aug 21, 2017 at 11:33 AM, Dirk Willems > wrote: > > Hello, > > > maybe a strange question but I was looking for the version of tar > if its possible ? > > > I tried some things but not exactly what I want, also looked in > the pkg list but I didn't seem to find it ? > > > ?Hi Dirk, > /usr/bin/tar ?is part of the core operating system > package, pkg://omnios/SUNWcs. It is "Solaris tar", which was derived > from version 7 UNIX a long time ago [1]. As such, I'm not aware that > it was ever versioned separately from the Solaris OS, nor from > illumos, as a fork of OpenSolaris. > > Someone with deeper Solaris/UNIX history knowledge could probably > share some insights. :) > Eric > > [1] https://en.wikipedia.org/wiki/Tar_(computing)#Key_implementations > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -- Dirk Willems System Engineer +32 (0)3 443 12 38 Dirk.Willems at exitas.be Quality. Passion. Personality www.exitas.be | Veldkant 31 | 2550 Kontich Illumos OmniOS Installation and Configuration Implementation Specialist. Oracle Solaris 11 Installation and Configuration Certified Implementation Specialist. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SmallPhoenixLogotypeRGB.png Type: image/png Size: 4648 bytes Desc: not available URL: From al.slater at scluk.com Wed Aug 23 07:39:48 2017 From: al.slater at scluk.com (Al Slater) Date: Wed, 23 Aug 2017 08:39:48 +0100 Subject: [OmniOS-discuss] Problem updating OmniOS machines In-Reply-To: References: Message-ID: Does anyone have any ideas what the cause is here, or how to debug it? On 21/08/2017 11:22, Al Slater wrote: > I have an number of omnios boxes running r151022, all upgraded from > r151014. Currently uname says omnios-r151022-f9693432c2 > > All but one of them are failing to update. The process just stops after > "Downloading linked" for each zone with no error message, but with a > return code of 1. Each machine said I had to upgrade pkg first, which > was done. > > > aslate-admin at mars:/export/home/aslate-admin$ sudo pkg update -r > Packages to update: 123 > Create boot environment: Yes > Create backup boot environment: No > > Planning linked: 0/8 done; 1 working: zone:qa-redis1 > Linked image 'zone:qa-redis1' output: > | Packages to update: 14 > ` > Planning linked: 1/8 done; 1 working: zone:qa-redis3 > Linked image 'zone:qa-redis3' output: > | Packages to update: 14 > ` > Planning linked: 2/8 done; 1 working: zone:qa-seclb1 > Linked image 'zone:qa-seclb1' output: > | Packages to update: 14 > ` > Planning linked: 3/8 done; 1 working: zone:pg-ugweb01 > Linked image 'zone:pg-ugweb01' output: > | Packages to update: 14 > ` > Planning linked: 4/8 done; 1 working: zone:qa-b2cweb05 > Linked image 'zone:qa-b2cweb05' output: > | Packages to update: 14 > ` > Planning linked: 5/8 done; 1 working: zone:base > Linked image 'zone:base' output: > | Packages to update: 14 > ` > Planning linked: 6/8 done; 1 working: zone:qa-lb1 > Linked image 'zone:qa-lb1' output: > | Packages to update: 14 > ` > Planning linked: 7/8 done; 1 working: zone:qa-tseclb1 > Linked image 'zone:qa-tseclb1' output: > | Packages to update: 14 > ` > Planning linked: 8/8 done > DOWNLOAD PKGS FILES XFER (MB) > SPEED > Completed 123/123 3553/3553 79.6/79.6 > 0B/s > > Downloading linked: 0/8 done; 1 working: zone:qa-redis1 > Downloading linked: 1/8 done; 1 working: zone:qa-redis3 > Downloading linked: 2/8 done; 1 working: zone:qa-seclb1 > Downloading linked: 3/8 done; 1 working: zone:pg-ugweb01 > Downloading linked: 4/8 done; 1 working: zone:qa-b2cweb05 > Downloading linked: 5/8 done; 1 working: zone:base > Downloading linked: 6/8 done; 1 working: zone:qa-lb1 > Downloading linked: 7/8 done; 1 working: zone:qa-tseclb1 > Linked progress: /aslate-admin at mars:/export/home/aslate-admin$ echo $? > 1 > > > Running with -v doesn't give any hints. > > The machines are updating from my own pkg repo, which is kept in sync > with the omniosce repo. > > Any ideas what is wrong? > -- Al Slater From oliver.weinmann at telespazio-vega.de Thu Aug 24 07:25:55 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Thu, 24 Aug 2017 07:25:55 +0000 Subject: [OmniOS-discuss] zfs recv causes system to crash / hang Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BE4398@gedaevw60.a.space.corp> Hi all, every time trying to do zfs send | recv between OmniOS 151022.x and Nexenta 4.0.5x the Nexenta node crashes. This is very critical to us as we either want to use the OmniOS system for DR or migrate some files between the two. I raised a ticket with Nexenta and they pointed me in the right direction. It seems that this problem had already been reported on Illumos mailinglist. So far no real fix has been provided. https://www.mail-archive.com/discuss at lists.illumos.org/msg02699.html The only way to fix this is either patch the receiving side (Nexenta). They have not done this for 4.0.5.x yet. But I was told that it will be done in 5.1 and it is planned to upstream the fix to Illumos. 6393 zfs receive a full send as a clone or the sending side. 6536 zfs send: want a way to disable setting of DRR_FLAG_FREERECORDS But the patch for the sending side (OmniOS) doesn't work. The last thing on the post is an advice to implement this fix on the sending side: https://gist.github.com/pcd1193182/fcb9f8d43dcbcf32ba736ea7ef600658 It seems that the problem not only affects zfs send | recv between Illumos based an Nexenta systems. Nexenta told us that they have a fix for NS 5.1 but currently upgrading to 5.x is not an option for us as this version has some limitations and it currently doesn't have this very important fix implemented: https://www.illumos.org/issues/8543 Is there anyone else effected by this bug? Best Regards, Oliver [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png] Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png URL: From oliver.weinmann at telespazio-vega.de Thu Aug 24 07:56:49 2017 From: oliver.weinmann at telespazio-vega.de (Oliver Weinmann) Date: Thu, 24 Aug 2017 07:56:49 +0000 Subject: [OmniOS-discuss] Constantly losing nfs shares smb shares? In-Reply-To: <767138E0D064A148B03FE8EC1E9325A20138BDF787@gedaevw60.a.space.corp> References: <767138E0D064A148B03FE8EC1E9325A20138BDF787@gedaevw60.a.space.corp> Message-ID: <767138E0D064A148B03FE8EC1E9325A20138BE43EB@gedaevw60.a.space.corp> Hi, I have done some more investigation and I found the cause for this problem. It always happens when running zfs send from a Nexenta system. [cid:Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png] Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Oliver Weinmann Sent: Montag, 21. August 2017 10:00 To: omnios-discuss Subject: [OmniOS-discuss] Constantly losing nfs shares smb shares? Hi, I have no clue why but on our omnios box (151022k) we are constantly losing all our nfs and smb shares. To fix it I have two shell scripts that just reset the sharenfs and sharesmb options. But this is not really a good fix as it happens at random times. I don't know where to start investigating. I have nothing suspicious in /var/adm/messages. Best Regards, Oliver [cid:image001.png at 01D31CBE.95E4A530] Oliver Weinmann Senior Unix VMWare, Storage Engineer Telespazio VEGA Deutschland GmbH Europaplatz 5 - 64293 Darmstadt - Germany Ph: + 49 (0)6151 8257 744 | Fax: +49 (0)6151 8257 799 oliver.weinmann at telespazio-vega.de http://www.telespazio-vega.de Registered office/Sitz: Darmstadt, Register court/Registergericht: Darmstadt, HRB 89231; Managing Director/Gesch?ftsf?hrer: Sigmar Keller -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7535 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png Type: image/png Size: 7535 bytes Desc: Logo_Telespazio_180_px_signature_eng_b58fa623-e26d-4116-9230-766adacfe55e1111111111111.png URL: From chip at innovates.com Thu Aug 24 12:41:27 2017 From: chip at innovates.com (Schweiss, Chip) Date: Thu, 24 Aug 2017 07:41:27 -0500 Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance Message-ID: I just move one of my production systems to OmniOS CE 151022m from 151014 and my NFS performance has tanked. Here's a snapshot of nfssvrtop: 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, awrite: 9634 KB Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align% 3 10.28.17.1 0 0 0 0 0 0 0 0 0 0 0 0 0 3 all 0 0 0 0 0 0 0 0 0 0 0 0 0 4 10.28.17.1 9 0 0 0 0 0 0 0 0 0 0 0 0 4 10.28.16.160 17 0 0 0 0 0 0 0 0 0 0 0 0 4 10.28.16.127 20 0 0 0 0 0 0 0 0 0 0 0 0 4 10.28.16.113 74 6 6 0 0 48 56 0 1366 20824 0 0 100 4 10.28.16.64 338 16 0 36 3 476 0 1065 120 0 130 117390 100 4 10.28.16.54 696 68 0 91 5 2173 0 2916 52 0 93 142083 100 4 all 1185 90 6 127 8 2697 56 3996 151 20824 104 133979 100 The pool is not doing anything but serving NFS. Before the upgrade, the pool would sustain 20k NFS ops. Is there some significant change in NFS that I need to adjust its tuning? -Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at kebe.com Thu Aug 24 13:35:35 2017 From: danmcd at kebe.com (Dan McDonald) Date: Thu, 24 Aug 2017 09:35:35 -0400 Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance In-Reply-To: References: Message-ID: > On Aug 24, 2017, at 8:41 AM, Schweiss, Chip wrote: > > I just move one of my production systems to OmniOS CE 151022m from 151014 and my NFS performance has tanked. > > Here's a snapshot of nfssvrtop: > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, awrite: 9634 KB > Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align% > 3 10.28.17.1 0 0 0 0 0 0 0 0 0 0 0 0 0 > 3 all 0 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.17.1 9 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.160 17 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.127 20 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.113 74 6 6 0 0 48 56 0 1366 20824 0 0 100 > 4 10.28.16.64 338 16 0 36 3 476 0 1065 120 0 130 117390 100 > 4 10.28.16.54 696 68 0 91 5 2173 0 2916 52 0 93 142083 100 > 4 all 1185 90 6 127 8 2697 56 3996 151 20824 104 133979 100 > > The pool is not doing anything but serving NFS. Before the upgrade, the pool would sustain 20k NFS ops. > > Is there some significant change in NFS that I need to adjust its tuning? Oh my. I'd start pinging the illumos list on this. Also, are there any special tweaks you made in the 014 configuration? IF you did, I'd start back removing them and seeing what a default system does, just in case. I know Delphix and Nexenta still care about NFS quite a bit, so I can't believe something would be that bad. Maintainers: Check for NFS changes RIGHT AFTER 022 closed for blanket upstream pull-ins. Maybe it closed during a poor-performance window? Dan From chip at innovates.com Thu Aug 24 14:18:16 2017 From: chip at innovates.com (Schweiss, Chip) Date: Thu, 24 Aug 2017 09:18:16 -0500 Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance In-Reply-To: References: Message-ID: I switched back to 014 for now, it was too bad to inflict on my users. I have some new systems coming in soon that I'll test on r151022 before making them live. I will start with the NFS defaults. -Chip On Thu, Aug 24, 2017 at 8:35 AM, Dan McDonald wrote: > > > On Aug 24, 2017, at 8:41 AM, Schweiss, Chip wrote: > > > > I just move one of my production systems to OmniOS CE 151022m from > 151014 and my NFS performance has tanked. > > > > Here's a snapshot of nfssvrtop: > > > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 > KB, awrite: 9634 KB > > Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw > SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align% > > 3 10.28.17.1 0 0 0 0 0 0 > 0 0 0 0 0 0 0 > > 3 all 0 0 0 0 0 0 > 0 0 0 0 0 0 0 > > 4 10.28.17.1 9 0 0 0 0 0 > 0 0 0 0 0 0 0 > > 4 10.28.16.160 17 0 0 0 0 0 > 0 0 0 0 0 0 0 > > 4 10.28.16.127 20 0 0 0 0 0 > 0 0 0 0 0 0 0 > > 4 10.28.16.113 74 6 6 0 0 48 > 56 0 1366 20824 0 0 100 > > 4 10.28.16.64 338 16 0 36 3 476 > 0 1065 120 0 130 117390 100 > > 4 10.28.16.54 696 68 0 91 5 2173 > 0 2916 52 0 93 142083 100 > > 4 all 1185 90 6 127 8 2697 > 56 3996 151 20824 104 133979 100 > > > > The pool is not doing anything but serving NFS. Before the upgrade, > the pool would sustain 20k NFS ops. > > > > Is there some significant change in NFS that I need to adjust its tuning? > > Oh my. > > I'd start pinging the illumos list on this. Also, are there any special > tweaks you made in the 014 configuration? IF you did, I'd start back > removing them and seeing what a default system does, just in case. > > I know Delphix and Nexenta still care about NFS quite a bit, so I can't > believe something would be that bad. > > Maintainers: Check for NFS changes RIGHT AFTER 022 closed for blanket > upstream pull-ins. Maybe it closed during a poor-performance window? > > Dan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bfriesen at simple.dallas.tx.us Thu Aug 24 16:04:19 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Thu, 24 Aug 2017 11:04:19 -0500 (CDT) Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance In-Reply-To: References: Message-ID: On Thu, 24 Aug 2017, Schweiss, Chip wrote: > I switched back to 014 for now, it was too bad to inflict on my users. > > I have some new systems coming in soon that I'll test on r151022 before > making them live. I will start with the NFS defaults. No evidence has been presented that there is a NFS problem. It could be an underlying zfs pool issue. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From richard.elling at richardelling.com Thu Aug 24 16:33:47 2017 From: richard.elling at richardelling.com (Richard Elling) Date: Thu, 24 Aug 2017 09:33:47 -0700 Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance In-Reply-To: References: Message-ID: <366D4C73-D0A3-417D-AEC8-4B462D41C431@richardelling.com> > On Aug 24, 2017, at 5:41 AM, Schweiss, Chip wrote: > > I just move one of my production systems to OmniOS CE 151022m from 151014 and my NFS performance has tanked. > > Here's a snapshot of nfssvrtop: > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, awrite: 9634 KB > Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align% > 3 10.28.17.1 0 0 0 0 0 0 0 0 0 0 0 0 0 > 3 all 0 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.17.1 9 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.160 17 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.127 20 0 0 0 0 0 0 0 0 0 0 0 0 > 4 10.28.16.113 74 6 6 0 0 48 56 0 1366 20824 0 0 100 > 4 10.28.16.64 338 16 0 36 3 476 0 1065 120 0 130 117390 100 > 4 10.28.16.54 696 68 0 91 5 2173 0 2916 52 0 93 142083 100 > 4 all 1185 90 6 127 8 2697 56 3996 151 20824 104 133979 100 > > The pool is not doing anything but serving NFS. Before the upgrade, the pool would sustain 20k NFS ops. The commit time is in microseconds, and it does look high. Is there a slog? ? richard > > Is there some significant change in NFS that I need to adjust its tuning? > > -Chip > > > > _______________________________________________ > 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 apenner.it at gmail.com Thu Aug 24 18:20:42 2017 From: apenner.it at gmail.com (Artem Penner) Date: Thu, 24 Aug 2017 18:20:42 +0000 Subject: [OmniOS-discuss] Upgrade to 151022m from 014 - horrible NFS performance In-Reply-To: <366D4C73-D0A3-417D-AEC8-4B462D41C431@richardelling.com> References: <366D4C73-D0A3-417D-AEC8-4B462D41C431@richardelling.com> Message-ID: Hi, can you post output of https://github.com/d-helios/dtrace/blob/master/zfs/zfs_rwlatency.d And if you have separate log device output of https://github.com/d-helios/dtrace/blob/master/zfs/zil_latency.d --- What is your nfs-server settings? (sharectl get nfs) ??, 24 ???. 2017 ?. ? 19:35, Richard Elling < richard.elling at richardelling.com>: > On Aug 24, 2017, at 5:41 AM, Schweiss, Chip wrote: > > I just move one of my production systems to OmniOS CE 151022m from 151014 > and my NFS performance has tanked. > > Here's a snapshot of nfssvrtop: > > 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite: 104 KB, > awrite: 9634 KB > Ver Client NFSOPS Reads SWrites AWrites Commits Rd_bw > SWr_bw AWr_bw Rd_t SWr_t AWr_t Com_t Align% > 3 10.28.17.1 0 0 0 0 0 0 > 0 0 0 0 0 0 0 > 3 all 0 0 0 0 0 0 > 0 0 0 0 0 0 0 > 4 10.28.17.1 9 0 0 0 0 0 > 0 0 0 0 0 0 0 > 4 10.28.16.160 17 0 0 0 0 0 > 0 0 0 0 0 0 0 > 4 10.28.16.127 20 0 0 0 0 0 > 0 0 0 0 0 0 0 > 4 10.28.16.113 74 6 6 0 0 48 > 56 0 1366 20824 0 0 100 > 4 10.28.16.64 338 16 0 36 3 476 > 0 1065 120 0 130 117390 100 > 4 10.28.16.54 696 68 0 91 5 2173 > 0 2916 52 0 93 142083 100 > 4 all 1185 90 6 127 8 2697 > 56 3996 151 20824 104 133979 100 > > The pool is not doing anything but serving NFS. Before the upgrade, the > pool would sustain 20k NFS ops. > > > The commit time is in microseconds, and it does look high. Is there a slog? > ? richard > > > Is there some significant change in NFS that I need to adjust its tuning? > > -Chip > > > > _______________________________________________ > 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 paul.jochum at nokia.com Thu Aug 24 18:31:13 2017 From: paul.jochum at nokia.com (Paul Jochum) Date: Thu, 24 Aug 2017 13:31:13 -0500 Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository Message-ID: Hi All: I am working on updating a number of omnios machines from r151022 (under OmniOS TI) to R151022 (under OmniOS CE). I am having problems updating one of my zones. I am at the point now where I have unset all of the publishers in that zone, but I can not add the omniosce publisher. # pkg publisher PUBLISHER TYPE STATUS P LOCATION # # /usr/bin/pkg set-publisher -P -g https://pkg.omniosce.org/r151022/core/ omnios pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a valid pkg repository. Please verify the repository's location and the client's network configuration. Additional details: Unable to contact valid package repository Encountered the following error(s): Unable to contact any configured publishers. This is likely a network configuration problem. Unable to locate a CA directory: /etc/openssl/certs Secure connection is not available. This worked fine on the host of that zone, and on other zones (located on other hosts, but all at the same level of software). Any suggestions on how to fix this? (And I checked, there is no /etc/openssl directory on this or any of my other omnios machines, but there is the /etc/ssl/certs directory and it looks very similar to other /etc/ssl/certs on machine which did not have a problem updating the publisher) thanks Paul paul.jochum at nokia.com From jdg117 at elvis.arl.psu.edu Fri Aug 25 00:03:30 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Thu, 24 Aug 2017 20:03:30 -0400 Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: Your message of "Thu, 24 Aug 2017 13:31:13 CDT." References: Message-ID: <201708250003.v7P03U69018160@elvis.arl.psu.edu> In message , Paul Jochum writes : >configuration. >Additional details: > >Unable to contact valid package repository >Encountered the following error(s): >Unable to contact any configured publishers. >This is likely a network configuration problem. >Unable to locate a CA directory: /etc/openssl/certs >Secure connection is not available. > >This worked fine on the host of that zone, and on other zones (located >on other hosts, but all at the same level of software). Any suggestions >on how to fix this? (And I checked, there is no /etc/openssl directory >on this or any of my other omnios machines, but there is the >/etc/ssl/certs directory and it looks very similar to other >/etc/ssl/certs on machine which did not have a problem updating the >publisher) Shot in the dark assuming lipkg brand zone: # zoneadm -z $zone halt # zoneadm -z $zone detach # /usr/bin/wget -P $zonepath/root/etc/ssl/pkg \ https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem # pkg -R $zonepath/root set-publisher -P \ -g https://pkg.omniosce.org/r151022/core/ omnios # zoneadm -z $zone attach -U John groenveld at acm.org From omnios at citrus-it.net Fri Aug 25 11:45:48 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 25 Aug 2017 11:45:48 +0000 (UTC) Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: References: Message-ID: On Thu, 24 Aug 2017, Paul Jochum wrote: ; Hi All: ; ; I am working on updating a number of omnios machines from r151022 (under ; OmniOS TI) to R151022 (under OmniOS CE). I am having problems updating one of ; my zones. I am at the point now where I have unset all of the publishers in ; that zone, but I can not add the omniosce publisher. ; ; # pkg publisher ; PUBLISHER TYPE STATUS P LOCATION ; # ; # /usr/bin/pkg set-publisher -P -g https://pkg.omniosce.org/r151022/core/ ; omnios Try setting it from the global zone. This looks like the zone doesn't have direct Internet connectivity. global% pkg -R /path/to/zone/root set-publisher ... Andy -- For OmniOSce Support, join us at https://gitter.im/omniosorg/Lobby -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From paul.jochum at nokia.com Fri Aug 25 13:29:52 2017 From: paul.jochum at nokia.com (Paul Jochum) Date: Fri, 25 Aug 2017 08:29:52 -0500 Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: <201708250003.v7P03U69018160@elvis.arl.psu.edu> References: <201708250003.v7P03U69018160@elvis.arl.psu.edu> Message-ID: Hi John and Andy: I tried it from the host, and received the same error message (output below). I know the host has internet connectivity, since I was able to use nearly the same command (without the -R option of the zone name/path), to set the publisher on the host. In the example below, the wget command copies the new cert to *.pem.1, (since I had previously used wget to set-publisher on the host), and that file is identical to the omniosce-ca.cert.pem file I used to set-publisher on the host. # zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running / ipkg shared 1 lss-ganglia02 running /rpool/zones/lss-ganglia02 lipkg shared # zoneadm -z lss-ganglia02 halt # zoneadm -z lss-ganglia02 detach # /usr/bin/wget -P /etc/ssl/pkg https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem --2017-08-25 08:19:59-- https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem Length: 2175 (2.1K) [application/x-x509-ca-cert] Saving to: '/etc/ssl/pkg/omniosce-ca.cert.pem.1' omniosce-ca.cert.pe 100%[===================>] 2.12K --.-KB/s in 0s 2017-08-25 08:20:00 (209 MB/s) - '/etc/ssl/pkg/omniosce-ca.cert.pem.1' saved [2175/2175] # /usr/bin/pkg -R /rpool/zones/lss-ganglia02/root set-publisher -P -g https://pkg.omniosce.org/r151022/core/ omnios pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a valid pkg repository. Please verify the repository's location and the client's network configuration. Additional details: Unable to contact valid package repository Encountered the following error(s): Unable to contact any configured publishers. This is likely a network configuration problem. Unable to locate a CA directory: /etc/openssl/certs Secure connection is not available. Thanks, Paul On 08/24/2017 07:03 PM, John D Groenveld wrote: > In message , Paul Jochum writes > : >> configuration. >> Additional details: >> >> Unable to contact valid package repository >> Encountered the following error(s): >> Unable to contact any configured publishers. >> This is likely a network configuration problem. >> Unable to locate a CA directory: /etc/openssl/certs >> Secure connection is not available. >> >> This worked fine on the host of that zone, and on other zones (located >> on other hosts, but all at the same level of software). Any suggestions >> on how to fix this? (And I checked, there is no /etc/openssl directory >> on this or any of my other omnios machines, but there is the >> /etc/ssl/certs directory and it looks very similar to other >> /etc/ssl/certs on machine which did not have a problem updating the >> publisher) > Shot in the dark assuming lipkg brand zone: > # zoneadm -z $zone halt > # zoneadm -z $zone detach > # /usr/bin/wget -P $zonepath/root/etc/ssl/pkg \ > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > # pkg -R $zonepath/root set-publisher -P \ > -g https://pkg.omniosce.org/r151022/core/ omnios > # zoneadm -z $zone attach -U > > John > groenveld at acm.org > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss From omnios at citrus-it.net Fri Aug 25 13:47:41 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 25 Aug 2017 13:47:41 +0000 (UTC) Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: References: <201708250003.v7P03U69018160@elvis.arl.psu.edu> Message-ID: What is the trust-anchor-directory property set to on the image root? % pkg property trust-anchor-directory PROPERTY VALUE trust-anchor-directory etc/ssl/pkg (or pkg -R /rpool/zones/lss-ganglia02/root property) Andy On Fri, 25 Aug 2017, Paul Jochum wrote: ; Hi John and Andy: ; ; I tried it from the host, and received the same error message (output ; below). I know the host has internet connectivity, since I was able to use ; nearly the same command (without the -R option of the zone name/path), to set ; the publisher on the host. In the example below, the wget command copies the ; new cert to *.pem.1, (since I had previously used wget to set-publisher on the ; host), and that file is identical to the omniosce-ca.cert.pem file I used to ; set-publisher on the host. ; ; # zoneadm list -cv ; ID NAME STATUS PATH BRAND IP ; 0 global running / ipkg shared ; 1 lss-ganglia02 running /rpool/zones/lss-ganglia02 lipkg shared ; # zoneadm -z lss-ganglia02 halt ; # zoneadm -z lss-ganglia02 detach ; # /usr/bin/wget -P /etc/ssl/pkg ; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem ; --2017-08-25 08:19:59-- ; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem ; ; Length: 2175 (2.1K) [application/x-x509-ca-cert] ; Saving to: '/etc/ssl/pkg/omniosce-ca.cert.pem.1' ; ; omniosce-ca.cert.pe 100%[===================>] 2.12K --.-KB/s in 0s ; ; 2017-08-25 08:20:00 (209 MB/s) - '/etc/ssl/pkg/omniosce-ca.cert.pem.1' saved ; [2175/2175] ; ; # /usr/bin/pkg -R /rpool/zones/lss-ganglia02/root set-publisher -P -g ; https://pkg.omniosce.org/r151022/core/ omnios ; pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a ; valid pkg repository. ; Please verify the repository's location and the client's network ; configuration. ; Additional details: ; ; Unable to contact valid package repository ; Encountered the following error(s): ; Unable to contact any configured publishers. ; This is likely a network configuration problem. ; Unable to locate a CA directory: /etc/openssl/certs ; Secure connection is not available. ; ; Thanks, ; Paul ; ; On 08/24/2017 07:03 PM, John D Groenveld wrote: ; > In message , Paul Jochum ; > writes ; > : ; > > configuration. ; > > Additional details: ; > > ; > > Unable to contact valid package repository ; > > Encountered the following error(s): ; > > Unable to contact any configured publishers. ; > > This is likely a network configuration problem. ; > > Unable to locate a CA directory: /etc/openssl/certs ; > > Secure connection is not available. ; > > ; > > This worked fine on the host of that zone, and on other zones (located ; > > on other hosts, but all at the same level of software). Any suggestions ; > > on how to fix this? (And I checked, there is no /etc/openssl directory ; > > on this or any of my other omnios machines, but there is the ; > > /etc/ssl/certs directory and it looks very similar to other ; > > /etc/ssl/certs on machine which did not have a problem updating the ; > > publisher) ; > Shot in the dark assuming lipkg brand zone: ; > # zoneadm -z $zone halt ; > # zoneadm -z $zone detach ; > # /usr/bin/wget -P $zonepath/root/etc/ssl/pkg \ ; > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem ; > # pkg -R $zonepath/root set-publisher -P \ ; > -g https://pkg.omniosce.org/r151022/core/ omnios ; > # zoneadm -z $zone attach -U ; > ; > John ; > groenveld at acm.org ; > _______________________________________________ ; > 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 ; -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From paul.jochum at nokia.com Fri Aug 25 14:37:05 2017 From: paul.jochum at nokia.com (Paul Jochum) Date: Fri, 25 Aug 2017 09:37:05 -0500 Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: References: <201708250003.v7P03U69018160@elvis.arl.psu.edu> Message-ID: <61a90746-61ff-f7c5-ed81-3cf43e83a8c8@nokia.com> Hi Andy: For both the host and the zone, the trust-anchor-directory returns etc/ssl/pkg From the host: # pkg property trust-anchor-directory PROPERTY VALUE trust-anchor-directory etc/ssl/pkg # pkg -R /rpool/zones/lss-ganglia02/root property trust-anchor-directory PROPERTY VALUE trust-anchor-directory etc/ssl/pkg # pkg -R /rpool/zones/lss-ganglia02/root property PROPERTY VALUE be-policy default ca-path /etc/openssl/certs check-certificate-revocation False content-update-policy default dehydrated [] flush-content-cache-on-success True mirror-discovery False preferred-authority publisher-search-order [] send-uuid True signature-policy verify signature-required-names [] trust-anchor-directory etc/ssl/pkg use-system-repo False Paul On 08/25/2017 08:47 AM, Andy Fiddaman wrote: > What is the trust-anchor-directory property set to on the image root? > > % pkg property trust-anchor-directory > PROPERTY VALUE > trust-anchor-directory etc/ssl/pkg > > (or pkg -R /rpool/zones/lss-ganglia02/root property) > > Andy > > On Fri, 25 Aug 2017, Paul Jochum wrote: > > ; Hi John and Andy: > ; > ; I tried it from the host, and received the same error message (output > ; below). I know the host has internet connectivity, since I was able to use > ; nearly the same command (without the -R option of the zone name/path), to set > ; the publisher on the host. In the example below, the wget command copies the > ; new cert to *.pem.1, (since I had previously used wget to set-publisher on the > ; host), and that file is identical to the omniosce-ca.cert.pem file I used to > ; set-publisher on the host. > ; > ; # zoneadm list -cv > ; ID NAME STATUS PATH BRAND IP > ; 0 global running / ipkg shared > ; 1 lss-ganglia02 running /rpool/zones/lss-ganglia02 lipkg shared > ; # zoneadm -z lss-ganglia02 halt > ; # zoneadm -z lss-ganglia02 detach > ; # /usr/bin/wget -P /etc/ssl/pkg > ; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > ; --2017-08-25 08:19:59-- > ; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > ; > ; Length: 2175 (2.1K) [application/x-x509-ca-cert] > ; Saving to: '/etc/ssl/pkg/omniosce-ca.cert.pem.1' > ; > ; omniosce-ca.cert.pe 100%[===================>] 2.12K --.-KB/s in 0s > ; > ; 2017-08-25 08:20:00 (209 MB/s) - '/etc/ssl/pkg/omniosce-ca.cert.pem.1' saved > ; [2175/2175] > ; > ; # /usr/bin/pkg -R /rpool/zones/lss-ganglia02/root set-publisher -P -g > ; https://pkg.omniosce.org/r151022/core/ omnios > ; pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a > ; valid pkg repository. > ; Please verify the repository's location and the client's network > ; configuration. > ; Additional details: > ; > ; Unable to contact valid package repository > ; Encountered the following error(s): > ; Unable to contact any configured publishers. > ; This is likely a network configuration problem. > ; Unable to locate a CA directory: /etc/openssl/certs > ; Secure connection is not available. > ; > ; Thanks, > ; Paul > ; > ; On 08/24/2017 07:03 PM, John D Groenveld wrote: > ; > In message , Paul Jochum > ; > writes > ; > : > ; > > configuration. > ; > > Additional details: > ; > > > ; > > Unable to contact valid package repository > ; > > Encountered the following error(s): > ; > > Unable to contact any configured publishers. > ; > > This is likely a network configuration problem. > ; > > Unable to locate a CA directory: /etc/openssl/certs > ; > > Secure connection is not available. > ; > > > ; > > This worked fine on the host of that zone, and on other zones (located > ; > > on other hosts, but all at the same level of software). Any suggestions > ; > > on how to fix this? (And I checked, there is no /etc/openssl directory > ; > > on this or any of my other omnios machines, but there is the > ; > > /etc/ssl/certs directory and it looks very similar to other > ; > > /etc/ssl/certs on machine which did not have a problem updating the > ; > > publisher) > ; > Shot in the dark assuming lipkg brand zone: > ; > # zoneadm -z $zone halt > ; > # zoneadm -z $zone detach > ; > # /usr/bin/wget -P $zonepath/root/etc/ssl/pkg \ > ; > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem > ; > # pkg -R $zonepath/root set-publisher -P \ > ; > -g https://pkg.omniosce.org/r151022/core/ omnios > ; > # zoneadm -z $zone attach -U > ; > > ; > John > ; > groenveld at acm.org > ; > _______________________________________________ > ; > 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 > ; From omnios at citrus-it.net Fri Aug 25 14:39:10 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Fri, 25 Aug 2017 14:39:10 +0000 (UTC) Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: <61a90746-61ff-f7c5-ed81-3cf43e83a8c8@nokia.com> References: <201708250003.v7P03U69018160@elvis.arl.psu.edu> <61a90746-61ff-f7c5-ed81-3cf43e83a8c8@nokia.com> Message-ID: On Fri, 25 Aug 2017, Paul Jochum wrote: ; ca-path /etc/openssl/certs pkg -R /... set-property ca-path /etc/ssl/certs Regards, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From paul.jochum at nokia.com Fri Aug 25 20:11:58 2017 From: paul.jochum at nokia.com (Paul Jochum) Date: Fri, 25 Aug 2017 15:11:58 -0500 Subject: [OmniOS-discuss] failure in set-publisher for a zone to the new omniosce repository In-Reply-To: References: <201708250003.v7P03U69018160@elvis.arl.psu.edu> <61a90746-61ff-f7c5-ed81-3cf43e83a8c8@nokia.com> Message-ID: <90385169-dc9c-81ca-ce29-f9f5e29ae291@nokia.com> Andy: Thank you, that fixed it. Strange, the host has that property set the same way (as /etc/openssl/certs), and it worked fine there. It is just this one zone that was having this problem, but now it is working :) Have a great weekend! Paul On 08/25/2017 09:39 AM, Andy Fiddaman wrote: > On Fri, 25 Aug 2017, Paul Jochum wrote: > > ; ca-path /etc/openssl/certs > > pkg -R /... set-property ca-path /etc/ssl/certs > > Regards, > > Andy From gearboxes at outlook.com Fri Aug 25 22:29:39 2017 From: gearboxes at outlook.com (Machine Man) Date: Fri, 25 Aug 2017 22:29:39 +0000 Subject: [OmniOS-discuss] Release 22 unable to boot with 4k disks Message-ID: I removed the data disks and installed on 2x 512 disks then added the 4k disks again boot fails. I'm not sure that this can be the expected behavior with 4k disks almost being the norm these days. Getting error panic bd_strategy 512 bytes I/O not multiple of block size. I downloaded the latest iso. Am I missing something? If I upgrade another release to R22 I assume it will not use the new loader? Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From gearboxes at outlook.com Fri Aug 25 22:37:17 2017 From: gearboxes at outlook.com (Machine Man) Date: Fri, 25 Aug 2017 22:37:17 +0000 Subject: [OmniOS-discuss] Release 22 unable to boot with 4k disks Message-ID: Ok doing a search I see this a known issue. I will install release 14 instead. From: Machine Man Sent: Friday, August 25, 2017 18:33 To: omnios-discuss at lists.omniti.com Subject: [OmniOS-discuss] Release 22 unable to boot with 4k disks I removed the data disks and installed on 2x 512 disks then added the 4k disks again boot fails. I'm not sure that this can be the expected behavior with 4k disks almost being the norm these days. Getting error panic bd_strategy 512 bytes I/O not multiple of block size. I downloaded the latest iso. Am I missing something? If I upgrade another release to R22 I assume it will not use the new loader? Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From henson at acm.org Fri Aug 25 22:39:15 2017 From: henson at acm.org (Paul B. Henson) Date: Fri, 25 Aug 2017 15:39:15 -0700 Subject: [OmniOS-discuss] Release 22 unable to boot with 4k disks In-Reply-To: References: Message-ID: <20170825223914.GN20158@bender.it-sys.cpp.edu> On Fri, Aug 25, 2017 at 10:29:39PM +0000, Machine Man wrote: > I removed the data disks and installed on 2x 512 disks then added the > 4k disks again boot fails. This is documented in the release notes: https://omnios.omniti.com/wiki.php/BSDLoader The release version of OmniTI omnios r151022 has a version of loader with issue 8303 which renders it incompatible with disks with logical 4k sectors (physical 4k is fine as long as they are presented logically as 512b). I believe the fix for this has been integrated into the Community Edition of omnios r151022: http://www.omniosce.org/ so I would suggest you upgrade your system to the latest update of that and try again. You also have the option of sticking with grub for r151022 rather than switching to loader, that is documented on the BSDLoader page as well; but only for upgrades, not for new installs I believe. From jim.oltman at gmail.com Sat Aug 26 21:19:30 2017 From: jim.oltman at gmail.com (Jim Oltman) Date: Sat, 26 Aug 2017 15:19:30 -0600 Subject: [OmniOS-discuss] Upgrade from 151022 to CE bootadm error Message-ID: Finally upgrading my 151022 to the CE version. There wer e no issues updating the package repo to the CE repo. When I ran the: sudo /usr/bin/pkg update -rv --backup-be-name 20170826_01_Pre_OmniOS-CE I received the following error after everything had been installed: DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 133/133 4670/4670 97.7/97.7 0B/s PHASE ITEMS Removing old actions 881/881 Installing new actions 968/968 Updating modified actions 4855/4855 Updating package state database Done Updating package cache 133/133 Updating image state Done Creating fast lookup database Done Reading search index Done Building new search index 418/418 pkg: '/sbin/bootadm update-archive -R /tmp/tmpvYNPxO' failed. with a return code of 1. Updating package cache 1/1 A clone of 20170826_Pre_OmniOS-CE exists and has been updated and activated. On the next boot the Boot Environment 20170826_Pre_OmniOS-CE-1 will be mounted on '/'. Reboot when ready to switch to this updated BE. Updating package cache 1/1 I rebooted then on bootup received an error about /usr mount fatally failed. I was able to boot to the previous BE. I tried the update again and received the same bootadm error as above. I'm not sure where to go from here. Hope someone can help. Thanks! Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From bfriesen at simple.dallas.tx.us Sun Aug 27 13:43:53 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Sun, 27 Aug 2017 08:43:53 -0500 (CDT) Subject: [OmniOS-discuss] Upgrade from 151022 to CE bootadm error In-Reply-To: References: Message-ID: On Sat, 26 Aug 2017, Jim Oltman wrote: > I rebooted then on bootup received an error about /usr mount fatally > failed. I was able to boot to the previous BE. I tried the update again > and received the same bootadm error as above. I'm not sure where to go > from here. Hope someone can help. Thanks! Make sure that you did not split /usr into its own filesystem outside of the root filesystem. OmniOS is not prepared for that. I made this mistake before. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From jimklimov at cos.ru Sun Aug 27 15:31:32 2017 From: jimklimov at cos.ru (Jim Klimov) Date: Sun, 27 Aug 2017 15:31:32 +0000 Subject: [OmniOS-discuss] Upgrade from 151022 to CE bootadm error In-Reply-To: References: Message-ID: On August 27, 2017 3:43:53 PM GMT+02:00, Bob Friesenhahn wrote: >On Sat, 26 Aug 2017, Jim Oltman wrote: > >> I rebooted then on bootup received an error about /usr mount fatally >> failed. I was able to boot to the previous BE. I tried the update >again >> and received the same bootadm error as above. I'm not sure where to >go >> from here. Hope someone can help. Thanks! > >Make sure that you did not split /usr into its own filesystem outside >of the root filesystem. OmniOS is not prepared for that. I made this >mistake before. > >Bob Or if you did - make sure the new system is prepared to handle this. My system layout managed by scripts below went through several OmniOS upgrades (finally to Bloody CE) just fine. It ain't every year that something has to be re-patched with them. https://github.com/jimklimov/illumos-splitroot-scripts -- Typos courtesy of K-9 Mail on my Android From jdg117 at elvis.arl.psu.edu Sun Aug 27 18:35:04 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Sun, 27 Aug 2017 14:35:04 -0400 Subject: [OmniOS-discuss] sendmail+SASL Message-ID: <201708271835.v7RIZ4mN004252@elvis.arl.psu.edu> Anyone have success configuring sendmail+libsasl under OmniOS? $ /etc/sasl/Sendmail.conf pwcheck_method: shadow log_level: 7 I'm getting no further than Andrew Watkins: illumos SASL doesn't provide a lot of debugging, so I'd like to trace libsasl and sendmail via printf. What build.sh invocation or minimum environment is required just to rebuild a couple packages once I git omnios-build? I do not want to build all of OmniOS and illumos and I want to link against my installed libraries vice Bloody. John groenveld at acm.org From tobi at oetiker.ch Mon Aug 28 13:07:28 2017 From: tobi at oetiker.ch (Tobias Oetiker) Date: Mon, 28 Aug 2017 15:07:28 +0200 (CEST) Subject: [OmniOS-discuss] ANNOUNCEMENT - OmniOS r151022o - Security Update! Message-ID: <901322396.188169.1503925648239.JavaMail.zimbra@oetiker.ch> OmniOS Community Edition is releasing OmniOS r151022o with a bunch of security fixes: libxml2 fixes for: * CVE-2016-4658 * CVE-2016-5131 * CVE-2017-0663 * CVE-2017-5969 * CVE-2017-9047 * CVE-2017-9048 * CVE-2017-9049 * CVE-2017-9050 bzip2 fix for (we have announced this one separately already): * CVE-2016-3189 This release also contains an update for java to to OpenJDK 1.7.0_141-b02 This release does NOT require a reboot. Full release notes can be found at https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch tobi at oetiker.ch +41 62 775 9902 From rjahnel at ellipseinc.com Mon Aug 28 15:08:44 2017 From: rjahnel at ellipseinc.com (Richard Jahnel) Date: Mon, 28 Aug 2017 15:08:44 +0000 Subject: [OmniOS-discuss] Fixing a BSD boot mirror Message-ID: <65DC5816D4BEE043885A89FD54E273FC78138642@MAIL101.Ellipseinc.com> So a few days after I upgraded one of my machines to R151022 and switched to the BSD loader, I lost one of the drives in the boot mirror. So the question of the day is: What is the command sequence for replacing a drive in a BSD loader rpool mirror? I know the sequence for GRUB, but I don't yet know it for BSD. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdg117 at elvis.arl.psu.edu Mon Aug 28 19:03:39 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Mon, 28 Aug 2017 15:03:39 -0400 Subject: [OmniOS-discuss] Fixing a BSD boot mirror In-Reply-To: Your message of "Mon, 28 Aug 2017 15:08:44 -0000." <65DC5816D4BEE043885A89FD54E273FC78138642@MAIL101.Ellipseinc.com> References: <65DC5816D4BEE043885A89FD54E273FC78138642@MAIL101.Ellipseinc.com> Message-ID: <201708281903.v7SJ3dDe011004@elvis.arl.psu.edu> In message <65DC5816D4BEE043885A89FD54E273FC78138642 at MAIL101.Ellipseinc.com>, R ichard Jahnel writes: >So the question of the day is: What is the command sequence for replacing a dr >ive in a BSD loader rpool mirror? # prtvtoc /dev/rdsk/c0t0d1s2 | fmthard -s - /dev/rdsk/c0t1d1s2 # zpool attach rpool c0t0d1s0 c0t1d1s0 # installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/c0t1d1s0 John groenveld at acm.org From softwareinforjam at gmail.com Mon Aug 28 20:42:59 2017 From: softwareinforjam at gmail.com (Software Information) Date: Mon, 28 Aug 2017 15:42:59 -0500 Subject: [OmniOS-discuss] Move Versions Message-ID: Hi All Still learning OmniOS. Need a little help please. I have the version below. OmniOS 5.11 omnios-r151020-4151d05 March 2017 I am noticing that Community Edition version r151022o has been released but when I run pkg update, it says No updates available for this image. What do I need to do to get the latest version? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdg117 at elvis.arl.psu.edu Mon Aug 28 21:01:32 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Mon, 28 Aug 2017 17:01:32 -0400 Subject: [OmniOS-discuss] Move Versions In-Reply-To: Your message of "Mon, 28 Aug 2017 15:42:59 CDT." References: Message-ID: <201708282101.v7SL1WPv011530@elvis.arl.psu.edu> In message >Still learning OmniOS. Need a little help please. I have the version below. >OmniOS 5.11 omnios-r151020-4151d05 March 2017 > >I am noticing that Community Edition version r151022o has been released but >when I run pkg update, it says No updates available for this image. What do >I need to do to get the latest version? Migrate to OpenSSH: Then pkg update to OmniOSce: John groenveld at acm.org From jim.oltman at gmail.com Tue Aug 29 03:36:11 2017 From: jim.oltman at gmail.com (Jim Oltman) Date: Mon, 28 Aug 2017 21:36:11 -0600 Subject: [OmniOS-discuss] Upgrade from 151022 to CE bootadm error In-Reply-To: References: Message-ID: On Aug 27, 2017 9:34 AM, "Jim Klimov" wrote: On August 27, 2017 3:43:53 PM GMT+02:00, Bob Friesenhahn < bfriesen at simple.dallas.tx.us> wrote: >On Sat, 26 Aug 2017, Jim Oltman wrote: > >> I rebooted then on bootup received an error about /usr mount fatally >> failed. I was able to boot to the previous BE. I tried the update >again >> and received the same bootadm error as above. I'm not sure where to >go >> from here. Hope someone can help. Thanks! > >Make sure that you did not split /usr into its own filesystem outside >of the root filesystem. OmniOS is not prepared for that. I made this >mistake before. > >Bob Or if you did - make sure the new system is prepared to handle this. My system layout managed by scripts below went through several OmniOS upgrades (finally to Bloody CE) just fine. It ain't every year that something has to be re-patched with them. https://github.com/jimklimov/illumos-splitroot-scripts -- Typos courtesy of K-9 Mail on my Android No spilt in the filesystem. Tank is a separate mount: Last login: Sat Aug 26 14:59:17 2017 from 10.0.0.200 OmniOS 5.11 omnios-r151022-f9693432c2 May 2017 joltman at OmniOS-NAS:/export/home/joltman$ sudo df -h Password: Filesystem Size Used Avail Use% Mounted on rpool/ROOT/20170826_Pre_OmniOS-CE 2.7G 2.6G 88M 97% / swap 4.7G 332K 4.7G 1% /etc/svc/volatile swap 4.7G 0 4.7G 0% /tmp swap 4.7G 76K 4.7G 1% /var/run rpool/export 88M 23K 88M 1% /export rpool/export/home 115M 27M 88M 24% /export/home rpool 88M 31K 88M 1% /rpool tank 1.1T 36K 1.1T 1% /tank This is a default install I did a few months back. I didn't do any funky partitioning. I'm not sure why I see 3 swaps. Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From danmcd at kebe.com Tue Aug 29 04:00:39 2017 From: danmcd at kebe.com (Dan McDonald) Date: Tue, 29 Aug 2017 00:00:39 -0400 Subject: [OmniOS-discuss] Upgrade from 151022 to CE bootadm error In-Reply-To: References: Message-ID: <982706AB-D6E6-4D9F-951B-CF47B755FACC@kebe.com> Three swaps are three mountpoints using tmpfs. Please share "zfs list" and "beadm list" again, please? Dan Sent from my iPhone (typos, autocorrect, and all) > On Aug 28, 2017, at 11:36 PM, Jim Oltman wrote: > > > > On Aug 27, 2017 9:34 AM, "Jim Klimov" wrote: > On August 27, 2017 3:43:53 PM GMT+02:00, Bob Friesenhahn wrote: > >On Sat, 26 Aug 2017, Jim Oltman wrote: > > > >> I rebooted then on bootup received an error about /usr mount fatally > >> failed. I was able to boot to the previous BE. I tried the update > >again > >> and received the same bootadm error as above. I'm not sure where to > >go > >> from here. Hope someone can help. Thanks! > > > >Make sure that you did not split /usr into its own filesystem outside > >of the root filesystem. OmniOS is not prepared for that. I made this > >mistake before. > > > >Bob > > Or if you did - make sure the new system is prepared to handle this. > > My system layout managed by scripts below went through several OmniOS upgrades (finally to Bloody CE) just fine. It ain't every year that something has to be re-patched with them. > > https://github.com/jimklimov/illumos-splitroot-scripts > > -- > Typos courtesy of K-9 Mail on my Android > > > No spilt in the filesystem. Tank is a separate mount: > > Last login: Sat Aug 26 14:59:17 2017 from 10.0.0.200 > OmniOS 5.11 omnios-r151022-f9693432c2 May 2017 > joltman at OmniOS-NAS:/export/home/joltman$ sudo df -h > Password: > Filesystem Size Used Avail Use% Mounted on > rpool/ROOT/20170826_Pre_OmniOS-CE 2.7G 2.6G 88M 97% / > swap 4.7G 332K 4.7G 1% /etc/svc/volatile > swap 4.7G 0 4.7G 0% /tmp > swap 4.7G 76K 4.7G 1% /var/run > rpool/export 88M 23K 88M 1% /export > rpool/export/home 115M 27M 88M 24% /export/home > rpool 88M 31K 88M 1% /rpool > tank 1.1T 36K 1.1T 1% /tank > > This is a default install I did a few months back. I didn't do any funky partitioning. I'm not sure why I see 3 swaps. > > Jim > _______________________________________________ > 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 jdg117 at elvis.arl.psu.edu Tue Aug 29 15:34:43 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Tue, 29 Aug 2017 11:34:43 -0400 Subject: [OmniOS-discuss] sendmail+SASL In-Reply-To: Your message of "Sun, 27 Aug 2017 14:35:04 EDT." <201708271835.v7RIZ4mN004252@elvis.arl.psu.edu> References: <201708271835.v7RIZ4mN004252@elvis.arl.psu.edu> Message-ID: <201708291534.v7TFYhgO015455@elvis.arl.psu.edu> In message <201708271835.v7RIZ4mN004252 at elvis.arl.psu.edu>, John D Groenveld wr ites: >What build.sh invocation or minimum environment is required just >to rebuild a couple packages once I git omnios-build? > $ cd /code/john-omnios-151023/illumos-omnios/usr/src/cmd/sendmail $ ksh /code/john-omnios-151023/illumos-omnios/bldenv.sh \ /code/john-omnios-151023/illumos-omnios/illumos.sh make John groenveld at acm.org From peter.tribble at gmail.com Tue Aug 29 16:15:29 2017 From: peter.tribble at gmail.com (Peter Tribble) Date: Tue, 29 Aug 2017 17:15:29 +0100 Subject: [OmniOS-discuss] Errors running pkgrecv against r151014 repo Message-ID: If I try to create or update a mirror of the r151014 repo, I get the following error: $ pkgrecv -s http://pkg.omniti.com/omnios/r151014/ -d /omnios/test14 '*' Processing packages for publisher omnios ... Retrieving and evaluating 11456 package(s)... Download Manifests ( 6886/11456) /pkgrecv: http protocol error: code: 404 reason: Not Found URL: ' http://pkg.omniti.com/omnios/r151014/omnios/manifest/0/runtime%2Fpython-27 at 2.7%2C5.11-0.151014%3A20170425T210810Z' (happened 4 times) Looking at the web version of the repo, there's only one version of that package, with a different timestamp. Looking at the downloaded catalog, it has 2 versions listed. [ { "actions": [ "set name=pkg.summary value=\"Placeholder for Python 2.7 upgrade\"", "set name=pkg.description value=\"Placeholder for Python 2.7 upgrade\"", "set name=description value=\"Placeholder for Python 2.7 upgrade\"" ], "version": "2.7,5.11-0.151014:20170425T210810Z" }, { "actions": [ "set name=pkg.summary value=\"Placeholder for Python 2.7 upgrade\"", "set name=pkg.description value=\"Placeholder for Python 2.7 upgrade\"", "set name=description value=\"Placeholder for Python 2.7 upgrade\"" ], "version": "2.7,5.11-0.151014:20170425T211535Z" } ] This isn't necessarily a problem, because I currently do have a working older mirror (which does have just the one correct version of the package). It would be a problem if I lost my current mirror, as I wouldn't be able to recreate it, so it would be handy if someone at OmniTI could fix this. Thanks, -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bfriesen at simple.dallas.tx.us Tue Aug 29 17:42:53 2017 From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn) Date: Tue, 29 Aug 2017 12:42:53 -0500 (CDT) Subject: [OmniOS-discuss] sendmail+SASL In-Reply-To: <201708291534.v7TFYhgO015455@elvis.arl.psu.edu> References: <201708271835.v7RIZ4mN004252@elvis.arl.psu.edu> <201708291534.v7TFYhgO015455@elvis.arl.psu.edu> Message-ID: On Tue, 29 Aug 2017, John D Groenveld wrote: > In message <201708271835.v7RIZ4mN004252 at elvis.arl.psu.edu>, John D Groenveld wr > ites: >> What build.sh invocation or minimum environment is required just >> to rebuild a couple packages once I git omnios-build? >> > > > > $ cd /code/john-omnios-151023/illumos-omnios/usr/src/cmd/sendmail > $ ksh /code/john-omnios-151023/illumos-omnios/bldenv.sh \ > /code/john-omnios-151023/illumos-omnios/illumos.sh make Please let us know what you learn about running sendmail+libsasl on OmniOS. I am very interested in accomplishing this as well. In particular, I would like to add user-based authentication to user-posted emails and enable use of TLS for inbound and outbound emails. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From lists at marzocchi.net Tue Aug 29 19:47:49 2017 From: lists at marzocchi.net (Olaf Marzocchi) Date: Tue, 29 Aug 2017 21:47:49 +0200 Subject: [OmniOS-discuss] "pkg set-publisher" looking for certificates in /etc/openssl/certs Message-ID: Hello, I tried to upgrade my r151020 (already with OpenSSH) to the latest Community Edition. I downloaded the certificates and checked them successfully, but changing the publisher (after replacing the https with http) fails: $ pkg publisher PUBLISHER TYPE STATUS P LOCATION omnios origin online F http://pkg.omniti.com/omnios/r151020/ uulm.mawi origin online F http://scott.mathematik.uni-ulm.de/release/ niksula.hut.fi origin online F http://pkg.niksula.hut.fi/ $ pfexec /usr/bin/pkg set-publisher -P \ -G http://pkg.omniti.com/omnios/r151020/ \ -g https://pkg.omniosce.org/r151022/core/ omnios pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a valid pkg repository. Please verify the repository's location and the client's network configuration. Additional details: Unable to contact valid package repository: https://pkg.omniosce.org/r151022/core Encountered the following error(s): Transport errors encountered when trying to contact repository. Reported the following errors: Unable to locate a CA directory: /etc/openssl/certs Secure connection is not available. $ ls -l /etc/ssl/pkg/ total 24 lrwxrwxrwx 1 root root 13 Jan 27 2014 78e80b96.0 -> OmniTI_CA.pem lrwxrwxrwx 1 root root 14 Apr 18 04:00 82b377f0.0 -> OmniTI_CA2.pem -r--r--r-- 1 root bin 1326 Jan 27 2014 OmniTI_CA.pem -r--r--r-- 1 root bin 2269 Apr 18 04:00 OmniTI_CA2.pem -r--r--r-- 1 root bin 2244 Apr 18 04:00 OmniTI_CA2_OmniOS.pem lrwxrwxrwx 1 root root 21 Apr 18 04:00 a7c78dde.0 -> OmniTI_CA2_OmniOS.pem -rw-rw-r-- 1 root root 2175 Jul 10 13:32 omniosce-ca.cert.pem I can ping "omniosce.org", and the server has normal Internet access. I checked online but I haven't found any solution. Could you please give me some hints? Thanks Olaf Marzocchi From omnios at citrus-it.net Tue Aug 29 20:01:46 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Tue, 29 Aug 2017 20:01:46 +0000 (UTC) Subject: [OmniOS-discuss] "pkg set-publisher" looking for certificates in /etc/openssl/certs In-Reply-To: References: Message-ID: On Tue, 29 Aug 2017, Olaf Marzocchi wrote: ; Unable to contact valid package repository: ; https://pkg.omniosce.org/r151022/core ; Encountered the following error(s): ; Transport errors encountered when trying to contact repository. ; Reported the following errors: ; Unable to locate a CA directory: /etc/openssl/certs ; Secure connection is not available. ; ... ; Could you please give me some hints? Yes, try: # pkg set-property ca-path /etc/ssl/certs then set the publishers again. You're the second person to have reported this problem and I don't know why your package root would have the wrong CA path on it. If you need any more help with this, please log onto our gitter Lobby at https://gitter.im/omniosorg/Lobby Regards, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123 From jdg117 at elvis.arl.psu.edu Wed Aug 30 01:30:41 2017 From: jdg117 at elvis.arl.psu.edu (John D Groenveld) Date: Tue, 29 Aug 2017 21:30:41 -0400 Subject: [OmniOS-discuss] sendmail+SASL In-Reply-To: Your message of "Tue, 29 Aug 2017 12:42:53 CDT." References: <201708271835.v7RIZ4mN004252@elvis.arl.psu.edu> <201708291534.v7TFYhgO015455@elvis.arl.psu.edu> Message-ID: <201708300130.v7U1Uf7N018625@elvis.arl.psu.edu> In message , Bob Friesenhahn writes: >Please let us know what you learn about running sendmail+libsasl on >OmniOS. I am very interested in accomplishing this as well. In I hoped sendmail was simply corrupting the username and password on its way to libsasl, but that's not case. illumos libsasl doesn't support shadow(4) and the login.so and plain.so auxprop plugins don't seem to actually do anything with checkpass, though maybe I'm missing another callback. It looks like the sendmail + Cyrus SASL replacement is the only route: John groenveld at acm.org From chip at innovates.com Wed Aug 30 19:54:36 2017 From: chip at innovates.com (Schweiss, Chip) Date: Wed, 30 Aug 2017 14:54:36 -0500 Subject: [OmniOS-discuss] SAS 9305-16e HBA support in Illumos Message-ID: I made the assumption that a Broadcom/LSI HBA would be supported already in OmniOS CE r151022o. This HBA is not loading. Here's the 'lspci -vv' output: 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS3216 PCI-Express Fusion-MPT SAS-3 (rev 01) Subsystem: LSI Logic / Symbios Logic Device 3180 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- From chip at innovates.com Thu Aug 31 12:30:11 2017 From: chip at innovates.com (Schweiss, Chip) Date: Thu, 31 Aug 2017 07:30:11 -0500 Subject: [OmniOS-discuss] [zfs] SAS 9305-16e HBA support in Illumos In-Reply-To: <78B3A268-125F-41ED-9898-E1DC42D195F2@joyent.com> References: <4FB32C07-51A0-43C1-9E69-69C1876B13EA@elemental.org> <19DC39EC-F31F-4C5E-867A-A164E044565B@elemental.org> <78B3A268-125F-41ED-9898-E1DC42D195F2@joyent.com> Message-ID: On Wed, Aug 30, 2017 at 3:12 PM, Dan McDonald wrote: > > On Aug 30, 2017, at 4:11 PM, Dale Ghent wrote: > > > > Or rather: > > > > # update_drv -a -i '"pciex1000,c9"' mpt_sas > > It MIGHT fail because mpt_sas checks PCI IDs explicitly itself. :( > > Yes, the update_drv command just hangs indefinately. -Chip > FYI, > Dan > > > ------------------------------------------ > illumos-zfs > Archives: https://illumos.topicbox.com/groups/zfs/discussions/ > T372d7ddd75316296-M31c90a92ac6d9d9dbd977114 > Powered by Topicbox: https://topicbox.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chip at innovates.com Thu Aug 31 13:29:04 2017 From: chip at innovates.com (Schweiss, Chip) Date: Thu, 31 Aug 2017 08:29:04 -0500 Subject: [OmniOS-discuss] [zfs] SAS 9305-16e HBA support in Illumos In-Reply-To: References: <4FB32C07-51A0-43C1-9E69-69C1876B13EA@elemental.org> <19DC39EC-F31F-4C5E-867A-A164E044565B@elemental.org> <78B3A268-125F-41ED-9898-E1DC42D195F2@joyent.com> Message-ID: I've added mpt_sas "pciex1000,c9" to /etc/driver_aliases and rebooted. Looks like it's partially working, but it's not fully functional. Service are timing out: # svcs STATE STIME FMRI legacy_run 8:25:48 lrc:/etc/rc2_d/S20sysetup disabled 8:15:40 svc:/platform/i86pc/acpihpd:default online 8:15:39 svc:/system/svc/restarter:default .... offline 8:15:40 svc:/milestone/multi-user-server:default offline 8:15:40 svc:/system/boot-config:default offline 8:15:40 svc:/system/zones:default offline 8:15:40 svc:/system/intrd:default offline 8:15:40 svc:/system/fm/smtp-notify:default offline* 8:15:49 svc:/system/fmd:default offline* 8:25:48 svc:/milestone/multi-user:default maintenance 8:19:49 svc:/system/hal:default maintenance 8:25:48 svc:/network/iscsi/initiator:default Here's what I see in /var/adm/messages: Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:48 vsphere-zfs01 mpt0: Initiator WWNs: 0x500062b202aea2c0-0x500062b202aea2cf Aug 31 08:15:48 vsphere-zfs01 pcieb: [ID 586369 kern.info] PCIE-device: pci1000,3180 at 0, mpt_sas0 Aug 31 08:15:48 vsphere-zfs01 npe: [ID 236367 kern.info] PCI Express-device: pci1000,3180 at 0, mpt_sas0 Aug 31 08:15:48 vsphere-zfs01 genunix: [ID 936769 kern.info] mpt_sas0 is /pci at 0,0/pci8086,1905 at 1,1/pci1000,3180 at 0 Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 583861 kern.info] mpt_sas1 at mpt_sas0: scsi-iport f00 Aug 31 08:15:48 vsphere-zfs01 genunix: [ID 936769 kern.info] mpt_sas1 is /pci at 0,0/pci8086,1905 at 1,1/pci1000,3180 at 0/iport at f00 Aug 31 08:15:48 vsphere-zfs01 genunix: [ID 408114 kern.info] /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0/iport at f00 (mpt_sas1) online Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c40e3ca FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5001d9faeba FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c3c23a6 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5004308e14e FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c40df6e FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4b3b76 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d362a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c3c243a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d877a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c40dfba FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4b2ede FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4b41fa FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5004bc7c1fa FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c358c22 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c183872 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c183a06 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c181a7a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c1813ee FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c18122e FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c182fda FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c181e2e FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c18472a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c1814de FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5003c35f62a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5004c2a3826 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d3836 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d364a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d6382 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d6356 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d69ba FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d6512 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d7192 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d36ee FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d64f2 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4b3c16 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c50070a5c08a FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d3662 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d60d6 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d35a2 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4d1fbe FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4d27c6 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d66a2 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c500056fb256 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c40e3be FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4d1846 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c6d5ff6 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4d1e52 FastPath Capable and Enabled Aug 31 08:15:48 vsphere-zfs01 scsi: [ID 243001 kern.info] w5000c5002c4d2276 FastPath Capable and Enabled Aug 31 08:15:49 vsphere-zfs01 scsi: [ID 107833 kern.warning] WARNING: /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:49 vsphere-zfs01 MPT Firmware Fault, code: 2667 Aug 31 08:15:49 vsphere-zfs01 scsi: [ID 107833 kern.warning] WARNING: /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:49 vsphere-zfs01 ioc reset abort passthru Aug 31 08:15:49 vsphere-zfs01 mpt_sas: [ID 201859 kern.warning] WARNING: smp_start do passthru error 11 Aug 31 08:15:51 vsphere-zfs01 scsi: [ID 365881 kern.info] /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:51 vsphere-zfs01 MPT Firmware version v9.0.100.0 (?) Aug 31 08:15:51 vsphere-zfs01 scsi: [ID 365881 kern.info] /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:51 vsphere-zfs01 mpt_sas0 MPI Version 0x206 Aug 31 08:15:51 vsphere-zfs01 scsi: [ID 365881 kern.info] /pci at 0 ,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): Aug 31 08:15:51 vsphere-zfs01 mpt0: IOC Operational. Where do I go from here? -Chip On Thu, Aug 31, 2017 at 7:30 AM, Schweiss, Chip wrote: > On Wed, Aug 30, 2017 at 3:12 PM, Dan McDonald wrote: > >> > On Aug 30, 2017, at 4:11 PM, Dale Ghent wrote: >> > >> > Or rather: >> > >> > # update_drv -a -i '"pciex1000,c9"' mpt_sas >> >> It MIGHT fail because mpt_sas checks PCI IDs explicitly itself. :( >> >> > Yes, the update_drv command just hangs indefinately. > > -Chip > > > >> FYI, >> Dan >> >> >> ------------------------------------------ >> illumos-zfs >> Archives: https://illumos.topicbox.com/groups/zfs/discussions/T372d7dd >> d75316296-M31c90a92ac6d9d9dbd977114 >> Powered by Topicbox: https://topicbox.com >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chip at innovates.com Thu Aug 31 14:53:44 2017 From: chip at innovates.com (Schweiss, Chip) Date: Thu, 31 Aug 2017 09:53:44 -0500 Subject: [OmniOS-discuss] [zfs] SAS 9305-16e HBA support in Illumos In-Reply-To: <328231EA-C034-4337-BB37-F3FF2AA1C2D7@elemental.org> References: <4FB32C07-51A0-43C1-9E69-69C1876B13EA@elemental.org> <19DC39EC-F31F-4C5E-867A-A164E044565B@elemental.org> <78B3A268-125F-41ED-9898-E1DC42D195F2@joyent.com> <328231EA-C034-4337-BB37-F3FF2AA1C2D7@elemental.org> Message-ID: This server will be serving NFS for vSphere. It is running OmniOS CE, nothing VMware. I'm working on flashing firmware now and will report back any changes. -Chip On Thu, Aug 31, 2017 at 9:42 AM, Dale Ghent wrote: > > > On Aug 31, 2017, at 9:29 AM, Schweiss, Chip wrote: > > > > I've added mpt_sas "pciex1000,c9" to /etc/driver_aliases and rebooted. > > > > Looks like it's partially working, but it's not fully functional. > Service are timing out: > > > > Here's what I see in /var/adm/messages: > > > > > > Aug 31 08:15:49 vsphere-zfs01 scsi: [ID 107833 kern.warning] WARNING: > /pci at 0,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): > > Aug 31 08:15:49 vsphere-zfs01 MPT Firmware Fault, code: 2667 > > Aug 31 08:15:49 vsphere-zfs01 scsi: [ID 107833 kern.warning] WARNING: > /pci at 0,0/pci8086,1905 at 1,1/pci1000,3180 at 0 (mpt_sas0): > > The driver is reporting that the MPT IOC (IO Controller) is reporting a > fault. It's just reading this condition off the controller chip itself, and > unfortunately there doesn't seem to be a handy reference published by > LSI/Avago regarding what 2667h actually means. > > However I note from your machine's hostname that this is perhaps a ESI > guest that is being given the HBA in passthrough mode? It would seem that > someone else has encountered a similar issue as yourself in this case, with > the same MPT fault code, but on Linux running Proxmox. According to this > forum thread, they ended up flashing the firmware on the card to something > newer and the problem went away: > > https://forum.proxmox.com/threads/pci-passthrough.16483/ > > I would suggest Tim's approach and flashing your card up to the newest IT > (not IR) firmware. > > /dale > > > ------------------------------------------ > illumos-zfs > Archives: https://illumos.topicbox.com/groups/zfs/discussions/ > T372d7ddd75316296-Mb0dd6c92e5393440a8b0c8fb > Powered by Topicbox: https://topicbox.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lkateley at kateley.com Thu Aug 31 18:43:46 2017 From: lkateley at kateley.com (Linda Kateley) Date: Thu, 31 Aug 2017 14:43:46 -0400 Subject: [OmniOS-discuss] ip not persistent? Message-ID: All, Has anyone ever run into a case where ipadm details are persistent across reboot? I am seeing this intermittently in zones. linda From danmcd at kebe.com Thu Aug 31 18:58:26 2017 From: danmcd at kebe.com (Dan McDonald) Date: Thu, 31 Aug 2017 14:58:26 -0400 Subject: [OmniOS-discuss] ip not persistent? In-Reply-To: References: Message-ID: <20170831185826.GA26484@everywhere.local> On Thu, Aug 31, 2017 at 02:43:46PM -0400, Linda Kateley wrote: > All, > > Has anyone ever run into a case where ipadm details are persistent across > reboot? I am seeing this intermittently in zones. ipadm(1M) is SUPPOSED TO be persisten across reboots. Unless you specify with -t. Or are you seeing things that are NOT persistent that should be? Dan From lkateley at kateley.com Thu Aug 31 19:05:16 2017 From: lkateley at kateley.com (Linda Kateley) Date: Thu, 31 Aug 2017 15:05:16 -0400 Subject: [OmniOS-discuss] ip not persistent? In-Reply-To: <20170831185826.GA26484@everywhere.local> References: <20170831185826.GA26484@everywhere.local> Message-ID: <9c80a7f3-3c0a-6575-2175-702b0d6028b8@kateley.com> I am doing it with -T? linda On 8/31/17 2:58 PM, Dan McDonald wrote: > On Thu, Aug 31, 2017 at 02:43:46PM -0400, Linda Kateley wrote: >> All, >> >> Has anyone ever run into a case where ipadm details are persistent across >> reboot? I am seeing this intermittently in zones. > ipadm(1M) is SUPPOSED TO be persisten across reboots. Unless you specify > with -t. > > Or are you seeing things that are NOT persistent that should be? > > Dan From lkateley at kateley.com Thu Aug 31 19:07:20 2017 From: lkateley at kateley.com (Linda Kateley) Date: Thu, 31 Aug 2017 15:07:20 -0400 Subject: [OmniOS-discuss] ip not persistent? In-Reply-To: <20170831185826.GA26484@everywhere.local> References: <20170831185826.GA26484@everywhere.local> Message-ID: <9b1e88e6-d989-7262-85e5-85cac2e712d6@kateley.com> So also no services come up because the zones boot without IP. lk On 8/31/17 2:58 PM, Dan McDonald wrote: > On Thu, Aug 31, 2017 at 02:43:46PM -0400, Linda Kateley wrote: >> All, >> >> Has anyone ever run into a case where ipadm details are persistent across >> reboot? I am seeing this intermittently in zones. > ipadm(1M) is SUPPOSED TO be persisten across reboots. Unless you specify > with -t. > > Or are you seeing things that are NOT persistent that should be? > > Dan From danmcd at kebe.com Thu Aug 31 19:51:07 2017 From: danmcd at kebe.com (Dan McDonald) Date: Thu, 31 Aug 2017 15:51:07 -0400 Subject: [OmniOS-discuss] ip not persistent? In-Reply-To: <9c80a7f3-3c0a-6575-2175-702b0d6028b8@kateley.com> References: <20170831185826.GA26484@everywhere.local> <9c80a7f3-3c0a-6575-2175-702b0d6028b8@kateley.com> Message-ID: <20170831195107.GB27090@everywhere.local> On Thu, Aug 31, 2017 at 03:05:16PM -0400, Linda Kateley wrote: > I am doing it with -T? -T is "type" for the create-addr command: ipadm create-addr -T dhcp zonevnic0/v4 The above example should persist across boots. -t is "Temporary" ipadm create-addr -t -T dhcp zonevnic0/v4 The above example will not persist across boots. Dan From lkateley at kateley.com Thu Aug 31 22:33:38 2017 From: lkateley at kateley.com (Linda Kateley) Date: Thu, 31 Aug 2017 18:33:38 -0400 Subject: [OmniOS-discuss] ip not persistent? In-Reply-To: <20170831195107.GB27090@everywhere.local> References: <20170831185826.GA26484@everywhere.local> <9c80a7f3-3c0a-6575-2175-702b0d6028b8@kateley.com> <20170831195107.GB27090@everywhere.local> Message-ID: Ended up being the weirdest thing, someone put a hosts.allow file in the zone that didn't contain the IP, so it didn't know what to do.. Took it off, works perfectly On 8/31/17 3:51 PM, Dan McDonald wrote: > On Thu, Aug 31, 2017 at 03:05:16PM -0400, Linda Kateley wrote: >> I am doing it with -T? > -T is "type" for the create-addr command: > > ipadm create-addr -T dhcp zonevnic0/v4 > > The above example should persist across boots. > > -t is "Temporary" > > ipadm create-addr -t -T dhcp zonevnic0/v4 > > The above example will not persist across boots. > > Dan