[zones-discuss] how to unset a publisher in a zone?
hello all, after upgrading from S11X to S11, i'm unable to attach a zone due to a missing publisher. I'm trying to remove the old publisher but i have this: root@electre:~# pkg -R /zones/test_bd/root/ publisher PUBLISHER TYPE STATUS URI solaris (syspub) origin online file:///mnt/repo/ solaris (syspub) origin online proxy:// http://localhost:1/ latp origin online http://electre:1/ root@electre:~# pkg -R /zones/test_bd/root/ unset-publisher solaris pkg unset-publisher: Removal failed for 'solaris': solaris is a system publisher and cannot be unset. there are 2 publishers with the same name, how can i correct this problem? thanks in advance for help, gerard ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] 7116113 bug in zone, what is the workaround?
hello, i got this bug after upgtrading form S11X to S11: SunOS Release 5.11 Version 11.0 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. Feb 20 10:25:54 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method or service exit timed out. Killing contract 772. Feb 20 10:25:54 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method /lib/svc/method/nss-upgrade failed due to signal KILL. Feb 20 10:26:54 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method or service exit timed out. Killing contract 798. Feb 20 10:26:54 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method /lib/svc/method/nss-upgrade failed due to signal KILL. Feb 20 10:27:55 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method or service exit timed out. Killing contract 801. Feb 20 10:27:55 svc.startd[17564]: svc:/system/name-service/upgrade:default: Method /lib/svc/method/nss-upgrade failed due to signal KILL. Feb 20 10:27:55 svc.startd[17564]: system/name-service/upgrade:default failed: transitioned to maintenance (see 'svcs -xv' for details) Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Enter user name for system maintenance (control-d to bypass): the bug ID 7116113 gives the following workaround: Increase the system/name-service/upgrade start method timeout_seconds to a value larger than 60 seconds. Say 300 seconds (5min). i tried: root@www2:~# svccfg -s svc:/system/name-service/upgrade:default start/timeout_seconds = 300 svccfg: Syntax error. as you can see, the syntax is uncorrect. Anybody can help to give the correct syntax? thanks in advance, gerard ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones toast after updating Solaris 11 Express system
the problem is very hard to solve. excuse my bad english, i try to explain: - remember that the initial OS is b151, first S11X release - BE is opensolaris-3 - first, i got the SRU13 iso and set a local repo with it - i have to upgrade pkg, it creates a new BE - opensolaris-4 - then, i upgrade to SRU13, it creates opensolaris-5 the problem is that when i boot the BE opensolaris-4, the zones are broken, so i tried the method detach; attach -u . But the zone remains broken As you can see, from BE opensolaris-3 to BE opensolaris-5, the OS stays at b151, not 175 because i cannot upgrade to S11X due to zones broken. I'd hope to upgrade my machine during the day, but it seems impossible. I open a SR on MOS. thanks for help, 2012/2/11 gerard henry solar...@gmail.com your reply gave me an idea, but now the machine is rebooted with old BE: - when i booted the new BE, and did attach -u, i forgot one essential thing explained in 13352339: ORACLE SOLARIS 11 EXPRESS 2010.11 SRU 13 REPO ISO IMAGE - as i workoed with the lofiadm way, i forgot to re-mount it after reboot, and i guess this is why the attach -u does nothing. As soon as possible, i'll test it thanks for all replies, 2012/2/11 Enda O'Connor enda.ocon...@oracle.com Hi According to this your global zone is at 151 ie express Global zone version: entire@0.5.11,5.11-0.151.0.1:**20101105T054056Z in global zone run pkg info entire if that says 151 then can i see pkg publisher If that points to s11 can I see pkg update -nv '*@latest' Enda On 11/02/2012 14:06, gerard henry wrote: i exactly have the same problem, but detach; attach -u didn't solve it But it seems that the attach -u doesn't upgrade, according to the messages: # zoneadm -z www attach -u Log File: /var/tmp/www.attach_log.LGaqKg Attach Path: /zones/www/root Attach ZFS Dataset: rpool/zones/www/ROOT/zbe-4 Installing: Using pre-existing data in zonepath Global zone version: entire@0.5.11,5.11-0.151.0.1:** 20101105T054056Z Non-Global zone version: entire@0.5.11,5.11-0.151.0.1:** 20101105T054056Z Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows No updates necessary for this image. Updating non-global zone: Zone updated. Result: Attach Succeeded. after the system has booted with: SunOS Release 5.11 Version 151.0.1.12 64-bit I don't understand what you said with pkg -R ... image-update ? thanks in advance for help, 2011/10/5 Ian Collins i...@ianshome.com mailto:i...@ianshome.com On 10/ 5/11 09:26 PM, casper@oracle.com mailto:casper@oracle.com wrote: Before I go through the pain of logging a support call, has anyone seen or fixed the following problem: I ran an update on a fresh Solaris 11 Express system from the support repository and after restarting, all the systems zones are dead. The zone consoles report: SunOS Release 5.11 Version 151.0.1.8 64-bit Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) svc:/system/early-manifest-__**import:default signalled: SYS The zones run an older version of the Solaris software and as a result its libc doesn't match the kernel and the binaries will fail. I think you will need to upgrade all your zones too It might be something simple as zoneadm detach; zoneadm attach -u but make sure that you keep sufficient save sufficient information to reinstall the zones; and make sure you try this on one zone first before you detach all of them. It might be possible to update the zones also using pkg -Rzoneroot image-update after you've mounted the root filesystem. Thanks Casper! I really should tattoo zoneadm detach; zoneadm attach -u inside my eyelids! -- Ian. __**___ zones-discuss mailing list zones-discuss@opensolaris.org mailto:zones-discuss@**opensolaris.orgzones-discuss@opensolaris.org __**_ zones-discuss mailing list zones-discuss@opensolaris.org __**_ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones toast after updating Solaris 11 Express system
i exactly have the same problem, but detach; attach -u didn't solve it But it seems that the attach -u doesn't upgrade, according to the messages: # zoneadm -z www attach -u Log File: /var/tmp/www.attach_log.LGaqKg Attach Path: /zones/www/root Attach ZFS Dataset: rpool/zones/www/ROOT/zbe-4 Installing: Using pre-existing data in zonepath Global zone version: entire@0.5.11,5.11-0.151.0.1:20101105T054056Z Non-Global zone version: entire@0.5.11,5.11-0.151.0.1:20101105T054056Z Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows No updates necessary for this image. Updating non-global zone: Zone updated. Result: Attach Succeeded. after the system has booted with: SunOS Release 5.11 Version 151.0.1.12 64-bit I don't understand what you said with pkg -R ... image-update ? thanks in advance for help, 2011/10/5 Ian Collins i...@ianshome.com On 10/ 5/11 09:26 PM, casper@oracle.com wrote: Before I go through the pain of logging a support call, has anyone seen or fixed the following problem: I ran an update on a fresh Solaris 11 Express system from the support repository and after restarting, all the systems zones are dead. The zone consoles report: SunOS Release 5.11 Version 151.0.1.8 64-bit Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) svc:/system/early-manifest-**import:default signalled: SYS The zones run an older version of the Solaris software and as a result its libc doesn't match the kernel and the binaries will fail. I think you will need to upgrade all your zones too It might be something simple as zoneadm detach; zoneadm attach -u but make sure that you keep sufficient save sufficient information to reinstall the zones; and make sure you try this on one zone first before you detach all of them. It might be possible to update the zones also using pkg -Rzoneroot image-update after you've mounted the root filesystem. Thanks Casper! I really should tattoo zoneadm detach; zoneadm attach -u inside my eyelids! -- Ian. __**_ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] zones toast after updating Solaris 11 Express system
your reply gave me an idea, but now the machine is rebooted with old BE: - when i booted the new BE, and did attach -u, i forgot one essential thing explained in 13352339: ORACLE SOLARIS 11 EXPRESS 2010.11 SRU 13 REPO ISOIMAGE - as i workoed with the lofiadm way, i forgot to re-mount it after reboot, and i guess this is why the attach -u does nothing. As soon as possible, i'll test it thanks for all replies, 2012/2/11 Enda O'Connor enda.ocon...@oracle.com Hi According to this your global zone is at 151 ie express Global zone version: entire@0.5.11,5.11-0.151.0.1:**20101105T054056Z in global zone run pkg info entire if that says 151 then can i see pkg publisher If that points to s11 can I see pkg update -nv '*@latest' Enda On 11/02/2012 14:06, gerard henry wrote: i exactly have the same problem, but detach; attach -u didn't solve it But it seems that the attach -u doesn't upgrade, according to the messages: # zoneadm -z www attach -u Log File: /var/tmp/www.attach_log.LGaqKg Attach Path: /zones/www/root Attach ZFS Dataset: rpool/zones/www/ROOT/zbe-4 Installing: Using pre-existing data in zonepath Global zone version: entire@0.5.11,5.11-0.151.0.1:** 20101105T054056Z Non-Global zone version: entire@0.5.11,5.11-0.151.0.1:** 20101105T054056Z Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows No updates necessary for this image. Updating non-global zone: Zone updated. Result: Attach Succeeded. after the system has booted with: SunOS Release 5.11 Version 151.0.1.12 64-bit I don't understand what you said with pkg -R ... image-update ? thanks in advance for help, 2011/10/5 Ian Collins i...@ianshome.com mailto:i...@ianshome.com On 10/ 5/11 09:26 PM, casper@oracle.com mailto:casper@oracle.com wrote: Before I go through the pain of logging a support call, has anyone seen or fixed the following problem: I ran an update on a fresh Solaris 11 Express system from the support repository and after restarting, all the systems zones are dead. The zone consoles report: SunOS Release 5.11 Version 151.0.1.8 64-bit Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) svc:/system/early-manifest-__**import:default signalled: SYS The zones run an older version of the Solaris software and as a result its libc doesn't match the kernel and the binaries will fail. I think you will need to upgrade all your zones too It might be something simple as zoneadm detach; zoneadm attach -u but make sure that you keep sufficient save sufficient information to reinstall the zones; and make sure you try this on one zone first before you detach all of them. It might be possible to update the zones also using pkg -Rzoneroot image-update after you've mounted the root filesystem. Thanks Casper! I really should tattoo zoneadm detach; zoneadm attach -u inside my eyelids! -- Ian. __**___ zones-discuss mailing list zones-discuss@opensolaris.org mailto:zones-discuss@**opensolaris.orgzones-discuss@opensolaris.org __**_ zones-discuss mailing list zones-discuss@opensolaris.org __**_ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] unable to upgrade from b111 to b134
first, i found the following workaround: http://voyager-eng.livejournal.com/tag/active%20dataset and it works! then, sun support helped me, and it seems that i hit the following bug: Zones Cloned by Using zoneadm clone Can Cause a Snapshot Name Collision When You Activate a Boot Environment (10990) The use of the zoneadm clone command to create zones can cause a snapshot name collision, which can lead to a failure or an infinite loop when you activate a boot environment. Although this bug has been fixed in this release, you may encounter this issue while upgrading from OpenSolaris 2009.06 to the Oracle Solaris 11 Express release. Workaround: Before using image-update to update your system to the Oracle Solaris 11 Express release, run the zoneadm detach command for each zone in the OpenSolaris 2009.06 boot environment. To reattach the zones: 1. Update the image. # pkg image-update 2. Boot into the boot environment that was created by image-update. 3. Run the zoneadm attach -u command for each zone in the new boot environment. i've not tested it yet, but i'm confiant. thanks for all replies, 2010/12/22 John D Groenveld jdg...@elvis.arl.psu.edu In message 4d127340.5050...@ianshome.com, Ian Collins writes: What happens if you detach the zones, upgrade and then reattach with -u? I think he's got two problems: his ZBEs in the detach zones aren't (un)mounted properly and his ZBEs are clones and the snapshots are confusing the hell out of him as much as they confused the hell out of me when I first played with that feature. # zonecfg -z foo # zfs list -r |grep foo # mount |grep foo We'll probably need to see the zfs properties for the ZBEs that refuse to attach -u. John groenv...@acm.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] unable to upgrade from b111 to b134
2010/12/22 gerard henry solar...@gmail.com i tried another approach like this: m...@src:~$ pfexec zfs send -R rpool/zones/w...@move | ssh dst pfexec zfs receive -d rpool cannot receive: local origin for clone rpool/zones/www2/ROOT/zb...@zbe-2does not exist on the source server: m...@src:~$ zfs destroy rpool/zones/www2/ROOT/zb...@zbe-2 cannot destroy 'rpool/zones/www2/ROOT/zb...@zbe-2': snapshot has dependent clones use '-R' to destroy the following datasets: rpool/zones/www2/ROOT/z...@20100709 rpool/zones/www2/ROOT/z...@electre rpool/zones/www2/ROOT/zbe m...@src:~# zfs list -r rpool/zones/www2 NAMEUSED AVAIL REFER MOUNTPOINT rpool/zones/www2 2.46G 11.9G37K /zones/www2 rpool/zones/www2/ROOT2.46G 11.9G18K legacy rpool/zones/www2/ROOT/zbe1.81M 11.9G 1.76G legacy rpool/zones/www2/ROOT/zbe-2 2.45G 11.9G 1.03G legacy m...@src:~# zoneadm -z www2 halt m...@src:~# zoneadm -z www2 detach m...@src:~# zfs list -r rpool/zones/www2 NAMEUSED AVAIL REFER MOUNTPOINT rpool/zones/www2 2.46G 11.9G37K /zones/www2 rpool/zones/www2/ROOT2.46G 11.9G18K legacy rpool/zones/www2/ROOT/zbe1.81M 11.9G 1.76G legacy rpool/zones/www2/ROOT/zbe-2 2.45G 11.9G 1.03G /zones/www2/root Can i safely destroyed the datasets above, if i understand well, my zone is only using: rpool/zones/www2/ROOT/zbe-2 thanks for help, 2010/12/22 John D Groenveld jdg...@elvis.arl.psu.edu In message aanlkti=by3uj7pz_qns17s-py37=e_cpkvjqrzuei...@mail.gmail.come_cpkvjqrzuei%2...@mail.gmail.com, gera rd henry writes: i have a sun x4150 with 4 zones (b111). I want to upgrade to b134, before upgrading to S11express. The process fails. As a workourand, i'm trying to move zones on another server in b134. So i'm tryng to follow the official document found here: http://docs.sun.com/app/docs/doc/819-2450 page 307. It also fails when trying to attach a zone on the destination server: zoneadm -z www2 attach -u Log File: /var/tmp/www2.attach_log.oJaO4J ERROR: no active dataset. What is the output of zfs list and mount for the filesystems associated with these zones? John groenv...@acm.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] failed to move zones in os2009.06 (attach failed)
wonderful, it works like a charm: m...@ultra20:~# zoneadm -z bibcmi4 attach -d rpool/zones/bibcmi4/ROOT/zbe-2 Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z Non-Global zone version: ent...@0.5.11,5.11-0.111:20090518T052643Z Evaluation: Packages in bibcmi4 are in sync with global zone. Attach complete. m...@ultra20:~# zoneadm list -cv ID NAME STATUS PATH BRANDIP 0 global running/ native shared - bibcmi4 installed /zones/bibcmi4 ipkg shared - myzone installed /export/home/myzoneipkg shared Is the a documentation anywhere? How do you know about this option? Thanks very much for you help gerard -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] failed to move zones in os2009.06 (attach failed)
searching in the official docs, i.e. http://opensolaris.com, i went to the following url: http://wikis.sun.com/display/OpenSolarisInfo200906/Isolating+Your+Development+Work that gives strange urls: http://hub.opensolaris.org/bin/view/Community+Group+zones/flar_zones but flar doesn't exist in opensolaris http://www.solarisinternals.com/wiki/index.php/Zones_Best_Practices that talk about ufsdump, or cpio while other docs state about pax to save zones! i'm very confused. Does it mean that deploying zones in opensolaris is a bad choice? (i guess that's why i receive no reply from my post) -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] failed to move zones in os2009.06 (attach failed)
hello all, i need to move zones from serv1 to serv2. Every server is os2009.06 b111b On serv1, i have, after detach: serv1 # zfs list -r rpool/zones/bibcmi4 NAME USED AVAIL REFER MOUNTPOINT rpool/zones/bibcmi4 1.46G 8.43G38K /zones/bibcmi4 rpool/zones/bibcmi4/ROOT1.46G 8.43G18K legacy rpool/zones/bibcmi4/ROOT/zbe1.33M 8.43G 828M legacy rpool/zones/bibcmi4/ROOT/zbe-2 1.45G 8.43G 877M /zones/bibcmi4/root following this post: http://mail.opensolaris.org/pipermail/zones-discuss/2010-February/006060.html i send the snapshots on serv2, and i have: serv2 # zfs list -r rpool/zones/bibcmi4 NAME USED AVAIL REFER MOUNTPOINT rpool/zones/bibcmi4 1.29G 45.9G38K /zones/bibcmi4 rpool/zones/bibcmi4/ROOT1.29G 45.9G19K legacy rpool/zones/bibcmi4/ROOT/zbe 494M 45.9G 494M legacy rpool/zones/bibcmi4/ROOT/zbe-2 825M 45.9G 825M /zones/bibcmi4/root (the last line was legacy, and i set the mountpoint manually) i did a zonecfg, with create -a but now, it fails to attach: serv2 # zoneadm -z bibcmi4 attach ERROR: The -a, -d or -r option is required when there is no active root dataset. i found another thread related to this message: http://opensolaris.org/jive/thread.jspa?messageID=439124 but unfortunately, it doesn't help. The option doesn't exist in zoneadm, so i don't understand what's happen. The official docs http://docs.sun.com/app/docs/doc/817-1592/zone?a=view doesn't take this case into account (zonepaths on zfs). I need to move zones before upgrading to b134, thanks in advance for help, gerard -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Re: unable to migrate zone
Try 'zoneadm -z servimp2 attach -n /zones/servimp2'. If you get a arning add '-F' after 'attach'. very strange: t2000-root% zoneadm -z servimp2 attach -n /zones/servimp2 -n: illegal option -- n usage: attach [-F] Attach the zone to the system. The zone state must be 'configured' prior to attach; upon successful completion, the zone state will be 'installed'. The system software on the current system must be compatible with the software on the zone's original system. Specify -F to force the attach and skip software compatibility tests. t2000-root% cat /etc/release Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 14 November 2006 -n is only valid in Solaris Express? but, it seems i had success with this command befoire installing patch 118833-36 thanks for your reply gerard This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
