[OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Hi guys, Following the upgrade instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151014 I am running into the following issue: /usr/bin/pkg update --be-name=omnios-r151016 entire@11,5.11-0.151016 Creating Plan - pkg update: No matching version of entire can be installed:

Re: [OmniOS-discuss] Got a larval fix for you, Bob!

Unfortunately, while the console message goes away, there is still a problem. Notice the failures to shutdown the zone: % while true while> do while> echo Boot ; time pfexec zoneadm -z swdev boot while> echo Shutdown ; time pfexec zoneadm -z swdev shutdown while> done Boot zone 'swdev': zone

Re: [OmniOS-discuss] network configuration script

On Mon, 3 Apr 2017 13:53:18 -0400 Dan McDonald wrote: > > Git is fine assuming the URL you mentioned earlier is the correct repo. > Otherwise, I'll need a URL from which I can "git clone". > The URL is correct and works. -- Hilsen/Regards Michael Rasmussen Get my public

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 3, 2017, at 3:18 PM, Dan McDonald wrote: > > AND THINGS GET WEIRDER. > > After the failure I documented earlier, I went off to do something else. > When I came back, the zsched process was gone, and the zone appeared to be > properly shut down. > > So I booted

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

From: http://omnios.omniti.com/wiki.php/ReleaseNotes?rev=a0d510f34690cfe285ec3a775d1f10d3464b684e OmniOS has moved to a per-release package repository setup. Each major release going forward will have its own IPS repository. The previous repo for releases

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Hi Frank, some of the package names changed after 151014. Can you try this instead: /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

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Hi Dale, Thanks for the info. I'm planning on going to 151020, but need an intermediate step from 151006. 151014 is fine as well. I've did the rejections below, then tried the update again, and got this: /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject

Re: [OmniOS-discuss] Ang: network configuration script

maybe a page on the omnios wiki with pointers would be all that is needed cheers tobi - On Apr 3, 2017, at 8:46 AM, Johan Kragsterman johan.kragster...@capvert.se wrote: > Hi Michael and all! > > > I think this is a good idea, thanks, Michael, but that is not the most > important >

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 2, 2017, at 7:07 PM, Bob Friesenhahn > wrote: > > Previously I reported a problem (in the 040 timeframe) in that zones are > hanging when being shut down. Problems continue on that system. Today I am > seeing the same issue with a different OmniOS

Re: [OmniOS-discuss] network configuration script

I'll need to take a look at this in depth. Our preferred license is CDDL. Take a look at the prototypes directory for sample headers for each: https://github.com/omniti-labs/illumos-omnios/tree/master/usr/src/prototypes/ One thing about this, and I need to try it of course, is

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Dumb question: Do you have any non-OmniOS publishers like ms.omniti.com on this installation? If so, let's see if one of those is incorporate-blocking you. If not, you could try, thought this will produce more output: pkg update -v --be-name=omnios-r151014 entire@11,5.11-0.151014

Re: [OmniOS-discuss] network configuration script

On Mon, 3 Apr 2017 11:41:15 -0400 Dan McDonald wrote: > I'll need to take a look at this in depth. > Sure ;-) > Our preferred license is CDDL. Take a look at the prototypes directory for > sample headers for each: > > >

Re: [OmniOS-discuss] network configuration script

> On Apr 3, 2017, at 12:01 PM, Michael Rasmussen wrote: > > I will make a new version later today which supports command line. Do > you need the file attached here or can you live with that you have to > fetch it from git? Git is fine assuming the URL you mentioned earlier is

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 3, 2017, at 1:40 PM, Bob Friesenhahn > wrote: > > The common theme is always the first message "failed to open console master: > Device busy". The failure to unmount filesystems is new to me. That could be something from the LX code, but I'm not seeing

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

I see the problem... > On Apr 3, 2017, at 1:47 PM, Frank Boeye wrote: > > pkg contents -m runtime/perl/manual > > set name=pkg.fmri > value=pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z > set name=pkg.summary value="Perl 5.16.1 Programming Language

Re: [OmniOS-discuss] Continuing hung-zone problems

On Mon, 3 Apr 2017, Dan McDonald wrote: If you have a shell available, you should inspect the available processes to see what all is stuck in where. I will try to find some time for such activities. Apr 2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] failed to

[OmniOS-discuss] Ang: network configuration script

Hi Michael and all! I think this is a good idea, thanks, Michael, but that is not the most important reason I respond this mail: I have been thinking for a while about all the nice scripts for different solutions people have been presenting here, both bash, py, perl, DTrace, etc. The

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

No other publisher: root@ant-san:~# pkg publisher PUBLISHER TYPE STATUS URI omniosorigin online http://pkg.omniti.com/omnios/r151014/ root@ant-san:~# I's not a dumb question, I had to google around a bit for that :) I've did

Re: [OmniOS-discuss] Continuing hung-zone problems

On Mon, 3 Apr 2017, Dan McDonald wrote: All of my zones (some of which do not use NFS and have almost every network service disabled) on my two OmniOS systems are equally plagued with this issue. I know that I am not alone since others have reported that this is happening to them. I've

[OmniOS-discuss] Got a larval fix for you, Bob!

I would like you to go into your zones, and patch THEIR version of /usr/sbin/shutdown thusly: --- /usr/sbin/shutdown Fri Apr 22 16:36:43 2016 +++ /zones/lipkg0/root/usr/sbin/shutdownMon Apr 3 17:54:24 2017 @@ -228,7 +228,9 @@ if [ "$pid1" ] || [ "$pid2" ] then - /usr/bin/kill

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 3, 2017, at 2:11 PM, Bob Friesenhahn > wrote: > > The problem is definintely with zone 'shutdown'. I have never seen it happen > with 'reboot' or 'halt'. Which does go through the inittab things. I've found something. I can reproduce this on bloody

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 3, 2017, at 3:38 PM, Bob Friesenhahn > wrote: > > It does not seem that you obtained the same initial error message ("failed to > open console master: Device busy") that I always do. When it fails, I *DO* see this. Apr 3 15:22:16 bloody

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Hi, I've had a feeling that i'd probably have to do a regular update first. I've tried this before but ran into the following: root@ant-san:~# pkg update Creating Plan - pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151014 Release

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

> On Apr 3, 2017, at 4:11 PM, Frank Boeye wrote: > > Do I need to specify an old repository or publisher first again then? Yes. Sorry for not being clear about that. You need to go back to the 006 publisher and get it all-the-way updated. Dan

Re: [OmniOS-discuss] OmniOs update from 151006 to 151016 issue

Thought so. Can you help me in the right direction on what the correct publisher is for 006? http://pkg.omniti.com/omnios/r151006/ obviously is incorrect, and I can't seem to find it online. Thanks! -Frank -Original Message- From: Dan McDonald [mailto:dan...@omniti.com] Sent:

Re: [OmniOS-discuss] Continuing hung-zone problems

> On Apr 3, 2017, at 2:59 PM, Dan McDonald wrote: > > Okay. I will be diving into this now to see WTF happened. I'm sorry for not > paying closer attention to this sooner. AND THINGS GET WEIRDER. After the failure I documented earlier, I went off to do something else.