date:20170403

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

2017-04-03 Thread Bob Friesenhahn

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 is already booted
pfexec zoneadm -z swdev boot  0.00s user 0.00s system 0% cpu 0.015 
total

Shutdown
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 6.145 
total

Boot
pfexec zoneadm -z swdev boot  0.01s user 0.00s system 0% cpu 1.271 
total

Shutdown
zone 'swdev': unable to shutdown zone
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 
1:40.08 total

Boot
zone 'swdev': zone is already booted
pfexec zoneadm -z swdev boot  0.01s user 0.00s system 47% cpu 0.021 
total

Shutdown
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 6.135 
total

Boot
pfexec zoneadm -z swdev boot  0.01s user 0.00s system 0% cpu 1.230 
total

Shutdown
zone 'swdev': unable to shutdown zone
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 
1:40.07 total

Boot
zone 'swdev': zone is already booted
pfexec zoneadm -z swdev boot  0.01s user 0.00s system 41% cpu 0.024 
total

Shutdown
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 6.156 
total

Boot
pfexec zoneadm -z swdev boot  0.00s user 0.00s system 0% cpu 1.154 
total

Shutdown
^C
pfexec zoneadm -z swdev shutdown  0.00s user 0.00s system 0% cpu 
33.103 total


--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

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 $pid1 $pid2 > /dev/null 2>&1
+# XXX KEBE SAYS TRY SOMETHING DIFFERENT...
+   /usr/bin/pwait $pid1 $pid2
+#  /usr/bin/kill $pid1 $pid2 > /dev/null 2>&1
 fi
 
 /sbin/init ${initstate}


I believe the shutdown script is forking procs that don't finish until AFTER 
zoneadmd starts to shut things down.  This causes the problems you see.

