Sparse Root Zone using loopback refuses to shutdown

New to zones, so been following along with the System Administration Guide: Solaris Containers-Resource Management and Solaris Zones doc from Sun (#817-1592). Everything seems ok with a plain jane zone, but I've run into trouble trying to use the loopback method to mount some other filesystems.
The zone in question refuses to shut down no matter what method I use, and seemingly points to an RPC issue.
using zlogin from the global zone, I get this, and it just hangs:
# zlogin oracle_ods01 shutdown -i 0
Shutdown started. Fri Jul 24 08:40:02 PDT 2009
Cannot send to root on /dev/pts/2
open: No such device or address
Cannot send to root on /dev/pts/2
open: No such device or address
showmount: oracle_ods01: RPC: Rpcbind failure - RPC: SuccessLogged into the zone:
# shutdown -i 0
Shutdown started. Fri Jul 24 08:41:27 PDT 2009
Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
The system oracle_ods01 will be shut down in 1 minute
Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
The system oracle_ods01 will be shut down in 1 minute
Broadcast Message from root (pts/2) on oracle_ods01 Fri Jul 24 08:41:28...
The system oracle_ods01 will be shut down in 1 minute
showmount: oracle_ods01: RPC: Rpcbind failure - RPC: Success
Changing to init state 0 - please waitBasically, I'm guessing its related to communication between the zones, but I'm not sure exactly what I'm missing. It's a default Solaris 10 install, so I've not disabled anything that wasn't already disabled. I did enable pools, but thats about it for the changes I've made so far. I guess I"m jus tnot sure if I should be looking at something I need to do in the global zone, or if I need to do something in the sparse root zone.
Any insights appreciated, as I'm not sure that I didn't miss something along the way!
Edited by: jef_e on Jul 24, 2009 8:52 AM
I take that back - my other test zone also seems to be giving me issues. I initally issues a zone halt to shut it down, which seems to work for all zones. But is that recommended?

Similar Messages

Using a interface in a sparse-root zone on a different subnet

Hello,
is it possible to use interface ce0 for the global zone and configure interface ce1 for the non-global zone, but the interfaces are on a different subnet?
ce0 ... 10.5.5.18 / global zone
ce1 ... 192.168.5.18 / non-global zone
using Solaris 5.10 Generic_125100-10
I configured ce0 in the global zone (of course)
and I plumbed ce1 also in the global zone - but configured ce1 in the zones definition
zonecfg:oem> add net
zonecfg:oem:net> set physical=ce1
zonecfg:oem:net> set address=192.168.5.18The zone boots without any problems and it looks like this:
[global zone]
# ifconfig -a
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.5.5.18 netmask ffffff00 broadcast 10.5.5.255
        ether 0:3:ba:b0:53:39
ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        inet 0.0.0.0 netmask 0
        ether 0:3:ba:b0:53:39
ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        zone oem
        inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255[non-global zone]
# ifconfig -a
ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255I've read this is solved with GLDv3 drivers and exclusive IP instances mentioned in the blog http://blogs.sun.com/stw/entry/what_s_up_ce_doc -
so the system shows
# dladm show-link
ce0             type: legacy    mtu: 1500       device: ce0
ce1             type: legacy    mtu: 1500       device: ce1I get weird results even if I ping between the zones, I get "ICMP Destination unreachable"
Can this be solved with a full-root zone ...?
-- Nick

here are my current settings:
*[global zone]*
# netstat -nr
Routing Table: IPv4
Destination           Gateway           Flags Ref   Use   Interface
10.5.5.0             10.5.5.18          U         1 10864 ce0
224.0.0.0            10.5.5.18          U         1      0 ce0
default             10.5.5 .1          UG        1 42839
127.0.0.1            127.0.0.1          UH        2 619817 lo0
# ifconfig -a
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.5.5.18 netmask ffffff00 broadcast 10.5.5.255
        ether 0:3:ba:b0:53:39
ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        inet 0.0.0.0 netmask 0
        ether 0:3:ba:b0:53:39
ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        zone oem
        inet 192.168.5.18 netmask ffffff00 broadcast 192.168.5.255
! root@elba2:/ # route get 192.168.5.18
   route to: 192.168.5.18
destination: 192.168.5.18
       mask: 255.255.255.255
interface: ce1:1
      flags: <UP,DONE>
recvpipe sendpipe ssthresh    rtt,ms rttvar,ms hopcount      mtu     expire
       0         0         0         0         0         0      8232         0 *[sparse-root zone]*
# netstat -nr
Routing Table: IPv4
Destination           Gateway           Flags Ref   Use   Interface
192.168.5.0          192.168.5.18         U         1     83 ce1:1
224.0.0.0            192.168.5.18         U         1      0 ce1:1
127.0.0.1            127.0.0.1            UH       19 86105 lo0:1
# ifconfig -a
ce1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 7
        inet 192.168.5.18 netmask ffffff00 broadcast 192.168.1.255
# route get 10.5.5.18
   route to: 10.5.5.18
destination: 10.5.5.18
       mask: 255.255.255.255
interface: ce0
      flags: <UP,DONE>
recvpipe sendpipe ssthresh    rtt,ms rttvar,ms hopcount      mtu     expire
       0         0         0         0         0         0      8232         0 Thank you for your time !
-- Nick

SAP Install on Solaris 10 Sparse Root Zone ../usr/sap

Hi All,
I was wondering if anyone is running SAP on Solaris 10, SAP EHP4 ECC 6.0 Oracle DB version 10. App and Db in a sparse root zone.
When we initially created our SAP install the Directories containing <SID> and trans_<SID> was give to us as "/usr/sap"
Since this is a sparse root zone, the /usr directory is read only. To accommodate SAP, a directory was created in the global zone for each of the containers ( we have ECC, PI, BW etc..) and then mounted as a filesystem in each container.   /usr/sap exists in every container, and it was supposed to be nothing more than a mount point for the <SID> and trans_<SID> NFS mounts. This /usr/sap directory exists on the global zone of our M5000 and the additional files and folders are eating up OS space.
This creates me with two problems.
1. WHen I take a snapshot, I can't recover the zone in a automatic fashion because the local zone can not see the global /usr directory, so I have to recover that folder/file manually.
2. I don't know exactly, but files are being created in the usr/sap directory that is causing internal drives to grow quickly.
To resolve our issues it was determined that the best course of action is to remove the connection to the global zone by creating a /sap directory in each container and linking it as /usr/sap. The /sap directory will be an NFS/FC mount point and that will fix the issue of disk space usage and backup recovery.
Does anyone have another way to solve this problem or any suggestions that we should do something different. ?

I use sparse zones on Solaris with ZFS.
I delegate filesystems to the zone.
root@global ~# zonecfg -z zone_name info
zonename: zone_name
zonepath: /zfs_zones/zone_name
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
inherit-pkg-dir:
        dir: /lib
inherit-pkg-dir:
        dir: /platform
inherit-pkg-dir:
        dir: /sbin
inherit-pkg-dir:
        dir: /usr
net:
        address: w.x.y.z/nn
        physical: nxge0
        defrouter: w.x.y.z
dataset:
        name: zfs_zones/zone_name/oracle
dataset:
        name: zfs_zones/zone_name/sapmnt
dataset:
        name: zfs_zones/zone_name/usr_sap
root@zone_name ~# zfs list -o name,mountpoint
NAME                                     MOUNTPOINT
zfs_zones/zone_name/oracle               /oracle
zfs_zones/zone_name/oracle/SID_mirrlogA /oracle/SID/mirrlogA
zfs_zones/zone_name/oracle/SID_mirrlogB /oracle/SID/mirrlogB
zfs_zones/zone_name/oracle/SID_oraarch   /oracle/SID/oraarch
zfs_zones/zone_name/oracle/SID_origlogA /oracle/SID/origlogA
zfs_zones/zone_name/oracle/SID_origlogB /oracle/SID/origlogB
zfs_zones/zone_name/oracle/SID_sapdata1 /oracle/SID/sapdata1
zfs_zones/zone_name/oracle/SID_sapdata2 /oracle/SID/sapdata2
zfs_zones/zone_name/oracle/SID_sapdata3 /oracle/SID/sapdata3
zfs_zones/zone_name/oracle/SID_sapdata4 /oracle/SID/sapdata4
zfs_zones/zone_name/sapmnt               /sapmnt
zfs_zones/zone_name/usr_sap              /usr/sap
Edited by: RUSS HANSEN on Dec 14, 2011 8:52 PM

Whole root or sparse root zones and patching

Hi all,
A while back, I did some cluster patching tests on a system with only sparse root zones, and one with whole root zones...and I seem to recall that the patch time was about equal which surprised me. I had thought the sparse root model mainly is patching the global zone, and even though patchadd may need to run through the sparse NGZ's...that it isn't doing much other than updating /var/sadm info in the NGZ's.
Has anyone seen this to be true or if there are major patching improvements using a "sparse" root NGZ model over a "whole" root model?
thanks much.

My testing showed the same results and I was a bit surprised as well. As I dug into it further my understanding was that the majority of the patch application time goes into figuring out what to patch, not actually copying files around. That work must be done for the sparse zones in the same way as for the full root zones, we just save the few milliseconds of actually backing up and replacing the file.
I suspect there is a large amount of slack that could be optimized in the patching process (both with and without zones), but I don't understand it nearly well enough to say that with any authority.

How to add /usr/local to sparse-root zone ?

I had created sparse-root local zone. The installed some soft and realised that I would need /usr/locain the zone. But I have problem with adding it.
Original configuration of the zone:
bash-3.00# zonecfg -z z1
zonecfg:z1> info
zonepath: /zones/z1
autoboot: true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address: x.x.x.x/y
physical: elxl0
zonecfg:z1>Current configuration:
bash-3.00# zonecfg -z z1
zonecfg:z1> info
zonepath: /zones/z1
autoboot: true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
fs:
dir: /usr/local
special: /zones/z1-local
raw not specified
type: lofs
options: [rw]
net:
address: x.x.x.x/y
physical: elxl0Now:
bash-3.00# zoneadm -z z1 boot
zoneadm: zone 'z1': Could not mkdir /zones/z1/root/usr/local.
zoneadm: zone 'z1': It is on a read-only file system in this local zone.
zoneadm: zone 'z1': Make sure /usr/local exists in the global zone.
zoneadm: zone 'z1': call to zoneadmd failedprzemol

The messages contains all you need:
zoneadm: zone 'z1': Make sure /usr/local exists in the global zone.Just do a "mkdir /usr/local" in global zone and your zone installation will work.
But: Unfortunately you will get into trouble, if you want to install some software packages into /usr/local later.
Installation of Software below an inherited filesystem like /usr is not supported and somewhat impossible. The fact that /usr/local is a mounted filesystem does not count here.
These type of problems are already discussed in this forum...

Sparse Root Zone Mount Points

In my zone xml files I have configured filesystems to be mounted in the non global zones.
The filesystems exists on separate SAN storage.
filesystem special=/dev/dsk/controllerdisknumber raw=/dev/dsk/controllerdisknumber directory=/somemountpoint
The problem we are experiencing is that occasionally our path to the SAN goes down. Yes these are multipathed but we still experience the outage.
What happens is that the filesystems that are mounted in the NGZ's go away. So the zone is left running
but the mountpoints are not mounted any longer.
When the path to the SAN comes back, the global zone sees that the devices are back, but the NGZ still
does not mount their filesystems as specified in their specific xml.
The only way for the mount points to come back is to 1) reboot the zone or 2) manually mount the filesystems from the global zone, specifying that they be mounted in the NGZ.
Is this working as it should? Should the zone not attempt to remount its filesystems if they are lost?
Instead of specifying a filesystem in the zoneconfig, should we just be giving the devices to the zone and then use the NGZ /etc/vfstab to mount ?
Thank you for the help.

