heh heh. Gold. A great one that I'll now hopefully not get caught by! ;)
Nathan. Dimopoulos, Chris wrote: > Nathan. > the error was basically caused by confusion (mixing up the two commands > ) on my part. poolbind V's pbind > ie. > > root at aud5012s [162] > poolbind -p boe0-pool -i zoneid dcmc065z > root at aud5012s [163] > pbind -q `pgrep -z dcmc065z -x init` process id > 27989: not bound > > instead of using > > root at aud5012s [229] > poolbind -q `pgrep -z dcmc065z -x init` > 27989 boe0-pool > > Silly mistake ! > > > Chris Dimopoulos > Unix Technical Services - Enterprise Services > Australia and New Zealand Banking Group Limited > 32/55 Collins St Melbourne, Vic, 3000 > T: +61 3 8685 5435 E: chris.dimopoulos at anz.com > > -----Original Message----- > From: Nathan.Kroenert at Sun.COM [mailto:Nathan.Kroenert at Sun.COM] > Sent: Wednesday, 28 January 2009 11:29 AM > To: Chris Dimo > Cc: ug-msosug at opensolaris.org > Subject: Re: [ug-msosug] Process ID not bound > > Hey, Chris - > > Share the error with us. I think pretty much everyone would learn > something from it... :) > > Nathan. > > On 01/27/09 16:00, Chris Dimo wrote: >> Folks, >> Please ignore. >> ive discovered the issue. ( user error :-) ) >> >> Apologies for using up bandwidth ! >> >> -----Original Message----- >> From: Chris Dimo [mailto:dimo at mail.org] >> Sent: Tuesday, 27 January 2009 3:50 PM >> To: ug-msosug at opensolaris.org >> Subject: RE: Process ID not bound >> >> >> Ok, further to my email.. >> ive trowelled through my logs when I first set up the pool and indeed >> it worked ! >> there has been no sys adm activity on this domain since then, and when > >> I decided to check the other domain ( where no work was done on the >> pools ) Im now getting the same error !! >> >> any ideas thoughts ? >> >> -----Original Message----- >> From: Chris Dimo [mailto:dimo at mail.org] >> Sent: Tuesday, 27 January 2009 2:41 PM >> To: ug-msosug at opensolaris.org >> Subject: Process ID not bound >> >> >> Folks >> >> Folks, >> i have reached an impass and any help/advice would be appreciated. >> Ive got an M5000 Domain running Sol10u5. >> Ive had a Fixed CPU pool running for some time now, and all working as > >> it should. >> On Friday, I created 2 additional fixed cpu pools ( after removing one > >> which i recreated ). The following process was followed to remove the > >> pool and pset I didnt want. >> >> root at aud5012s [177] > pooladm -s >> root at aud5012s [180] > poolcfg -c 'destroy pset boe-pset' >> /etc/pooladm.conf root at aud5012s [181] > pooladm -c >> >> root at aud5012s [173] > pooladm -s >> root at aud5012s [174] > poolcfg -c 'destroy pool boe-pool' >> /etc/pooladm.conf root at aud5012s [175] > pooladm -c >> >> After creating the new pools which seemed to work ok... >> >> root at aud5012s [158] > poolstat >> pset >> id pool size used load >> 0 pool_default 8 0.00 0.49 >> 9 boe1-pool 2 0.00 0.00 >> 8 boe0-pool 2 0.00 0.01 >> 10 wps-pool 4 0.00 0.00 >> >> However, after trying to assign a container to one of the new pools I >> am getting the following : >> >> root at aud5012s [162] > poolbind -p boe0-pool -i zoneid dcmc065z >> root at aud5012s [163] > pbind -q `pgrep -z dcmc065z -x init` process id >> 27989: not bound >> >> Ive also discovered that previously bound containers to cpu pools are >> showing the same message. >> >> Any help would be appreciated. >> >> Cheers >> Chris Dimopoulos. >> >> _______________________________________________ >> ug-msosug mailing list >> ug-msosug at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/ug-msosug > -- ////////////////////////////////////////////////////////////////// // Nathan Kroenert nathan.kroenert at sun.com // // Systems Engineer Phone: +61 3 9869-6255 // // Sun Microsystems Fax: +61 3 9869-6288 // // Level 7, 476 St. Kilda Road Mobile: 0419 305 456 // // Melbourne 3004 Victoria Australia // //////////////////////////////////////////////////////////////////