The global version of shutdown should not be modified for now (esp. if this 
doesn't work for you, you can use it to recover).

Thanks,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Richard Jahnel

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 (http://pkg.omniti.net/omnios/release/) will 
continue to serve packages for r151006 and r151008
The repo for r151010 is http://pkg.omniti.net/omnios/r151010/. See the 
upgrade instructions on how to move between repos if upgrading from a previous 
OmniOS release.

So I thinking that the answer should be http://pkg.omniti.net/omnios/release/

-Original Message-
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On Behalf 
Of Frank Boeye
Sent: Monday, April 3, 2017 3:19 PM
To: Dan McDonald 
Cc: omnios-discuss@lists.omniti.com
Subject: 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: maandag 3 april 2017 22:16
To: Frank Boeye ; Dan McDonald 
Cc: omnios-discuss@lists.omniti.com
Subject: 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

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Frank Boeye

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: maandag 3 april 2017 22:16
To: Frank Boeye ; Dan McDonald 
Cc: omnios-discuss@lists.omniti.com
Subject: 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

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

> 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

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Frank Boeye

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 
Signing Certificate/emailAddress=omnios-supp...@omniti.com could not be found. 
The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate 
Authority
The package involved 
is:pkg://omnios/locale/gu@0.5.11,5.11-0.151014:20170301T162851Z


Do I need to specify an old repository or publisher first again then?

Thanks!

-Frank

-Original Message-
From: Dan McDonald [mailto:dan...@omniti.com] 
Sent: maandag 3 april 2017 20:37
To: Frank Boeye ; Dan McDonald 
Cc: omnios-discuss@lists.omniti.com
Subject: 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:20130507T1
> 91120Z set name=pkg.summary value="Perl 5.16.1 Programming Language 
> Docs"
> set name=pkg.descr value="Perl 5.16.1 Programming Language Docs"
> set name=publisher value=s...@omniti.com file 
> 80eb1eb144aa8dc55993e8e368ca8189e7911bb4 
> chash=cce029c54848ec6178ebd419fd738dd15b671f60 group=bin mode=0755 
> owner=root path=usr/perl5/5.16.1/bin/pod2html pkg.csize=927 
> pkg.size=2064 file 6360c1a609c5a72aa3380f5d2a9f1a576fb2e640 
> chash=be1ecb4772c547a9f7739a28303230c8aac6200b group=bin mode=0755 
> owner=root path=usr/perl5/5.16.1/bin/pod2latex pkg.csize=3804 
> pkg.size=10378 file 5d088db441e21d8faa653427ce905e7125da852e 
> chash=0ff7255b30bd6a2e216c4b20aa6de36780863cf4 group=bin mode=0755 
> owner=root path=usr/perl5/5.16.1/bin/pod2man pkg.csize=4791 
> pkg.size=11615 file a7dd55d275470b2fca194799c30cd04cb0d53d14 
> chash=9d97ff341806398db56fd3b3ba5025c48cefcb08 group=bin mode=0755 
> owner=root path=usr/perl5/5.16.1/bin/pod2text pkg.csize=3778 
> pkg.size=9158  Bunch more files  file 
> 704d896209dafbb4bd55a3e054273b9ee3c2968c 
> chash=e7cc73a54f163ad5aacf8265641bb0e9610c80d0 group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/utf8.3 pkg.csize=4590 
> pkg.size=12203 file 658bdc92fe9df6d61b2d645be5c4e8b5f1faa68a 
> chash=17d77b6c181ba716d8d78b862aa049d5e624e7c1 group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/vars.3 pkg.csize=2370 
> pkg.size=5193 file 7946cf41e4289d078292daaa3a5b97e29dbd8a20 
> chash=0b7d398714a70ce146727254ea2542d041b5650d group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/version.3 pkg.csize=5668 
> pkg.size=15576 file 77cb31e7b3765e1ec0886fd8a11b5af97dda9a56 
> chash=38552cdd0c7e8f4ce5d1f18a40312dcfda92337c group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/version::Internals.3 
> pkg.csize=11021 pkg.size=31868 file 
> 24f98111b69a8b09970c6d50765c8e0c02c93368 
> chash=f69e790ebd4c26817756a41cc45c4671145f3445 group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/vmsish.3 pkg.csize=3298 
> pkg.size=7992 file b5351f32a043da6782154f3fb3b8906db003895e 
> chash=57e11931fe6ce73af627a4652d3cbb714e7a5434 group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/warnings.3 pkg.csize=2759 
> pkg.size=8740 file 9b9ec1c4b3b6918b873126b2a1ce76164b199bfa 
> chash=7155a3420e0f13f2609a5a740581627c94a77af8 group=bin mode=0644 
> owner=root path=usr/perl5/5.16.1/man/man3/warnings::register.3 
> pkg.csize=1855 pkg.size=4138 license 
> 8db6c3c8a577b36129555ff15dabf691b4a73c55 
> chash=8f1b2dd37aec20d7b4aaf4ae32bc7b8501678f79 license=Artistic 
> pkg.csize=2416 pkg.size=6321 depend 
> fmri=runtime/perl@5.16.1,5.11-0.151006 type=incorporate depend 
> fmri=runtime/perl@5.16.1,5.11-0.151006 type=require

Wow!  I don't know how runtime/perl/manual ended up with an INCORPORATE 
dependency, but that's what happened.

I have one other suggestion:

- Please just do a vanilla "pkg update" of your 006 first.  It may create a new 
BE, BUT it will update all of the packages.  The revision on your 
runtime/perl/manual is VERY VERY OLD, and has this INCORPORATE dependency which 
is fixed by later revisions within 006.

I should've said this earlier: You can't update to a whole new revision until 
your OLD revision is at its latest possible update.

Please try that and report back.

Thank you,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald


> 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 zoneadmd[3639]: [ID 702911 daemon.error] [zone 'lipkg0'] 
failed to open console master: Device busy
Apr  3 15:22:16 bloody zoneadmd[3639]: [ID 702911 daemon.error] [zone 'lipkg0'] 
WARNING: could not open master side of zone console for lipkg0 to release slave 
handle: Device busy
Apr  3 15:22:16 bloody zoneadmd[3639]: [ID 702911 daemon.error] [zone 'lipkg0'] 
WARNING: console /devices//pseudo/zconsnex@1/zcons@2 found, but it could not be 
removed.: I/O error


And you may be right about it being a race of some sort.  But between what 
entities I cannot tell as of yet.  As of this second, I cannot get this error 
to manifest.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

> 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 the zone, and uttered "zoneadm -z lipkg0 shutdown".  THIS TIME IT 
> WORKED!

But trying it again failed.

Okay, I see what happened.

1st shutdown failed.  I tried a 2nd shutdown, which also failed, BUT managed to 
unwedge zsched, likely by calling zone_destroy() and having the right thing 
happen.

Sorry for rubberducking on the public mailing list.  :)

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

> 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.  When 
I came back, the zsched process was gone, and the zone appeared to be properly 
shut down.

So I booted the zone, and uttered "zoneadm -z lipkg0 shutdown".  THIS TIME IT 
WORKED!

I noticed *this* in my /var/adm/messages:

Apr  3 15:15:46 bloody genunix: [ID 408114 kern.info] 
/pseudo/zconsnex@1/zcons@2 (zcons2) online

This makes me wonder if something happens wrong the first time a zcons is 
created.  I'll try this again on another box I can reboot fully if need be.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] network configuration script

2017-04-03 Thread Michael Rasmussen

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 GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Real Users never use the Help key.


pgpFp9tnOII5p.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald


> 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 easily:

bloody(~)[0]% sudo zoneadm -z lipkg0 shutdown

zone 'lipkg0': unable to shutdown zone
bloody(~)[1]% zoneadm list -cv
  ID NAME STATUS PATH   BRANDIP
   0 global   running/  ipkg shared
   1 lx1  running/zones/lx1 lx   excl  
   2 lx0  running/zones/lx0 lx   excl  
   3 lx2  running/zones/lx2 lx   excl  
   4 lipkg0   shutting_down /zones/lipkg0  lipkg
excl  
bloody(~)[0]% pgrep -z lipkg0
764
bloody(~)[0]% 

Process 764 is a zsched process.  It's here:

> 0xff007d61fc40::findstack -v
stack pointer for thread ff007d61fc40: ff007d61f950
[ ff007d61f950 _resume_from_idle+0x112() ]
  ff007d61f980 swtch+0x141()
  ff007d61f9c0 cv_wait+0x70(ff1955618148, fbcf8610)
  ff007d61fa50 zone_status_wait_cpr+0xb5(ff1955618000, 8, 
  fbb82a3d)
  ff007d61fb30 zsched+0x5f0(ff007dfbacf0)
  ff007d61fb40 thread_start+8()

Which is in this function:

3007  /*
3008   * Private CPR-safe version of zone_status_wait().
3009   */
3010  static void
3011  zone_status_wait_cpr(zone_t *zone, zone_status_t status, char *str)
3012  {
3013callb_cpr_t cprinfo;
3014  
3015ASSERT(status > ZONE_MIN_STATE && status <= ZONE_MAX_STATE);
3016  
3017CALLB_CPR_INIT(, _status_lock, callb_generic_cpr,
3018str);
3019mutex_enter(_status_lock);
3020while (zone->zone_status < status) {
3021CALLB_CPR_SAFE_BEGIN();
3022cv_wait(>zone_cv, _status_lock);
3023CALLB_CPR_SAFE_END(, _status_lock);
3024}
3025/*
3026 * zone_status_lock is implicitly released by the following.
3027 */
3028CALLB_CPR_EXIT();
3029  }


Okay.  I will be diving into this now to see WTF happened.  I'm sorry for not 
paying closer attention to this sooner.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

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 Docs"
> set name=pkg.descr value="Perl 5.16.1 Programming Language Docs"
> set name=publisher value=s...@omniti.com
> file 80eb1eb144aa8dc55993e8e368ca8189e7911bb4 
> chash=cce029c54848ec6178ebd419fd738dd15b671f60 group=bin mode=0755 owner=root 
> path=usr/perl5/5.16.1/bin/pod2html pkg.csize=927 pkg.size=2064
> file 6360c1a609c5a72aa3380f5d2a9f1a576fb2e640 
> chash=be1ecb4772c547a9f7739a28303230c8aac6200b group=bin mode=0755 owner=root 
> path=usr/perl5/5.16.1/bin/pod2latex pkg.csize=3804 pkg.size=10378
> file 5d088db441e21d8faa653427ce905e7125da852e 
> chash=0ff7255b30bd6a2e216c4b20aa6de36780863cf4 group=bin mode=0755 owner=root 
> path=usr/perl5/5.16.1/bin/pod2man pkg.csize=4791 pkg.size=11615
> file a7dd55d275470b2fca194799c30cd04cb0d53d14 
> chash=9d97ff341806398db56fd3b3ba5025c48cefcb08 group=bin mode=0755 owner=root 
> path=usr/perl5/5.16.1/bin/pod2text pkg.csize=3778 pkg.size=9158
> 
> Bunch more files
> 
> file 704d896209dafbb4bd55a3e054273b9ee3c2968c 
> chash=e7cc73a54f163ad5aacf8265641bb0e9610c80d0 group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/utf8.3 pkg.csize=4590 pkg.size=12203
> file 658bdc92fe9df6d61b2d645be5c4e8b5f1faa68a 
> chash=17d77b6c181ba716d8d78b862aa049d5e624e7c1 group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/vars.3 pkg.csize=2370 pkg.size=5193
> file 7946cf41e4289d078292daaa3a5b97e29dbd8a20 
> chash=0b7d398714a70ce146727254ea2542d041b5650d group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/version.3 pkg.csize=5668 pkg.size=15576
> file 77cb31e7b3765e1ec0886fd8a11b5af97dda9a56 
> chash=38552cdd0c7e8f4ce5d1f18a40312dcfda92337c group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/version::Internals.3 pkg.csize=11021 
> pkg.size=31868
> file 24f98111b69a8b09970c6d50765c8e0c02c93368 
> chash=f69e790ebd4c26817756a41cc45c4671145f3445 group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/vmsish.3 pkg.csize=3298 pkg.size=7992
> file b5351f32a043da6782154f3fb3b8906db003895e 
> chash=57e11931fe6ce73af627a4652d3cbb714e7a5434 group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/warnings.3 pkg.csize=2759 pkg.size=8740
> file 9b9ec1c4b3b6918b873126b2a1ce76164b199bfa 
> chash=7155a3420e0f13f2609a5a740581627c94a77af8 group=bin mode=0644 owner=root 
> path=usr/perl5/5.16.1/man/man3/warnings::register.3 pkg.csize=1855 
> pkg.size=4138
> license 8db6c3c8a577b36129555ff15dabf691b4a73c55 
> chash=8f1b2dd37aec20d7b4aaf4ae32bc7b8501678f79 license=Artistic 
> pkg.csize=2416 pkg.size=6321
> depend fmri=runtime/perl@5.16.1,5.11-0.151006 type=incorporate
> depend fmri=runtime/perl@5.16.1,5.11-0.151006 type=require

Wow!  I don't know how runtime/perl/manual ended up with an INCORPORATE 
dependency, but that's what happened.

I have one other suggestion:

- Please just do a vanilla "pkg update" of your 006 first.  It may create a new 
BE, BUT it will update all of the packages.  The revision on your 
runtime/perl/manual is VERY VERY OLD, and has this INCORPORATE dependency which 
is fixed by later revisions within 006.

I should've said this earlier: You can't update to a whole new revision until 
your OLD revision is at its latest possible update.

Please try that and report back.

Thank you,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Bob Friesenhahn


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 probably missed out on those mails, but who else has seen this issue 
(precisely zones taking forever to shutdown)?  I know about the message, but I 
don't see zones being jammed up on shutdown.


Here is a link to the previous discussion thread:

http://lists.omniti.com/pipermail/omnios-discuss/2015-December/thread.html#6073

I wonder if it's "init 6" specifically?  I use reboot(1M) command, 
so it does not go through the inittab(4) sequence.  Now I'm more 
fascinated to know what process(es) are hanging, because I suspect 
they arrive via "init 6".


The problem is definintely with zone 'shutdown'.  I have never seen it 
happen with 'reboot' or 'halt'.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

> 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 it in my 020 zones 
(and I've several of them).

> 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 probably missed out on those mails, but who else has seen this issue 
(precisely zones taking forever to shutdown)?  I know about the message, but I 
don't see zones being jammed up on shutdown.

I wonder if it's "init 6" specifically?  I use reboot(1M) command, so it does 
not go through the inittab(4) sequence.  Now I'm more fascinated to know what 
process(es) are hanging, because I suspect they arrive via "init 6".

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] network configuration script

2017-04-03 Thread Dan McDonald


> 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 the correct repo.  
Otherwise, I'll need a URL from which I can "git clone".

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Frank Boeye

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 a rather basic system install, then just deployed napp-it over it. I'm 
not really a solaris dude, so thanks for bearing with me :D

Further output:

root@ant-san:~# pkg update -v --be-name=omnios-r151014 entire@11,5.11-0.151014
Creating Plan |
pkg update: No matching version of entire can be installed:
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150402T192159Z
  Reason:  All versions matching 'require' dependency 
pkg:/editor/vim@7.3,5.11-0.151014 are rejected
Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151014:20150402T174104Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150727T183612Z
  Reason:  All versions matching 'require' dependency 
pkg:/SUNWcs@0.5.11,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150402T175117Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150417T182313Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150727T054625Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150818T161010Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150913T201525Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150914T194934Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150929T225303Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20151112T210017Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20151215T144929Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160204T172603Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160420T161518Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160603T031037Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151006:20130507T191035Z
  Reason:  Excluded by proposed incorporation 
'incorporation/jeos/omnios-userland'
   This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20161027T152352Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20161230T212400Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20170301T162827Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150914T123242Z
   pkg://omnios/entire@11,5.11-0.151014:20151112T205709Z
   pkg://omnios/entire@11,5.11-0.151014:20151202T161039Z
   pkg://omnios/entire@11,5.11-0.151014:20160104T154618Z
   pkg://omnios/entire@11,5.11-0.151014:20160602T180308Z
   pkg://omnios/entire@11,5.11-0.151014:20160607T003721Z
  Reason:  All versions matching 'require' dependency 
pkg:/editor/vim@7.3,5.11-0.151014 are rejected
Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151014:20150402T174104Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20160804T055959Z
  Reason:  All versions matching 'require' dependency 
pkg:/SUNWcs@0.5.11,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150402T175117Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected

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

2017-04-03 Thread Bob Friesenhahn


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 open console master: Device busy
Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] 
WARNING: could not open master side of zone console for swdev to release slave 
handle: Device busy
Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] 
WARNING: console /devices//pseudo/zconsnex@1/zcons@0 found, but it could not be 
removed.: I/O error
Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
unable to unmount '/zones/swdev/root/proc'
Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
unable to unmount file systems in zone
Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
unable to destroy zone
Apr  2 17:51:53 velma svc.startd[10]: [ID 122153 daemon.warning] 
svc:/system/zones:default: Method or service exit timed out.  Killing contract 
169.
Apr  2 17:51:53 velma svc.startd[10]: [ID 636263 daemon.warning] 
svc:/system/zones:default: Method "/lib/svc/method/svc-zones stop" failed due 
to signal KILL.