I've seen this issue also, but not aware of a good fix.
One possibility that comes to mind but I havent actually tested is to do a NFS export from the global zone and automount it in the local zone.
The automounter shoud deal with mountpoint reliability issues OK.
Its kind of ugly and isnt likely to be as efficient as a loopback mount though.

Whole Root / Sparse Root fusion // lofs problem

Hello everybody!
Actually i am getting probz with installations of software in sparse-root zones.
Especially caused by the lofs-techniques regarding /usr , /usr/bin and /usr/local, required for linking back the executables to the home folders of users in Sparse-Root zone.
are there any workarounds to obtain a functional setup for this cases or override the lofs-problem for linkage .
Read only after install to /usr/bin is o.k. but for Software install in Sparse Root it`s needed.
Encountered this problems with Oracle and DirX installs.
Whole-root zone obligation and the inherit disk usage would be unacceptable.
Would be running out of disk space.
Thanks for Replies !

Is there any option setable to temporarily override the "ro" lofs for an inherited-pkg-dir?
-fs-special?
The Application i want to install is DIRX for LDAP management.
It links the executable from /usr/bin to /export/home/ldap before finising the Installation.
The Installation is cacelled by the installer if the links cant be set.
After install there is no problem with "ro" access to the executable..
If i had to do all zones as whole-root zones i would use Xen on an Intel or amd based machine.
Sparse-root zone model is posible with Xen, but implies a lot of work.
The decision to solaris was due to low performance of Linux Kernels on Sparc compared with a native Solaris, the hardware of a Fire 880 was built for.
Any HowTo`s to a Workaround, e.g. a comand string ?( 4meNxDummy? ;) )

