When you add a patch to the global zone and to all non global zones, you do not have to consider whether the patch affects areas that are shared from the global zone. Use zoneadm z with the boot s option to start an installed zone. Solaris liveupgrade is a nice feature of solaris, which lets one upgrade the currently running version of solaris to a new realease or patch it without the need to bring the system into single user mode for a more or less long time. Fujitsu solaris 10 hardware platform manual pdf download. I have used the patch version 12143174 which worked like charm. How to verify nonglobal solaris zone is installed the geek diary. Failed to determine zone configuration for target boot environment.
I have tried to login to the non global zone and install it manually. If rcapadm e fails to start rcapd, you may need to use the solaris. This is especially true in a zones environment, where patchadd calls the zones utilties in order to patch the non global zone s after patching the global zone. For me liveupgrade patch 12143154 gave lot of trouble after booting from alternative boot environment. Bring up the local zone on the global zone where it comes up online without any issues. This message indicates that the non global zone in question was halted, and patchadd was not able to move the affected zone into an internal state used for software maintenance. Fixing a broken solaris zone i applied the latest set of patches to my x86 solaris 10 server this morning, and after the server was rebooted i noticed that my zones didnt start. Patching might fail with below error message if the directory is not readable by others.
Is the only zone from which a non global zone can be configured, installed, managed, or uninstalled. If a non global zone is not running when patchadd is run, patchadd will boot the non global zone into single user mode so that the patchadd will work, and then return the zone to its original state. Make patchadd modify packages in the current zone only. The first step is obviously to identify which piece of hardware failed. In the above commands it should have been possible to use e.
If the patch package is set to false, the installation can occur in either the global or non global zone. The patchadd utility cannot add the patches to the global zone only or to a subset of the non global zones. Is assigned a zone id by the system when the zone is booted. If using live upgrade to upgrade an inactive boot environment from solaris 8 or 9 to solaris 10, you must activate and boot into the solaris 10 boot environment before patching it. Cannot install zone on solaris 11 unix and linux forums. However, this patch fails to install due to the non global zone does not have.
This message indicates that the nonglobal zone in question was halted, and patchadd was not able to move the. The non global zone autoboot the setting to automatically start up the non global zone during startup of the global zone. Is the only zone with knowledge of non global zone existence and configuration. Which task needs to be performed before you can boot zone1. The root file system of any non global zones must not be referenced with the r option. The patch does not affect any area of the zone that is shared from the global zone. Failed to boot non global zone zone name this message indicates that the non global zone in question was halted, and patchadd was not able to move the affected zone into an internal state used for software maintenance.
So before considering using zone update on attach to speed up patching, you need to be aware of the differences between using update on attach to bring a non global zone up to the same patch level as the global zone versus just using patchadd with all the non global zones attached and available for patching. Oracle solaris 11 overview and design guide fujitsu global. Patches 11925452 or later and 12266010 need to be loaded on the global zone and all non global zones first. The solaris 8 containers righttouse package has not. Use this option to maintain a global baseline patch set.
A patch can be added to a nonglobal zone in the following cases. For the third option, read the output of patchadd carefully you will see the command iterate over all the non global zones. Solaris 10 live upgrade with zfs and nonglobalzones fail. Applying patches on a solaris system with zones installed system. When used in a non global zone, the patch is removed from packages in the non global zone only. In this example, the global zone is ash global zone 1 and local zone is ashlocal zone. On the global zone, boot the new zone by issuing zoneadm z boot. The idea of upgrading and patching has prompted me to make sure i can do this on a live system. Zones pca can be run both in the global zone or any non global zone. Oracle 1z0821 oracle solaris 11 system administration.
See interaction of g and pkginfo variable in zones, below. It seems the patching script was trying to access the local zone filesystems or zoneadm utility but could not. In this example it will be the boot disk, which is is devdskc0t0d0. If non global zones have their own separate root file systems, make sure all of them are mounted. I was trying to upgrade to the latest patch level, but in single user mode while updating patch cluster i get ailed to boot non global zone zone3 failed exit code 1 failed 01. If i start zones then patchadd works ok, however not an option when trying to install patch bundle. Solaris branded zones running on a ldom part 46 boot r. This could have several reasons and details need to be checked. Migrating a nonglobal zone to a different machine manas. New solaris update releases often have patches preinstalled which are not yet listed in patchdiag. When used in a nonglobal zone by the zone administrator, patchadd can only be used to add patches to that zone. Installing, booting, halting, uninstalling, and cloning nonglobal zones tasks. What is interesting is that this patch installed fine on my other server and it also patched the non global zone.
This wasnt a problem in solaris 8 or solaris 9, as the amount of code change delivered in patches was limited. Potentially problematic solaris 10 patches oracle solaris blog. To add a patch to the global zone and to all nonglobal zones, run patchadd as. When i ran the zoneadm utility with the list option, all of the zones were in the installed state they should be in the running state since the autoboot.
Solaris 10 kernel patches looks hard, but it isnt oracle. During this process what files will get affect in non global zones and which mechanism its using to change. When used in the global zone, the patch is added to packages in the global zone only and is not propagated to packages in any existing or yettobecreated nonglobal zone. Ifthere is a requirement to use odmstat in a solaris 10 local zone, it is possibleto do so by following one of two procedures. This worked, apart from shed loads of messages about being unable to remove files from readonly filesystems, i think this was again due to the non global zone.
If an ignored patch is required by another patch, this patch might fail to install due to the missing. Limitations and known bugs remarks recommended actions i installation and removal of a package or patch may fail in a system with non global zones, under the following conditions. When patching an inactive be, this patch should be installed manually to the active be, as its patch installation utilities are used even when rootdir is set. It is important that the zone is in the appropriate installed state before one can boot it up. If a non global zone has its own separate var file system, both 11925452 or later and patch 12266010 must be loaded on all. The zone configuration has to be instantiated and packages have to be installed under the zones root path. For example, activate and boot into the solaris 10 boot environment, and either patch the live boot environment or create another inactive boot environment, and then. Analyzing a patchadd or patchrm failure in the solaris os oracle. Install the recommend os patch bundle on new boot environment. Shares operation under the solaris kernel booted from the global zone. Pca always installs the patch for the patch installation utilities first to avoid possible bugs in patchadd. The configured zone has to be installed with the operating environment.
Failed to boot nonglobal zone zone name this message indicates that the nonglobal zone in question was halted, and patchadd was not able to move the affected zone into an internal state used for software maintenance. When used in a nonglobal zone, the patch is added to packages in the nonglobal zone only. There is a procedure to add and remove patches from a system with zones at. Patch for solaris users guide hcl software product. Recovering from a failed boot disk is not a very difficult procedure using solstice disksuite when the system has been properly setup and documented initially. This is a known problem and is usually due to the nonglobal zone file systems not being mounted in singleuser mode. Jul 25, 2012 if you want to use liveupgrade feature on oracle solaris 10, oracle recommends to patch the liveupgrade packages to the latest version since lot of bugs with old patch versions. Load patch 12266010, required patches 11873101, 11883333 or later, 12090004, 121302, 12264002, 12420404. Live upgrade patch installation before os patching unixarena.
The fixlet content for such a patch has only one installation action. Hi, if i change date and time in global zone, then it will affect in non global zones. Can not boot non global zone syswithz01 verifying that patch 11925432 is installed. Solaris 10 live upgrade with zfs and non global zones fail the goal was to consolidate 40 or so physical servers onto a m4000. For more information about the patchadd option, see. This will occur when etczonesindex in the inactive boot environment has an incorrect setting for the state for the global zone. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Make sure the global zone and all non global zones are in single user mode repeating steps 1 3 7. Applying patches on a solaris system with zones installed. The zone will not boot if the command has not been run again. If the patch package is set to true, this means that oracle forces the installation to all zones global and non global zones. Dec 27, 2011 failed to boot nonglobal zone during patchadd or patchrm or installpatchset 1.
Doing so might damage the global zone s file system, might compromise the security of the global zone, and might damage the non global zone s file system. You can bring down the local zone to single user mode,by just issuing init 1 command from local zones os console. To display a list of patches currently applied, you can continue to use the patchadd command with the p option or the. Dec 01, 2011 a zone might fail to boot if it is not properly configured. How to capture failed login attempts from tty logins telnet, rlogin, and terminal. If using a configuration where non global zone images are not shared between cluster nodes, the zone names the names of zones as defined by zonecfg and zoneadm z must. Thanks steve, this sounds like you are using non global zones. Failed to boot nonglobal zone zone name during patchadd or patchrm or installpatchset 1. When i ran zoneadm with the the boot option and the name of the zone to boot, i was greeted with the following error. Fixing a broken solaris zone prefetch technologies. Automated install ai from network boot solarissmallserver. The file systems that your local zone s are mounted from home0zonestest is not reachable while this patch is being applied. Problems patching solaris 10 system with zones oracle.
1081 1202 298 125 1540 1026 902 1043 706 1040 436 1215 709 1357 385 432 1332 1236 1553 69 103 902 556 514 1193 592 1423 184 1417 594 451 5 1498 1361 1233 1164 927