You did say you were using that zone as an NFS client.  Perhaps one of the 
processes wasn't really done accessing a remote filesystem?  I noticed the 
unmountable filesystem is procfs for that zone.  I can't tell you why that's 
interesting off the top of my head, that IS interesting to know, however.


The zone uses the automounter and NFS mounts would not have been made 
due to the zone simply having been booted for a minute or two.


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.


The zone configuration seems quite simple.  Is there something about 
it which might cause an issue?


The common theme is always the first message "failed to open console 
master: Device busy".  The failure to unmount filesystems is new to 
me.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald

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

The output you have indicates perl & vim, being blocked by:

pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z

Actually, also please include the output of:

pkg contents -m runtime/perl/manual

Thanks,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] network configuration script

2017-04-03 Thread Michael Rasmussen

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:
> 
>   
> https://github.com/omniti-labs/illumos-omnios/tree/master/usr/src/prototypes/
> 
I have no particular reservation against a license I was just asking
not to unintentionally exclude myself.

> One thing about this, and I need to try it of course, is whether or not this 
> could be modified to scribble commands into /mnt/.initialboot as a bonus 
> feature of the new Kayak interactive install?  Say under a "post-install 
> extras" sub-menu or something.
> 
I forgot to mention that it is my intention to make every parameter
available through command line as well. Eg. if all necessary parameter
is available from command line then use them and only return status
code like 0 or 1.