Sparse or full root Zones?

Hi,
having 'played' with zones for a while , the time has now come to start developing policies for their use within a consolidation programme. One area that is particularly unclear is; when do you use sparse zones as opposed to full root zones (disk space is not a problem within my organisation, so the decision can be technically rather than resource based).? To date I have not been able to find any documented recommendations and I would be interested in the views of the forum - thanks

IMHO, try to stick with sparse local zones unless the particular services to be provided by the zone require being able to write to any of the read-only file systems, especially /usr.
-mel

SMC - Solaris Management Console in whole root zone

Hi,
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.
Thanks...

Hi dnzrnd,
dnzrnd wrote:
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

Solaris Management Console in whole root zones

Is it possible to run smc in whole root zone? Is there a howto for this? I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.

Hi dnzrnd,
dnzrnd wrote:
Is it possible to run smc in whole root zone? Is there a howto for this?
I have created a whole root zone in my x86 and sparc systems but I can't seem to manage the zones through smc (Adding users, share disks and etc).
I was able to manage my sparse zones with smc but for some reason smc won't even start in whole root zone. The whole root zone does not seem to have smcserver and bunch of other directories relating to smc.SunMC should install and run fine in a whole-root zone: I haven't heard of any problems. Are you maybe confusing "Sun Management Center" (this forum) with "Solaris Management Console" (a different product)?
Regards,
[email protected]
http://www.HalcyonInc.com
New !! : http://forums.HalcyonInc.com !!

