[zones-discuss] Error on zoneadm attach -u when going from b132 to b133
I upgraded my system from b132 to b133 this weekend and I got error messages when I ran attach -u to upgrade my zones. The second run of the install of updated packages fails. In the log I find: $ pfexec cat /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:50 CET] Log File: /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:52 CET] Attaching... [Saturday, 20 February 2010 20:57:52 CET] existing [Saturday, 20 February 2010 20:57:52 CET] [Saturday, 20 February 2010 20:57:52 CET] Sanity Check: Passed. Looks like an OpenSolaris system. pkg: 'network/ftp' matches multiple packages network/ftp service/network/ftp 'network/dns/bind' matches multiple packages service/network/dns/bind network/dns/bind 'network/ssh' matches multiple packages network/ssh service/network/ssh If I run attach -u a second time it attaches without doing anything, or giving an error. Are my zones OK or are they partly upgraded ? Paul ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Error on zoneadm attach -u when going from b132 to b133
On Mon, 22 Feb 2010 11:49:46 +0100, Paul van der Zwan paul.vanderz...@sun.com wrote: I upgraded my system from b132 to b133 this weekend and I got error messages when I ran attach -u to upgrade my zones. The second run of the install of updated packages fails. In the log I find: $ pfexec cat /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:50 CET] Log File: /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:52 CET] Attaching... [Saturday, 20 February 2010 20:57:52 CET] existing [Saturday, 20 February 2010 20:57:52 CET] [Saturday, 20 February 2010 20:57:52 CET] Sanity Check: Passed. Looks like an OpenSolaris system. pkg: 'network/ftp' matches multiple packages network/ftp service/network/ftp 'network/dns/bind' matches multiple packages service/network/dns/bind network/dns/bind 'network/ssh' matches multiple packages network/ssh service/network/ssh If I run attach -u a second time it attaches without doing anything, or giving an error. Are my zones OK or are they partly upgraded ? I think exactly this issue is listed in the 133 release notes, and it states running a 2nd attach will work. if our marvellous opensolaris.org system would work you could read the 133 release notes here on the indiana discuss alias: http://opensolaris.org/jive/thread.jspa?threadID=124275 --- frankB ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Error on zoneadm attach -u when going from b132 to b133
On 22 feb 2010, at 12:02, Frank Batschulat (Home) wrote: On Mon, 22 Feb 2010 11:49:46 +0100, Paul van der Zwan paul.vanderz...@sun.com wrote: I upgraded my system from b132 to b133 this weekend and I got error messages when I ran attach -u to upgrade my zones. The second run of the install of updated packages fails. In the log I find: $ pfexec cat /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:50 CET] Log File: /var/tmp/dns.attach_log.sCaydi [Saturday, 20 February 2010 20:57:52 CET] Attaching... [Saturday, 20 February 2010 20:57:52 CET] existing [Saturday, 20 February 2010 20:57:52 CET] [Saturday, 20 February 2010 20:57:52 CET] Sanity Check: Passed. Looks like an OpenSolaris system. pkg: 'network/ftp' matches multiple packages network/ftp service/network/ftp 'network/dns/bind' matches multiple packages service/network/dns/bind network/dns/bind 'network/ssh' matches multiple packages network/ssh service/network/ssh If I run attach -u a second time it attaches without doing anything, or giving an error. Are my zones OK or are they partly upgraded ? I think exactly this issue is listed in the 133 release notes, and it states running a 2nd attach will work. if our marvellous opensolaris.org system would work you could read the 133 release notes here on the indiana discuss alias: http://opensolaris.org/jive/thread.jspa?threadID=124275 That seems to be it. Must have missed it.. Thanks Paul --- frankB ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] [osol-discuss] Error on zoneadm attach -u when going from b132 to b133
On 22 feb 2010, at 12:26, Alan Burlison wrote: Paul van der Zwan wrote: If I run attach -u a second time it attaches without doing anything, or giving an error. Are my zones OK or are they partly upgraded ? Sounds like an issue mentioned in the release notes: http://mail.opensolaris.org/pipermail/opensolaris-announce/2010-February/001411.html http://defect.opensolaris.org/bz/show_bug.cgi?id=14673 That seems to be it. Glad I did what the release notes say I should have done ;-) Thanks Paul -- Alan Burlison -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] [osol-discuss] Error on zoneadm attach -u when going from b132 to b133
you're lucky. It didn't work for me. I got caught in a catch 22 i'd do attach -u and it would fail, then i'd do attach (without -u) and it would tell me to do attach -u On Mon, Feb 22, 2010 at 8:51 AM, Paul van der Zwan paul.vanderz...@sun.comwrote: On 22 feb 2010, at 12:26, Alan Burlison wrote: Paul van der Zwan wrote: If I run attach -u a second time it attaches without doing anything, or giving an error. Are my zones OK or are they partly upgraded ? Sounds like an issue mentioned in the release notes: http://mail.opensolaris.org/pipermail/opensolaris-announce/2010-February/001411.html http://defect.opensolaris.org/bz/show_bug.cgi?id=14673 That seems to be it. Glad I did what the release notes say I should have done ;-) Thanks Paul -- Alan Burlison -- ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] minor code review for 6890415 6880288 (zoneadm.c, native brand)
On 02/22/10 09:40, Frank Batschulat (Home) wrote: May I have 2 code reviewers for the following minor changes for: PSARC/2010/008 Remove zoneadm install sub-option -x nodataset 6880288 retire zoneadm install -x nodataset option 6890415 zoneadm install fails but returns 0 http://cr.opensolaris.org/~batschul/nodataset/ Frank, This looks good to me. Thanks, Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] minor code review for 6890415 6880288 (zoneadm.c, native brand)
On Mon 22 Feb 2010 at 10:52AM, Jerry Jelinek wrote: On 02/22/10 09:40, Frank Batschulat (Home) wrote: May I have 2 code reviewers for the following minor changes for: PSARC/2010/008 Remove zoneadm install sub-option -x nodataset 6880288 retire zoneadm install -x nodataset option 6890415 zoneadm install fails but returns 0 http://cr.opensolaris.org/~batschul/nodataset/ Frank, This looks good to me. To me as well, although I would be tempted to call temp_err something like cleanup_err. -dp -- Daniel Price, Solaris Kernel Engineeringhttp://blogs.sun.com/dp ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] renaming zonepath
On 02/21/10 08:33 AM, Anil wrote: Never mind. I will not do this rename. It's not worth the trouble. r...@vps1:~# zoneadm -z note move /zones/note Moving across file systems; copying zonepath /zones/bugs...sh[1]: cd: /zones/bugs: [No such file or directory] zoneadm: zone 'note': 'copy' failed with exit code 1. The copy failed. More information can be found in /var/log/zoneAAA2XaapU Cleaning up zonepath /zones/note...The ZFS file system for this zone has been destroyed. I believe the zones are not mounted when the zone is not running so the cp fails. Luckily it did not delete the data *phew*. Thanks! Anil, My response is for future reference. The zoneadm move command should preserve the ZFS filesystem's properties because zoneadm(1M) merely changes the filesystem's mountpoint. What you're seeing is odd because zoneadm(1M) should never have to manually copy files across filesystems as long as you're moving a zone with a ZFS-based zonepath. (zoneadm(1M) only copies files across filesystems when it can't set the ZFS filesystem's mountpoint.) What version of Solaris are you using? Thanks, Jordan ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] snv_132: rlogin, rsh, telnet in non-global zones
Just to clarify, this question is specifically about ipkg zones (i.e., on an osol-b132 host). -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