> Pardon the latency.  Today is off for a number of reasons, and I won't be 
> fully recombobulated until Tuesday.
> 
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?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Quantum Mechanics is God's version of "Trust me."


pgpbeirG_Xh2p.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Dan McDonald


> 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 system (version is 
> omnios-r151020-4151d05).
> 
> In this case it was after doing 'init 6' to reboot the system and the problem 
> added about 180 seconds to the shutdown time.  In three reboots, the problem 
> happened twice.

If you have a shell available, you should inspect the available processes to 
see what all is stuck in where.

pgrep -z 

is helpful, as well as:

pstack 
pwdx 

pwdx(1) shows the PWD for a process.  If the process is stuck with 
PWD== that  can't be umounted until the process exits or 
changes PWD.  If that pstack(1) command shows NOTHING, it means it's stuck 
doing something in the kernel.  In that case, "mdb -k" may show you the 
processes from the kernel's pov:

::ps -t

and then you can find the stuck process, and check out its threads in "mdb -k" 
by:

::findstack -v

> This is logged:
> 
> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] 
> failed to open console master: Device busy
> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] 
> WARNING: could not open master side of zone console for swdev to release 
> slave handle: Device busy
> Apr  2 17:50:13 velma zoneadmd[653]: [ID 702911 daemon.error] [zone 'swdev'] 
> WARNING: console /devices//pseudo/zconsnex@1/zcons@0 found, but it could not 
> be removed.: I/O error
> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
> unable to unmount '/zones/swdev/root/proc'
> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
> unable to unmount file systems in zone
> Apr  2 17:51:29 velma zoneadmd[1842]: [ID 702911 daemon.error] [zone 'swdev'] 
> unable to destroy zone
> Apr  2 17:51:53 velma svc.startd[10]: [ID 122153 daemon.warning] 
> svc:/system/zones:default: Method or service exit timed out.  Killing 
> contract 169.
> Apr  2 17:51:53 velma svc.startd[10]: [ID 636263 daemon.warning] 
> svc:/system/zones:default: Method "/lib/svc/method/svc-zones stop" failed due 
> to signal KILL.