Unable to create a whole root zone

Hi Folks,
I wanted to create a whole-root zone. I am unable to create one :(. Did some one encounter this problem ?.
BTW: I have SC 3.2 installed on this two node cluster. I was able to validate our Data services on this setup without any problem Now I am trying to experiment with zones, by creating zones. I am unable to move further with my validation of our data services on zones.
*) mkdir -m 700 /export/zone-1
*) The version of the OS used
# cat /etc/release
Solaris 10 11/06 s10s_u3wos_09 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 01 November 2006
# zonecfg -z zone-1
zone-1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-1> create
zonecfg:zone-1> remove inherit-pkg-dir dir=/sbin
zonecfg:zone-1> remove inherit-pkg-dir dir=/usr
zonecfg:zone-1> remove inherit-pkg-dir dir=/platform
zonecfg:zone-1> remove inherit-pkg-dir dir=/lib
zonecfg:zone-1> set autoboot=true
zonecfg:zone-1> set zonepath=/export/zone-1
zonecfg:zone-1> add net
zonecfg:zone-1:net> set address=192.18.75.237
zonecfg:zone-1:net> set physical=eri0
zonecfg:zone-1:net> end
zonecfg:zone-1> info
zonename: zone-1
zonepath: /export/zone-1
autoboot: true
pool:
limitpriv:
net:
address: 192.18.75.237
physical: eri0
zonecfg:zone-1> verify
zonecfg:zone-1> commit
zonecfg:zone-1> exit
# cat /etc/zones/zone-1.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">

