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">
<!--
DO NOT EDIT THIS FILE. Use zonecfg(1M) instead.
-->
<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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Similar Messages

  • 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 !!

  • Whole root zone and fibre channel hba

    I have Solaris 10 x86 loaded up on an IBM blade. I've created a whole root zone on it and have installed Symantec NetBackup 6.5.5 and configured it as Media Server. I have an SL8500 tape library in the environment and all the tape drives are fibre channel. Now, in the global zone, I can run fcinfo hba-port or scli and the global zone finds the hba's with no problem. I've added the /dev/cfg/c1 and /dev/cfg/c2 devices to the zone, but running the commands, it cannot find the hba's at all.
    Is there something else that I need to do so that the zone can see the hba's, or is this just not possible in a zone?
    Thanks in advance,
    Ed Coates

    Hi.
    Check release notes for Netbackup. As i know Media Server is supported anly at Global zones.
    You can add access to /dev/rmt/* and give access to tapes, but stiil problem with robot device and this configuration not supported.
    Regards.

  • 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

  • Secure shell in a whole root zone

    Hello,
    I have two whole root zones running on my Solaris 10 server along with the global zone. I am able to secure shell in to the global zone, but not the whole root zones. Secure shell does not appear to be running in the whole root zones. I've tried svcadm restart ssh in the whole root zones,but no luck. What do I need to do to get secure shell working on the whole root zones?

    to create the necessary keys -
    # ssh-keygen -b 1024 -t rsa1 -f /etc/ssh/ssh_host_key -N ""
    # ssh-keygen -b 1024 -t rsa -f /etc/ssh/ssh_host_rsa_key -N ""
    # ssh-keygen -b 1024 -t dsa -f /etc/ssh/ssh_host_dsa_key -N ""-- Nick

  • SMC doesn't work in any solaris 10 whole-root zones

    All
    Are you aware of SUN not designing whole-root zones to work with Solaris Management Console?
    None of my solaris 10 whole-root zones/containers will run Solaris Management Console. Very, very frustrating!
    Anyone have a trick to get around this crazy design??
    Thank you!
    SB

    Thanks for your help!
    Yes, i see all font types.
    But maybe i havn't explained my problem good enough:
    I have a FLA-File which works great in Flash CS3: everything – even on different computers – is okay!
    The same FLA-File on the same computer in Flash CS6: the font-rendering is broken!
    In CS6 there seems to be a difference between textfields made via ActionScript and textfields on the stage: see the attached file in my first post.

  • Replication whole root zones

    Hello,
    I need to configure whole root zones which needs to be replicated to a secondary site.
    Would like to know if there is a way by which i can avoid replicating the swap file in a whole root zone configuration.
    Please advice.
    Thanks & Regards
    Ranjit

    I don't understand your question. What swap file are you referring to? There's nothing about a whole-root zone that requires a swap file be present.
    Darren

  • 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.

  • Whole root zone creation

    Hi
    I am building a whole root zone  running Solaris U9  I noticed the   zone does not get installed with  some updated packages  from global zone like the openssl installed in global zone does not get installed in the non global zone and it also requires  sshd user to be defined This results  the ssh not starting in the new zone  I want to know if this  is the default behaviour of whole root zone installation process and how can we  get the zone to be installed with all the  currently running packages  of the global zone Are there any post installation steps that  need to be followed for the zone to boot up correctly. I have run the  post  post installation configuration steps as well
    TIA

    Thanks Walter
    I was wondering  since most of the packages  installations at least  require one interaction   where it asks  for confirmation.  how  the other  packages are getting installed. But mostly that might be the reason
    There is also  the SUNW_PKG_ALLZONES and other related variables   which control  this but  since here the packages which are already installed on global zome are getting installed on NG zone , how these parameters can be changed I could not found  any of these parameters in any pkginfo file in the global zone

  • Patching JES  in whole root zone (where JES never installed in global zone)

    We ran into a problem today - we have a server (Solaris 10 x86 on 4150) with two full root zones. JES 5u1 was intsalled in each full root zone at a later date and never installed in the global zone. Now when trying to install the latest JES 5 patch cluster we have run into a problem. The patch cluster has a check that only lets it be run in the global zone. When we run it in the Global Zone - it exits every patch with a return code of 8 (software not installed).
    Is there any way we can run the patch bundle so it applies the patches to the no-global zones in this case? Will now installing teh shared components in the global zone then allow the patch cluster to run sucessfully.
    Thanks for any guidance here....

    Solution was to manually edit the patch cluster installation script and comment out the global zone check - it then installed perfecttly fine in the whole root zone

  • Whole root zone / remove /usr /platform /bin

    is it possible to remove /usr /platform /bin from non-globale zone ? iam running a braded zone (solris 8) on global zone (sol 10). i tried to use remove inherit-pak when creating the zone, but it didnt work.
    what iam missing here ?
    zonecfg:sol8> remove inherit-pkg-dir dir=/lib
    remove inherit-pkg-dir: No such resource with that id
    thanks a lot
    Edited by: 812290 on 17-Nov-2010 19:14

    I think the implication of the docs here http://docs.sun.com/app/docs/doc/817-1592/z.conf.start-29?l=all&a=view is that inherit-pkg-dir is not the default, so you prob haven't inherited that dir.
    You only need to use 'remove' if you have used inherit... and changed your mind.
    You can check the cfg by
    cat /etc/zones/<zone_name>.xml
    OR
    zonecfg -z <zonename> export
    which will output the cfg to stdout
    Cheers
    Chris

  • Solaris zones with whole root

    Hi,
    i was trying to configure a solaris whole root zone, but when i try to install , it gave an error , sanity check error.
    solaris# zonecfg -z solaris8
    solaris8: No such zone configured
    Use 'create' to begin configuring a new zone.
    zonecfg:solaris8-system> create -tb SUNWsolaris8
    zonecfg:solaris8> set zonepath=/export/solaris8
    zonecfg:solaris8> add net
    zonecfg:solaris8:net> set address=172.21.7.155/24
    zonecfg:solaris8:net> set physical=ce0
    zonecfg:solaris8:net> end
    zonecfg:solaris8> commit
    zonecfg:solaris8> exit
    then i use my archive file to install the image.
    zoneadm -z solaris8 install -u -a /export/solaris8.flar
    i need to have a whole root partiiton for the non-global zone. i dont want to share the global zone root partition on my container.
    what iam missing here
    thanks,

    Can you provide a copy/paste of the exact screen output please.
    Thanks

  • 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.

  • Why the error "unable to create unique temporary file" ?

    Hi,
    I've created a very simple zone on s10_69. The global zone is a default Solaris install, nothing added. When installing the local zones I get theses error messages:
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/100dpi/fonts.dirMMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/75dpi/fonts.dirNMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/F3bitmaps/fonts.dirOMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/misc/fonts.dirPMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirSMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirUMaypm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/server/etc/OWconfigjha4tm>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/sfw/lib/mozilla/.pkg_update_stampepaybn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/75dpi/fonts.dirgOa4Gn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/F3bitmaps/fonts.dirhOa4Gn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/Type1/fonts.diriOa4Gn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/misc/fonts.dirjOa4Gn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/misc/fonts.alias.alllOa4Gn>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirfGaWoo>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirhGaWoo>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/server/etc/OWconfigL2aqZo>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirgPaW7o>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirhPaW7o>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/xil/config1Faipp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/xil/config2_aWtp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirEhaywp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirGhaywp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirsVaqAp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.diruVaqAp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/bin/wscompilejbaWAp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/bin/wsdeploykbaWAp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/F3/fonts.dirioaqBp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/server/etc/OWconfigLYaaCp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dir10a4Dp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirZAaOEp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dir1AaOEp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirhUaqFp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirjUaqFp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirDNaGGp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirFNaGGp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.diryVaGLp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirAVaGLp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirdtaGMp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirftaGMp>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/100dpi/fonts.dirgZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/75dpi/fonts.dirhZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/F3/fonts.diriZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/Speedo/fonts.dirjZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/75dpi/fonts.alias.alllZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/F3/fonts.alias.allmZaWKq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/encodings/encodings.dirlqaGLq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/lib/X11/fonts/TrueType/ttmap/ttmaps.dirnqaGLq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/asadminsTaGNq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/pointbase/tools/serveroption/startcommander.shbHayPq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/pointbase/tools/serveroption/startconsole.shcHayPq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/pointbase/tools/serveroption/startserver.shdHayPq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/pointbase/tools/serveroption/stopserver.sheHayPq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/openwin/server/etc/OWconfigt2aGYq>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/appclienta2aOyr>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/asantb2aOyr>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/capture-schemac2aOyr>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/deploytoold2aOyr>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/jspce2aOyr>
    pkgadd: ERROR: unable to create unique temporary file </zones/zone2/root/usr/appserver/bin/package-appclientf2aOyr>and more like these.
    Any ideas why ?
    The files are all there after installation, without the temporary names. So it doesn't seem to be a big problem...
    Thanks,
    Vlad.

    I don't have the bug number handy but I'm quite certain this was
    resolved in one of the post-s10_69 builds. Please download the
    official Solaris 10 initial release and by all means, let us know if you
    continue to see this issue during zone installation.

Maybe you are looking for