You did say you were using that zone as an NFS client.  Perhaps one of the 
processes wasn't really done accessing a remote filesystem?  I noticed the 
unmountable filesystem is procfs for that zone.  I can't tell you why that's 
interesting off the top of my head, that IS interesting to know, however.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] network configuration script

2017-04-03 Thread Dan McDonald

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 whether or not this 
could be modified to scribble commands into /mnt/.initialboot as a bonus 
feature of the new Kayak interactive install?  Say under a "post-install 
extras" sub-menu or something.

Pardon the latency.  Today is off for a number of reasons, and I won't be fully 
recombobulated until Tuesday.

Thanks,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Frank Boeye

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 
pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh --reject 
pkg:/service/network/ssh-common pkg:/network/openssh pkg:/network/openssh-server
Creating Plan
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

root@ant-san:~# /usr/bin/pkg unset-publisher omnios
root@ant-san:~# /usr/bin/pkg set-publisher -P --set-property 
signature-policy=require-signatures -g http://pkg.omniti.com/omnios/r151014/ 
omnios
root@ant-san:~# /usr/bin/pkg update --be-name=omnios-r151014 
entire@11,5.11-0.151014
Creating Plan |
pkg update: No matching version of entire can be installed:
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150402T192159Z
  Reason:  All versions matching 'require' dependency 