<zone name="zone-1" zonepath="/export/zone-1" autoboot="true">
<network address="192.18.75.237" physical="eri0"/>
</zone>
# zoneadm list -civ
ID NAME STATUS PATH
0 global running /
- zone-1 configured /export/zone-1
# zoneadm -z zone-1 verify
# zoneadm -z zone-1 install
Preparing to install zone <zone-1>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-1> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWsczr
application SUNWsczr Sun Cluster (non-global zones support)
# pkginfo -i SUNWdtlog
system SUNWdtlog System boot for Desktop Login
# pkginfo -i SUNWsmmgr
system SUNWsmmgr System Management Agent Startup scripts
*** package <SUNWsczr> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/stoprgm> failed
pathname does not exist
NOTE: When the package <SUNWsczr> was installed in the global zone, the file <etc/init.d/stoprgm> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone <zone-1> in the file </export/zone-1/root/etc/init.d/stoprgm>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWsczr/save/pspool/SUNWsczr/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWsczr> on zone <zone-1> failed.
*** package <SUNWnisr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nis> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nis> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nis>.
WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <etc/nsswitch.nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/nsswitch.nisplus>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nisplus> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <lib/svc/method/nisplus> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nisplus>.
WARNING: attribute verification of </export/zone-1/root/var/nis/NIS+LDAPmapping.template> failed
pathname does not exist
NOTE: When the package <SUNWnisr> was installed in the global zone,
the file <var/nis/NIS+LDAPmapping.template> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/nis/NIS+LDAPmapping.template>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ nis/client.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/nisplus.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/rex.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/nisplus.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rex.xml> failed
pathname does not exist
Installation of <SUNWnisr> on zone <zone-1> partially
failed.
*** package <SUNWypr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/var/yp/updaters> failed
pathname does not exist
NOTE: When the package <SUNWypr> was installed in the global zone,
the file <var/yp/updaters> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/yp/updaters>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/passwd.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/server.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/update.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/xfr.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/passwd.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/server.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/update.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/xfr.xml> failed
pathname does not exist
Installation of <SUNWypr> on zone <zone-1> partially
failed.
*** package <SUNWipplr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWipplr/save/pspool/SUNWipplr/reloc/var/svc/manifest/applic ation/print/ipp-listener.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/ipp-listener.xml> failed
pathname does not exist
Installation of <SUNWipplr> on zone <zone-1> partially
failed.
*** package <SUNWaccr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-sar> failed
pathname does not exist
NOTE: When the package <SUNWaccr> was installed in the global zone,
the file <lib/svc/method/svc-sar> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-sar>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWaccr/save/pspool/SUNWaccr/reloc/var/svc/manifest/system/s ar.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/sar.xml> failed
pathname does not exist
Installation of <SUNWaccr> on zone <zone-1> partially
failed.
*** package <SUNWbsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/rpld.conf> failed
pathname does not exist
NOTE: When the package <SUNWbsr> was installed in the global zone,
the file <etc/rpld.conf> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/rpld.conf>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/ra rp.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/rp c/bootparams.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rarp.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/bootparams.xml> failed
pathname does not exist
Installation of <SUNWbsr> on zone <zone-1> partially
failed.
*** package <SUNWdhcsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dhcp> failed
pathname does not exist
NOTE: When the package <SUNWdhcsr> was installed in the global zone,
the file <etc/init.d/dhcp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dhcp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWdhcsr/save/pspool/SUNWdhcsr/reloc/var/svc/manifest/networ k/dhcp-server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dhcp-server.xml> failed
pathname does not exist
Installation of <SUNWdhcsr> on zone <zone-1> partially
failed.
*** package <SUNWatfsr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-autofs> failed
pathname does not exist
NOTE: When the package <SUNWatfsr> was installed in the global zone,
the file <lib/svc/method/svc-autofs> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-autofs>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWatfsr/save/pspool/SUNWatfsr/reloc/var/svc/manifest/system /filesystem/autofs.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/filesystem/autofs.xml> failed
pathname does not exist
Installation of <SUNWatfsr> on zone <zone-1> partially
failed.
*** package <SUNWkdcr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWkdcr/save/pspool/SUNWkdcr/reloc/var/svc/manifest/network/ security/krb5_prop.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/security/krb5_prop.xml> failed
pathname does not exist
Installation of <SUNWkdcr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.gif> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.gif> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.gif>.
WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.png> failed
pathname does not exist
NOTE: When the package <SUNWapch2r> was installed in the global zone,
the file <var/apache2/icons/world2.png> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.png>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWapch2r/save/pspool/SUNWapch2r/reloc/var/svc/manifest/netw ork/http-apache2.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/http-apache2.xml> failed
pathname does not exist
Installation of <SUNWapch2r> on zone <zone-1> partially
failed.
*** package <SUNWbindr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbindr/save/pspool/SUNWbindr/reloc/var/svc/manifest/networ k/dns/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dns/server.xml> failed
pathname does not exist
Installation of <SUNWbindr> on zone <zone-1> partially
failed.
*** package <SUNWbnur> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWbnur/save/pspool/SUNWbnur/reloc/var/svc/manifest/network/ uucp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/uucp.xml> failed
pathname does not exist
Installation of <SUNWbnur> on zone <zone-1> partially
failed.
*** package <SUNWcnsr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ chargen.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ daytime.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ discard.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ echo.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ time.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/chargen.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/daytime.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/discard.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/echo.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/time.xml> failed
pathname does not exist
Installation of <SUNWcnsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/lp/fd/pr.fd> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <etc/lp/fd/pr.fd> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/lp/fd/pr.fd>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/print-svc> failed
pathname does not exist
NOTE: When the package <SUNWpsr> was installed in the global zone,
the file <lib/svc/method/print-svc> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/print-svc>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWpsr/save/pspool/SUNWpsr/reloc/var/svc/manifest/applicatio n/print/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/server.xml> failed
pathname does not exist
Installation of <SUNWpsr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/var/snmp/mib/sun.mib> failed
pathname does not exist
NOTE: When the package <SUNWsacom> was installed in the global zone,
the file <var/snmp/mib/sun.mib> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/var/snmp/mib/sun.mib>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.dmi> is corrupt
file size <373> expected <1125> actual
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.snmpdx& gt; is corrupt
file size <382> expected <685> actual
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.dmi> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.snmpdx> failed
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/dmi.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/snmpdx.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/dmi.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/snmpdx.xml> failed
pathname does not exist
Installation of <SUNWsacom> on zone <zone-1> partially
failed.
*** package <SUNWdtlog> failed to install with fatal errors:
WARNING: attribute verification of </export/zone-1/root/etc/init.d/dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <etc/init.d/dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/init.d/dtlogin>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-dtlogin> failed
pathname does not exist
NOTE: When the package <SUNWdtlog> was installed in the global zone,
the file <lib/svc/method/svc-dtlogin> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/svc-dtlogin>.
ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/archive.
pkgadd: ERROR: class action script did not complete successfully
Installation of <SUNWdtlog> on zone <zone-1> failed.
*** package <SUNWnfssr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nfs-server> failed
pathname does not exist
NOTE: When the package <SUNWnfssr> was installed in the global zone,
the file <lib/svc/method/nfs-server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/nfs-server>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/rquota.xml> is corrupt
pathname does not exist
pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/server.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/rquota.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/server.xml> failed
pathname does not exist
Installation of <SUNWnfssr> on zone <zone-1> partially
failed.
*** package <SUNWntpr> installed with warnings:
WARNING: attribute verification of </export/zone-1/root/etc/inet/ntp.server> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <etc/inet/ntp.server> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/etc/inet/ntp.server>.
WARNING: attribute verification of </export/zone-1/root/lib/svc/method/xntp> failed
pathname does not exist
NOTE: When the package <SUNWntpr> was installed in the global zone,
the file <lib/svc/method/xntp> was also installed. After the file was
installed in the global zone, the contents and/or attributes of the file
changed. The contents of this file must never be changed. As a result,
the changes in this file have been duplicated in the non-global zone
<zone-1> in the file </export/zone-1/root/lib/svc/method/xntp>.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWntpr/save/pspool/SUNWntpr/reloc/var/svc/manifest/network/ ntp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ntp.xml> failed
pathname does not exist
Installation of <SUNWntpr> on zone <zone-1> partially
failed.
*** package <SUNWftpr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWftpr/save/pspool/SUNWftpr/reloc/var/svc/manifest/network/ ftp.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ftp.xml> failed
pathname does not exist
Installation of <SUNWftpr> on zone <zone-1> partially
failed.
*** package <SUNWrcapr> installed with warnings:
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcapr/save/pspool/SUNWrcapr/reloc/var/svc/manifest/system /rcap.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/rcap.xml> failed
pathname does not exist
Installation of <SUNWrcapr> on zone <zone-1> partially
failed.
pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcmdr/save/pspool/SUNWrcmdr/reloc/var/svc/manifest/networ k/talk.xml> is corrupt
pathname does not exist
chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/comsat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/finger.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/login.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rexec.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rstat.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rusers.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/spray.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/wall.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/shell.xml> failed
pathname does not exist
ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/talk.xml> failed
pathname does not exist
Installation of <SUNWrcmdr> on zone <zone-1> partially
failed.
WARNING: attribute verification of </export/zone-1/root/etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> ; failed
pathname does not exist
NOTE: When the package <SUNWsmmgr> was installed in the global zone,
the file <etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> was also installed. Af