pkg:/editor/vim@7.3,5.11-0.151014 are rejected
Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151014:20150402T174104Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150727T183612Z
  Reason:  All versions matching 'require' dependency 
pkg:/SUNWcs@0.5.11,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150402T175117Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150417T182313Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150727T054625Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150818T161010Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150913T201525Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150914T194934Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20150929T225303Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20151112T210017Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20151215T144929Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160204T172603Z
 pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160420T161518Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20160603T031037Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151006:20130507T191035Z
  Reason:  Excluded by proposed incorporation 
'incorporation/jeos/omnios-userland'
   This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20161027T152352Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20161230T212400Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
Reject:  pkg://omnios/SUNWcs@0.5.11,5.11-0.151014:20170301T162827Z
Reason:  All versions matching 'require' dependency pkg:/runtime/perl are 
rejected
  Reject:  pkg://omnios/entire@11,5.11-0.151014:20150914T123242Z
   pkg://omnios/entire@11,5.11-0.151014:20151112T205709Z
   pkg://omnios/entire@11,5.11-0.151014:20151202T161039Z
   pkg://omnios/entire@11,5.11-0.151014:20160104T154618Z
   pkg://omnios/entire@11,5.11-0.151014:20160602T180308Z
   pkg://omnios/entire@11,5.11-0.151014:20160607T003721Z
  Reason:  All versions matching 'require' dependency 
pkg:/editor/vim@7.3,5.11-0.151014 are rejected
Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151014:20150402T174104Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151014 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20150402T192953Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151014:20160301T161253Z
  Reason:  This version is excluded by installed incorporation

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

2017-04-03 Thread Dale Ghent


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 pkg:/network/openssh-server

I'd also like to note that 016 might not be the best choice as its it a version 
of Stable which is no longer supported. Currently, the supported versions of 
OmniOS are the current LTS (151014) and the previous and current Stable 
releases (151018 and 151020 respectively). 151016 will not see any security 
updates. If you are looking for something newer than LTS, the current Stable is 
always the best choice regarding updates.

/dale


> On Apr 3, 2017, at 6:48 AM, Frank Boeye  wrote:
> 
> 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:
>   Reject:  pkg://omnios/entire@11,5.11-0.151016:20151102T202622Z
>   Reason:  All versions matching 'require' dependency 
> pkg:/library/glib2@2.34.1,5.11-0.151016 are rejected
> Reject:  pkg://omnios/library/glib2@2.34.1,5.11-0.151016:20151102T204001Z
> Reason:  All versions matching 'require' dependency 
> pkg:/runtime/perl@5.16.1,5.11-0.151016 are rejected
>   Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151102T203644Z
>pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151104T132510Z
>pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20160301T161406Z
>   Reason:  This version is excluded by installed incorporation 
> pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
>   Reject:  pkg://omnios/entire@11,5.11-0.151016:20151112T204605Z
>pkg://omnios/entire@11,5.11-0.151016:20151202T161203Z
>   Reason:  All versions matching 'require' dependency 
> pkg:/editor/vim@7.3,5.11-0.151016 are rejected
> Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151016:20151102T185436Z
> Reason:  All versions matching 'require' dependency 
> pkg:/runtime/perl@5.16.1,5.11-0.151016 are rejected
>   Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151102T203644Z
>pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151104T132510Z
>pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20160301T161406Z
>   Reason:  This version is excluded by installed incorporation 
> pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
> 
> It seems that this problem has occurred earlier to some people, but I cannot 
> seem to find a posted solution anywhere.
> 
> Anyone have any clue?
> 
> This is a very standard install including Napp-It on a proliant microserver.
> 
> Thanks!
> 
> Regards,
> 
> -Frank
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss



signature.asc
Description: Message signed with OpenPGP
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Tobias Oetiker

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
> 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 people that have been creating them keep them in different places, and 
> some
> of them are public, some are not.
> 
> It would be nice to have a "script-market", placed somewhere where OmniOS
> users/developers could easily reach them, and with some description about 
> their
> use, perhaps categorized. I don't know the right place for something like 
> that,
> perhaps git? With links from the OmniOS website.
> 
> What do you people think about that?
> 
> Regards Johan
> 
> 
> 
> 
> -"OmniOS-discuss"  skrev: -
> Till: "omnios-discuss@lists.omniti.com" 
> Från: Michael Rasmussen
> Sänt av: "OmniOS-discuss"
> Datum: 2017-04-02 23:33
> Ärende: [OmniOS-discuss] network configuration script
> 
> Hi all,
> 
> I think it is not very easy for new users coming to Omnios from various
> other distros to make the initial network configuration so I have
> written a small tool in Python to remedy this obstacle. The script runs
> on all Omnios as of r151014. I have tested on r151014 and bloody
> (r151021)
> 
> The script is not ment to be the swiss army knife for configuring
> networks on Omnios so there is no support for vnic, vlan, and
> aggregates. It will only support configuring a single nic given the
> user the option for dhcp and static setup. The user is also asked
> whether to configure dns in which case the user is asked for an IP.
> 
> Currently it will only handle ethernet but IPoIB is on my todo list. I
> have attached the script here but if the file is to large it can also
> be downloaded here: http://git.datanom.net/netconf.git/
> 
> PS. If I want to have it included in Omnios what license should I use?
> 
> --
> Hilsen/Regards
> Michael Rasmussen
> 
> Get my public GnuPG keys:
> michael  rasmussen  cc
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
> mir  datanom  net
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
> mir  miras  org
> http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
> --
> /usr/games/fortune -es says:
> It's illegal in Wilbur, Washington, to ride an ugly horse.
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> 
> [bilagan "netconf" borttagen av Johan Kragsterman/Capvert]
> [bilagan "att0uq4e.dat" borttagen av Johan Kragsterman/Capvert]
> 
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch t...@oetiker.ch +41 62 775 9902
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