Hello,
I still get the errors.
# zonecfg -z zone-one
zone-one: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:zone-one> create -b
zonecfg:zone-one> set autoboot=true
zonecfg:zone-one> set zonepath=/export/zone-one
zonecfg:zone-one> add net
zonecfg:zone-one:net> set physical=eri0
zonecfg:zone-one:net> set address=192.18.xx.xxx
zonecfg:zone-one:net> end
zonecfg:zone-one> verify
zonecfg:zone-one> commit
zonecfg:zone-one> exit
# zoneadm -z zone-one verify
# zoneadm -z zone-one install
Preparing to install zone <zone-one>.
Creating list of files to copy from the global zone.
Copying <6080> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1071> packages on the zone.
Initialized <1071> packages on zone.
Zone <zone-one> is initialized.
Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
_DD

Whole root zone doesn't run Solaris Management Console

All
I created a couple of Whole Root zone's, but the SMC is not working. It can't even be found. (However, on the "sparse" zones, it works fine.)
I ran:
pkginfo SUNWsmcmd
and got:
system SUNWsmcmd System Management Agent applications and utilities
So, it seems like it's installed, but it ain't working on any of the whole-root zones.
Anyone have any ideas on this one?
Thank you
SB

I think I have the same problem -
One global zone and one whole-root zone installed.
I access the server withhttps://servername:6789/containersthen I can see Solaris Container Manager 3.6.1but when I select it, I get
There was an error while connecting to the Solaris Container Manager service. Restart the services and login again.
Restart Sun Management Center services and log in again.I restarted meanwhile every service, but I did not a server reboot.
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   1 mantis-ldap      running        /var/zone/mantis-ldapWhat logfile could help to clarify that?
SMC release is 3.6.1
-- Nick