2017-04-03 Thread Frank Boeye

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:
  Reject:  pkg://omnios/entire@11,5.11-0.151016:20151102T202622Z
  Reason:  All versions matching 'require' dependency 
pkg:/library/glib2@2.34.1,5.11-0.151016 are rejected
Reject:  pkg://omnios/library/glib2@2.34.1,5.11-0.151016:20151102T204001Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151016 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151102T203644Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151104T132510Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20160301T161406Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
  Reject:  pkg://omnios/entire@11,5.11-0.151016:20151112T204605Z
   pkg://omnios/entire@11,5.11-0.151016:20151202T161203Z
  Reason:  All versions matching 'require' dependency 
pkg:/editor/vim@7.3,5.11-0.151016 are rejected
Reject:  pkg://omnios/editor/vim@7.4.45,5.11-0.151016:20151102T185436Z
Reason:  All versions matching 'require' dependency 
pkg:/runtime/perl@5.16.1,5.11-0.151016 are rejected
  Reject:  pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151102T203644Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20151104T132510Z
   pkg://omnios/runtime/perl@5.16.1,5.11-0.151016:20160301T161406Z
  Reason:  This version is excluded by installed incorporation 
pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z

It seems that this problem has occurred earlier to some people, but I cannot 
seem to find a posted solution anywhere.

Anyone have any clue?

This is a very standard install including Napp-It on a proliant microserver.

Thanks!

Regards,

-Frank
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] Ang: network configuration script

2017-04-03 Thread Johan Kragsterman


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 people that have been creating them keep them in different places, and some 
of them are public, some are not.

It would be nice to have a "script-market", placed somewhere where OmniOS 
users/developers could easily reach them, and with some description about their 
use, perhaps categorized. I don't know the right place for something like that, 
perhaps git? With links from the OmniOS website.

What do you people think about that?

Regards Johan




-"OmniOS-discuss"  skrev: -
Till: "omnios-discuss@lists.omniti.com" 
Från: Michael Rasmussen 
Sänt av: "OmniOS-discuss" 
Datum: 2017-04-02 23:33
Ärende: [OmniOS-discuss] network configuration script

Hi all,

I think it is not very easy for new users coming to Omnios from various
other distros to make the initial network configuration so I have
written a small tool in Python to remedy this obstacle. The script runs
on all Omnios as of r151014. I have tested on r151014 and bloody
(r151021)

The script is not ment to be the swiss army knife for configuring
networks on Omnios so there is no support for vnic, vlan, and
aggregates. It will only support configuring a single nic given the
user the option for dhcp and static setup. The user is also asked
whether to configure dns in which case the user is asked for an IP.

Currently it will only handle ethernet but IPoIB is on my todo list. I
have attached the script here but if the file is to large it can also
be downloaded here: http://git.datanom.net/netconf.git/

PS. If I want to have it included in Omnios what license should I use?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
It's illegal in Wilbur, Washington, to ride an ugly horse.
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


[bilagan "netconf" borttagen av Johan Kragsterman/Capvert]
[bilagan "att0uq4e.dat" borttagen av Johan Kragsterman/Capvert]


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

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

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

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

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

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

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

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

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

Re: [OmniOS-discuss] network configuration script

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

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

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

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

Re: [OmniOS-discuss] network configuration script

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

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

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

Re: [OmniOS-discuss] network configuration script

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

Re: [OmniOS-discuss] network configuration script

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

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

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

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

[OmniOS-discuss] Ang: network configuration script

26 matches

Site Navigation

Mail list logo

Footer information