Whole root zone and packages

I installed in my global zone the "Entire Distribution" of Solaris 10 and some software from Companion CD.
Now I would like install a "whole root zone" with a basic set of packages (like "End User Distribution") and without the packages
from the Companion CD.
I can use pkgrm to delete the unnecessary packages in my whole root zone.
But is there a more elegant way to get a whole root zone only with basic packages?
Regards. P.

The "easy" way would be to do a minimal installation in the Global zone and then install the required services in the local zone.
HTH,
Roger S.

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

Best Practices for patching Sun Clusters with HA-Zones using LiveUpgrade?

We've been running Sun Cluster for about 7 years now, and I for
one love it. About a year ago, we starting consolidating our
standalone web servers into a 3 node cluster using multiple
HA-Zones. For the most part, everything about this configuration
works great! One problem we've having is with patching. So far,
the only documentation I've been able to find that talks about
patch Clusters with HA-Zones is the following:
http://docs.sun.com/app/docs/doc/819-2971/6n57mi2g0
Sun Cluster System Administration Guide for Solaris OS
How to Apply Patches in Single-User Mode with Failover Zones
This documentation works, but has two major drawbacks:
1) The nodes/zones have to be patched in Single-User Mode, which
translates to major downtime to do patching.
2) If there are any problems during the patching process, or
after the cluster is up, there is no simple back out process.
We've been using a small test cluster to test out using
LiveUpgrade with HA-Zones. We've worked out most of bugs, but we
are still in a position of patching our HA-Zoned clusters based
on home grow steps, and not anything blessed by Oracle/Sun.
How are others patching Sun Cluster nodes with HA-Zones? Has any
one found/been given Oracle/Sun documentation that lists the
steps to patch Sun Clusters with HA-Zones using LiveUpgrade??
Thanks!

Hi Thomas,
there is a blueprint that deals with this problem in much more detail. Actually it is based on configurations that are solely based on ZFS, i.e. for root and the zone roots. But it should be applicable also to other environments. "!Maintaining Solaris with Live Upgrade and Update On Attach" (http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach)
Unfortunately, due to some redirection work in the joint Sun and Oracle network, access to the blueprint is currently not available. If you send me an email with your contact data I can send you a copy via email. (You'll find my address on the web)
Regards
Hartmut

Sparse Root Zone using loopback refuses to shutdown

Similar Messages

Maybe you are looking for