Creating a zone

The output from
# zoneadm list -vc
ID NAME STATUS PATH
0 global running /
- psql-zone incomplete /opt/home/srao/psql-zone
I can't delete this zone as posted earlier. Now I tried to configure the same as shown.
# zonecfg -z psql-zone
psql-zone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfgsql-zone> create
zonecfgsql-zone> set zonepath=/opt/home/srao/psql-zone
zonecfgsql-zone> set autoboot=true
zonecfgsql-zone> add fs
zonecfgsql-zone:fs> set dir=/usr/local
zonecfgsql-zone:fs> set special=/opt/local
zonecfgsql-zone:fs> set type=lofs
zonecfgsql-zone:fs> end
zonecfgsql-zone> add net
zonecfgsql-zone:net> set address=206.24.18.143
zonecfgsql-zone:net> set physical=bge0
zonecfgsql-zone:net> end
zonecfgsql-zone> add attr
zonecfgsql-zone:attr> set name=comment
zonecfgsql-zone:attr> set type=string
zonecfgsql-zone:attr> set value="This is my workzone"
zonecfgsql-zone:attr> end
zonecfgsql-zone> verify
zonecfgsql-zone> commit
psql-zone: Problem updating index file
psql-zone: Problem updating index file
zonecfgsql-zone> exit
psql-zone: Problem updating index file
psql-zone: Problem updating index file
Configuration not saved; really quit (y/[n])?
I need this to proceed further to creae two zones and install small databses for testing.
Your help is really appreciated.
Thanks in advance

Hi
Thanks. It is done by deleting the entry in /etc/zones/index.
Now the problem is deleting the directory psql-zone under my home directory which was created during the orientation of the zone. I have tried using rm and rmdir with all options like r,f,p and s. Can you Pl let me know how to delete this directory.

Similar Messages

Creating a Zone with ufs?

Hi all,
When you create a zone though Ops Center does it try and format the file system as ZFS? Can you make a Zone with a UFS?
Thanks,
Shawn

Hi Shawn,
Ops Center can manage existing "brownfield" zones on other filesystems (i.e. UFS)... but any new ones that you have it create will be on ZFS (see here: http://wikis.sun.com/display/EM11gOC1/Creating+Zones)
Regards,
[email protected]

Do we need to create two zones for Two HBA for a host connected with SAN ?

Hi,While creating Zone , Do we need to create two zones for Two HBA for a host connected with SAN ? Or a zone is enough for
a host which having Two HBAs...We have two 9124s for our SAN fabric...
As I found like one zone below, I little bit confused that , if a host having two HBA connected with SAN, should I expect two zones for every Host?
from the zone set, I gave the command show zoneset
zone name SQLSVR-X-NNN_CX4 vsan 1
    pwwn 50:06:NN:NN:NN:NN:NN:NN
    pwwn 50:06:NN:NN:NN:NN:NN:NN
          pwwn 10:00:NN:NN:NN:NN:NN:NN
But I found only one zone for the server's HBA2:by the same time in the fabric I found switches A & B showing the WWNs of those HBAs on its
connected N port...Its not only for this server alone, but for all hosts..Can you help me to clarify on this please..that should we need to create one zone for
one HBA?

if u have two independent fabrics between hosts and storage, i think the below confs are recommended.
Scenario 1: 2 HBAs single port each ( redundancy across HBA / Storage port )
HBA1 - port 0 ---------> Fabric A ----------> Storage port ( FAx/CLx )
HBA2 - port 0 ---------> Fabirc B ----------> Storage port ( FAy/CLy )
Scenario 2: 2 HBAs of dual port each
HBA1 - port 0 -------> Fabric A ---------> Storage port ( FAx/CLx )
HBA2 - port0 ---------> Fabric A ---------> Storage port ( FAs/CLs )
HBA1 - port 1 --------> Fabric A --------> Storage port ( FAy/CLy )
HBA2 - port 1 ---------> Fabric B --------> Storage port ( FAt/CLt )
the zone which is in your output is VSAN 1. if its a production VSAN, Cisco doesn't recomends to use VSAN 1 ( default vsan ) for production.

Java Exception when creating NG zone

Hi,
Im running OC Update 2 on a Sun T3 (Solaris 10 U9).
When attempting to create NG ZOnes from a CDOM I receive the following message after htting <next> to Native, Whole root zone screen:
Java.lang.reflect.UndeclaredThrowableException
After hitting ok I can view the next screen but am unable to see the metadata LUN or any other info.
This is strange as it only occurs from certain CDOM's while I can happily create NG zones from other CDOM's on the same EC/PC.
Any input would be gratefully received.
Thanks.

Thanks Mike,
I had already looked at edelivery but am only able to find the downloads below and cant find the U3 download anywhere.
Not sure why, perhaps its permissions on my account??
Results
Select      Description      Release      Part Number      Updated      # Parts / Size
     Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1 Media Pack for Oracle Solaris on SPARC (64-bit)      12.1.0.1.0      B65576-02      JAN-13-2012      14 /
16G
     Oracle Enterprise Manager Ops Center 11g Release 1 Media Pack      11.1.0.1536.0      B61587-04      JAN-13-2012      12 /
8.9G
     Oracle Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) Media Pack for Oracle Solaris on SPARC (64-bit)      11.1.0.1.0      B59162-05      NOV-04-2011      15 /
15G
     Oracle® Enterprise Manager 10g Release 5 Grid Control (10.2.0.5.0) Media Pack for Sun Solaris SPARC (64-bit)      10.2.0.5.0      B54402-10      NOV-04-2011      14 /
11G
     Oracle Grid Engine Media Pack      6.2.7.0.0      B60064-02      DEC-29-2011      1 /
820M
     Oracle Enterprise Manager Ops Center Virtualization Management Pack Media Pack      2.5.0.0.0      B59409-01      DEC-27-2011      3 /
2.5G
     Oracle Enterprise Manager System Monitoring Plug-Ins & Management Connectors Release 12 Media Pack      n/a      B61612-02      DEC-21-2011      1 /
168M
Total: 7

Newb - creating a zone

I have a movie track called "wedding" I'd like to put on the main menu.
When I drag a video track to the menu it asks me to "create button and track".
I don't want a button. My main menu screen contains graphics. I'd like the user to click on an AREA of the menu screen and then it would invoke the "wedding" movie.
Is there any way of setting up these "areas" or "zones" on the screen where I can click and have it invoke the movie?
Thanks,,
DVD Studio Pro 4 (latest ver)

"I have a movie track called "wedding" I'd like to put on the main menu.
When I drag a video track to the menu it asks me to "create button and track".
I don't want a button. My main menu screen contains graphics. I'd like the user to click on an AREA of the menu screen and then it would invoke the "wedding" movie.
Is there any way of setting up these "areas" or "zones" on the screen where I can click and have it invoke the movie?"
"Invoking a movie" happens when you activate a "button"... where you're getting confused is in the terminology. The default button created by DVDSP if you drag a video track into the Menu and choose "Create Button and Track" is a small video of the track! There are also provisions for changing the size and lettering the "button."
Drag the track in, create the button, then go read the DVDSP manual for how to resize and letter (if desired) the button. It's a bit harder than chewing gum while walking, but only a little bit.

Can't create DNS zones in Server Admin

Hi All,
So, I've run into this strange problem where when configuring the zone files for the DNS server in Server Admin that clicking on the + button doesn't do anything. I've re-installed Tiger Server including reformating the disk and still nothing.
Can anyone tell me where the zone file is kept. It might be better just to make my own unless anyone can tell me why the + button isn't working.
Thanks much!

Definitely better to make your own, if you know how (lots of good google-able docs on this). Using Server Admin for DNS zone files is dicey at best.
BIND config file is located at '/etc/named.conf'
Zone files live in '/var/named/.' Primary zone files are named 'myDomain.com.zone' and secondary files are named 'myDomain.com.bak'
Feel free to email me if you need some default files.
Can anyone tell me where the zone file is kept. It
might be better just to make my own unless anyone can
tell me why the + button isn't working.
iBook G4 Mac OS X (10.4.3)

Opscenter 12c creating new zones on x86 server failing

Asking for some help!!!,
We are in the process of implementing Oracle Cloud Control 12c and of course Opscenter is a piece of it. When using Opscenter to install new zones on Sparc platform all works as expected. When using Opscenter to install new zones on a x86 server the process fails with not much information to go on. Without being too verbose with error messages we found the following in the /var/log/zones/zoneadm.323213129xxxx.ddasdhasdj.install file
Running auto-install: '/usr/bin/auto-install -z ddasdhasdj -Z dsaas7990000000000000dasdasda7777/rpool/ -m /tmp/manifest.xml.dsada -c /var/mnt/virtlibs/312321312890/zone-config-profile.xml
Error: auto-install failed.
Exiting with exit code 255.
===== Completed: /usr/lib/brand/solaris/pkgcreatezone this command is also followed by much of the same command-line qualifiers from above.
I'll will say this, the auto-install failed message is actually coming from line 242 fo the pkgcreatezone script found in /usr/lib/brand/solaris
Anyone with experience or knowledge in the area is greatly appreciated.
Thanks,
Leigh

Thanks for the reply.
As it happens, yesterday, one our guys was working on the machine and rebooted it removing the /system/volatile/install_log so I can't say at this point. I did take a look at the log earlier and can't remember what I saw. I'll have him do another install attempt and let you know what we see.
Leigh

Two physical Ethernet ports: How to create the zone?

Hi,
we have a Solaris 9 system with 2 physical Ethernet ports let's say hme0 (10.10.0.1)
and hme1 (192.168.0.1) which should be virtualized by a Solaris 9 container within our
T5220 server under Solaris 10.
The server interfaces e1000g0 and e1000g1 are configured as 192.168.0.100 respectively
10.10.0.100. Now we want to create the "solaris9" with
# zonecfg -z solaris9
zonecfg:solaris9> add net
zonecfg:solaris9:net> set address=192.168.0.1
zonecfg:solaris9:net> set physical=e1000g0
zonecfg:solaris9:net> set address=10.10.0.1
zonecfg:solaris9:net> set physical=e1000g1
zonecfg:solaris9:net> end
Is this setup for the network correct?
THX, Rainer

Hi Rainer
You are close! To add the second logical interface you add it as a separate 'net' resource. E.g.
# zonecfg -z solaris9
zonecfg:solaris9> add net
zonecfg:solaris9:net> set address=192.168.0.1
zonecfg:solaris9:net> set physical=e1000g0
zonecfg:solaris9:net> end
zonecfg:solaris9> add net
zonecfg:solaris9:net> set address=10.10.0.1
zonecfg:solaris9:net> set physical=e1000g1
zonecfg:solaris9:net> end
zonecfg:solaris9> exitHope this answers your question.
Martin

Need Best Practice for creating BE in ZFS boot environment with zones

Good Afternoon -
I have a Sparc system with ZFS Root File System and Zones. I need to create a BE for whenever we do patching or upgrades to the O/S. I have run into issues when testing booting off of the newBE where the zones did not show up. I tried to go back to the original BE by running the luactivate on it and received errors. I did a fresh install of the O/S from cdrom on a ZFS filesystem. Next ran the following commands to create the zones, and then create the BE, then activate it and boot off of it. Please tell me if there are any steps left out or if the sequence was incorrect.
# zfs create o canmount=noauto rpool/ROOT/S10be/zones
# zfs mount rpool/ROOT/S10be/zones
# zfs create o canmount=noauto rpool/ROOT/s10be/zones/z1
# zfs create o canmount=noauto rpool/ROOT/s10be/zones/z2
# zfs mount rpool/ROOT/s10be/zones/z1
# zfs mount rpool/ROOT/s10be/zones/z2
# chmod 700 /zones/z1
# chmod 700 /zones/z2
# zonecfg z z1
Myzone: No such zone configured
Use create to begin configuring a new zone
Zonecfg:myzone> create
Zonecfg:myzone> set zonepath=/zones/z1
Zonecfg:myzone> verify
Zonecfg:myzone> commit
Zonecfg:myzone>exit
# zonecfg z z2
Myzone: No such zone configured
Use create to begin configuring a new zone
Zonecfg:myzone> create
Zonecfg:myzone> set zonepath=/zones/z2
Zonecfg:myzone> verify
Zonecfg:myzone> commit
Zonecfg:myzone>exit
# zoneadm z z1 install
# zoneadm z z2 install
# zlogin C e 9. z1
# zlogin C e 9. z2
Output from zoneadm list -v:
# zoneadm list -v
ID NAME STATUS PATH BRAND IP
0 global running / native shared
2 z1 running /zones/z1 native shared
4 z2 running /zones/z2 native shared
Now for the BE create:
# lucreate n newBE
# zfs list
rpool/ROOT/newBE 349K 56.7G 5.48G /.alt.tmp.b-vEe.mnt <--showed this same type mount for all f/s
# zfs inherit -r mountpoint rpool/ROOT/newBE
# zfs set mountpoint=/ rpool/ROOT/newBE
# zfs inherit -r mountpoint rpool/ROOT/newBE/var
# zfs set mountpoint=/var rpool/ROOT/newBE/var
# zfs inherit -r mountpoint rpool/ROOT/newBE/zones
# zfs set mountpoint=/zones rpool/ROOT/newBE/zones
and did it for the zones too.
When ran the luactivate newBE - it came up with errors, so again changed the mountpoints. Then rebooted.
Once it came up ran the luactivate newBE again and it completed successfully. Ran the lustatus and got:
# lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
s10s_u8wos_08a yes yes no no -
newBE yes no yes no -
Ran init 0
ok boot -L
picked item two which was newBE
then boot.
Came up - but df showed no zones, zfs list showed no zones and when cd into /zones nothing there.
Please help!
thanks julie

The issue here is that lucreate add's an entry to the vfstab in newBE for the zfs filesystems of the zones. You need to lumount newBE /mnt then edit /mnt/etc/vfstab and remove the entries for any zfs filesystems. Then if you luumount it you can continue. It's my understanding that this has been reported to Sun, and, the fix is in the next release of Solaris.

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

To disable a service for jumpstart/create zone

To disable a service once a system is up a running, "svcadm disable" does the job well.
What would the suggested way of disabling a service before the system is up an running, in order to guarantee a service never runs.
Clarification of this point would be from a finish script when a system is being built using a Jumpstart system (which might traditionally use something like rm /a/etc/rc3.d/S55thing), or when creating a zone (which might use rm /zoneroot/zonename/root/etc/rc3.d/S55thing), either of these not running in the true context of the end system.

I wanted to elaborate a little on Tobin's comments.
Most of the Solaris services come disabled by default, but many of them are also re-enabled by our default profile, generic_open.xml.
Brian, you're on the right track, though -- changing the manifest isn't the right way to disable a service. Manifests we deliver aren't editable -- they'll get overwritten, not preserved on upgrade. You also shouldn't modify the profiles that we ship, as they're also overwritten on upgrade.
So how do you do the disabling, when you don't have a running repository to modify?
The best way is to provide a site-specific profile. You can create your own /var/svc/profile/site.xml which will be applied to the system after the system-supplied profiles (during svc:/system/manifest-import). There you can describe services as enabled or disabled.
Just create /a/var/svc/profile/site.xml during your jumpstart finish script. See the other .xml files in /var/svc/profile for examples of the format.
You can also test your profile on a running system by using "svccfg apply".

Probem in creating Solaris 10 branded zone on Solaris 11.0

Hello,
I'm creating a zone on HP Blade with Solaris 11.0 using VM template Solaris 10u10 (x86).
I haven't /etc/defaultrouter file, my Solaris 11 is 11/11 and not Express version.
The error shows that variable used for temporary directory is lost. It's very strange because I completed 5 installations in the same way without any problem. But two last just are stopping with this error:
./setupSysidcfgStaticIP[50]: America/Montreal/sysidcfg.VL-VM-LD104: cannot create [No such file or directory]
cp: cannot access America/Montreal/sysidcfg.VL-VM-LD104
chmod: WARNING: can't access America/Montreal/sysidcfg.VL-VM-LD104
The "setupSysidcfgStaticIP" script is one of the many in the image which runs the creation of sysidcfg-file for the zone. It has 9 arguments to run:
CONT=$1
ZONEPATH=$2
NIC=$3
IP_ADDR=$4
NETMASK=$5
DEFROUT=$6
PASSWD=$7
TZONE=$8
TMPDIR=$9
The sysidcfg-filename is calculated as SYSIDCFG=$TMPDIR/sysidcfg.$CONT <- here is the error, the $TMPDIR fails
After that the script creates the file and renames it:
/usr/bin/rm -rf $SYSIDCFG
/usr/bin/sed -e s/RzoneR/$CONT/ $_tktHome/conf/sysidcfgStaticIP |\
/usr/bin/sed -e s/RnicR/$NIC/ |\
/usr/bin/sed -e s/RnetmaskR/$NETMASK/ |\
/usr/bin/sed -e s/RdefaultrouterR/$DEFROUT/ |\
/usr/bin/sed -e s/Rip_addrR/$IP_ADDR/ |\
/usr/bin/sed -e s]RtimezoneR]$TZONE] |\
/usr/bin/sed -e s]RpasswdR]$PASSWD] >> $SYSIDCFG
/usr/bin/cp $SYSIDCFG $ZONEPATH/root/etc/sysidcfg
/usr/bin/chmod 777 $SYSIDCFG
The tmpdir is created and used in main script but it fails in the subroutine. I don't understand why it was used before without any problem and now it fails. I spent yesterday about 6 hours to debug it but still don't have any idea how to fix it.
I use the image solaris-10u10-x86.bin .
I cannot use the newer image solaris-10u11-x86.bin (which works perfectly) because it isn't certified for our production and the set of servers needs to be installed with the same patch level.
Any help will be appreciated!
Vlad
Edited by: 919435 on May 24, 2013 5:56 AM

Problem found. To jumpstart last two HP Blades we used the copies of AI templates. When we did it from scratch and re-installed the Solaris 11.0 we have no more errors.

Cannot create solaris 10 zone with flar archive

Hello,
i'm trying to configure a solaris zones with a flar archive of a solaris 10 system.
i've followed the procedure described here : http://www.sun.com/bigadmin/content/submitted/branded_zones_flash.jsp
whenever i try to create a zone and use: set brand=solaris10 the commit will fail with Unknown brand Missing document.
solaris version is Solaris 10 5/08 s10s_u5wos_10 SPARC and i have both the Solaris 8 and Solaris 9 container software installed.
is there another way to install a zone with the native brand or solaris 10 using an archive of some sort?
kind regards,

Thanks,
I've figured as much as using a whole root zone but i still struggle with the configuration of a solaris10 brand and the creation of a zone config with that brand.
I might be bettor of installing the zone without the flar image and try to copy the needed files and applications to the zone.
I only need the solaris10 brand zone to test the flar image so i can use it to restore the system with flar and jumpstart.

Partial Install of base pkgs upon creating Solaris 10 zone

Greetings,
I have this weird situation when attempting to create a zone. Hoping I can get a bit of insight as to a resolution here.
The procedure I follow is:
root@was07:/root
zonecfg -z was07zonewas07zone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:was07zone> create
zonecfg:was07zone> set autoboot=true
zonecfg:was07zone> set zonepath=/was07zone
zonecfg:was07zone> add net
zonecfg:was07zone:net> set address=xxx.xxx.xxx.107
zonecfg:was07zone:net> set physical=ce0
zonecfg:was07zone:net> end
zonecfg:was07zone> info
zonepath: /was07zone
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: xxx.xxx.xxx.107
physical: ce0
zonecfg:was07zone> verify
zonecfg:was07zone> commit
zonecfg:was07zone> exit
root@was07:/root
zoneadm -z was07zone installPreparing to install zone <was07zone>.
Creating list of files to copy from the global zone.
Copying <12701> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <937> packages on the zone.
Initialized <937> packages on zone.
Zone <was07zone> is initialized.
Installation of these packages generated warnings: <SUNWocfd SUNWkvm SUNWcsl SUNWcsr SUNWzlib SUNWgss SUNWopenssl-libraries SUNWsshcu SUNWsshdu SUNWperl584core SUNWperl584usr SUNWesu SUNWlibC SUNWlibms SUNWlexpt SUNWwbsup SUNWswmt SUNWbzip SUNWxwdv SUNWcpp SUNWctpls SUNWtecla SUNWtftp SUNWpr SUNWtls SUNWtnamd SUNWkrbu SUNWtnetc SUNWtnetd SUNWtoo SUNWudaplu SUNWudapltu SUNWudf SUNWnfscu SUNWlxml SUNWocf SUNWgzip SUNWadmlib-sysid SUNWadmap SUNWmdu SUNWadmc SUNWbip SUNWrcmdc SUNWrcmds SUNWscpu SUNWnisu SUNWfmd SUNWmdb SUNWpiclu SUNWlccom SUNWbsu SUNWnfssu SUNWidnl SUNWluxop SUNWadmfw SUNWinst SUNWipc SUNWipfu SUNWipmi SUNWiscsiu SUNWloc SUNWatfsu SUNWauda SUNWcfcl SUNWcfpl SUNWpcu SUNWpsu SUNWcnsu SUNWjfcau SUNWjss SUNWkey SUNWlibCf SUNWdtrc SUNWlibsasl SUNWllc SUNWlldap SUNWfchba SUNWfcmdb SUNWflexruntime SUNWftpu SUNWpkgcmdsu SUNWqusu SUNWrmodu SUNWroute SUNWsndmu SUNWsshu SUNWter SUNWgcmn SUNWtiu8 SUNWdoc SUNWvolu SUNWadmj SUNWwbapi SUNWaudit SUNWjsnmp SUNWwbcou SUNWjhrt SUNWwbpro SUNWxcu4 SUNWxcu6 SUNWeurf SUNWmgapp SUNWpmu SUNWowbcp SUNWlxsl SUNWzip SUNWsmbau SUNWscplp SUNWpool SUNWzoneu SUNWcpcu SUNW1251f SUNWGlib SUNWGtku SUNWTcl SUNWfruid SUNWfruip SUNWTk SUNWimagick SUNWbash SUNWpsutils SUNWa2psu SUNWbcp SUNWgsfot SUNWgsfst SUNWhpijs SUNWgimpprint SUNWgscr SUNWrsg SUNWgssdh SUNWgtar SUNWhiu8 SUNWhmdu SUNWiniu8 SUNWpapi SUNWippcore SUNWislcc SUNWisolc SUNWaudf SUNWciu8 SUNWjiu8 SUNWkiu8 SUNWbart SUNWbind SUNWgccruntime SUNWjcom SUNWppm SUNWpsf SUNWctlu SUNWjib SUNWffiltersu SUNWsmapi SUNWmdau SUNWfppd SUNWfss SUNWmibii SUNWsasnm SUNWsadmi SUNWmlib SUNWggrp SUNWntpu SUNWopenssl-commands SUNWpamsc SUNWpcsclite SUNWpsm-lpd SUNWqosu SUNWrcapu SUNWrmwbu SUNWscbcp SUNWscmhdlr SUNWslpu SUNWsmagt SUNWsmbac SUNWsmcmd SUNWtcatu SUNWtcpd SUNWprd SUNWtcsh SUNWpl5u SUNWtexi SUNWtlsd SUNWtlsu SUNWtnfc SUNWtnfd SUNWucbt SUNWugenu SUNWusbu SUNWwbdev SUNWwbdoc SUNWwbmc SUNWwebminu SUNWwgetu SUNWsprot SUNWxcu4t SUNWxsrt SUNWxrgrt SUNWxrpcrt SUNWmga SUNWrmui SUNWsadml SUNWypu SUNWzebrau SUNWzsh SUNW1394h SUNWaccu SUNWgpch SUNWpstl SUNWhea SUNWant SUNWapch2u SUNWapch2d SUNWapchu SUNWapchd SUNWbtool SUNWapct SUNWarc SUNWdclnt SUNWdhcsu SUNWdhcm SUNWipplu SUNWiqfs SUNWiquc SUNWiqum SUNWiqdoc SUNWladm SUNWiqjx SUNWfsmgtu SUNWdmgtu SUNWlvma SUNWlvmg SUNWiqu SUNWjhdev SUNWjato SUNWmctag SUNWmcon SUNWast SUNWpprou SUNWaudh SUNWbinutils SUNWbison SUNWbnuu SUNWcdrw SUNWjatodoc SUNWjatodmo SUNWjaxp SUNWcstl SUNWjhdem SUNWdfbh SUNWdhcsb SUNWdpl SUNWkdcu SUNWless SUNWlibm SUNWlibusb SUNWlibusbugen SUNWfac SUNWmcos SUNWflexlex SUNWmcosx SUNWmdbdm SUNWmddr SUNWftduu SUNWgcc SUNWmipu SUNWmkcd SUNWmlibe SUNWmlibh SUNWgm4 SUNWgmake SUNWmysqlu SUNWmysqlt SUNWncau SUNWncft SUNWocfh SUNWopenssl-include SUNWopenssl-man SUNWosdem SUNWpcsclite-devel SUNWpdu SUNWpiclh SUNWpl5v SUNWpl5p SUNWpmgr SUNWpppd SUNWpppdu SUNWpppdt SUNWpppg SUNWppro-plugin-sunos-base SUNWrpm SUNWrsm SUNWseru SUNWserweb SUNWsfdoc SUNWsfinf SUNWsfman SUNWsfwdemo SUNWsfwhea SUNWsmdoc SUNWspnego SUNWsra SUNWsrh SUNWcsu>
The file </was07zone/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
All of the errors in the above log look like this:
*** package <SUNWcsr> installed with warnings:
pkgadd: ERROR: unable to create package object </was07zone/root/usr>.
unable to fix attributes
Installation of <SUNWcsr> on zone <was07zone> partially failed.
I have performed this procedure on 8 identical machines in the past week with no problems, except this one.
uname -aSunOS was07 5.10 Generic_118822-23 sun4u sparc SUNW,Sun-Fire-V440
cat /etc/releaseSolaris 10 3/05 s10_74L2a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 22 January 2005
Now I can finish the the install and boot the zone just fine, but those packages are listed as partially installed, thusly when they are a prereq for any application, the application install fails with dependancy issues. If I try to install those pkgs, the dependancy loop gets very deep.
Plus I know that this isnt the expected results of my command chain above.
TIA for any assistance that can be provided.

One cant perform a zoneadm -z was07zone install
if the permissions on the zonepath are other than 700, correct?
/was07zone with permisisons=777
/was07zone must not be group readable.
/was07zone must not be group writable.
/was07zone must not be group executable.
/was07zone must not be world readable.
/was07zone must not be world writable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=755
/was07zone must not be group readable.
/was07zone must not be group executable.
/was07zone must not be world readable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=744
/was07zone must not be group readable.
/was07zone must not be world readable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=711
/was07zone must not be group executable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
I did open up another terminal window while creating the zone.. and /was07zone/root is created with permisisons of 755

Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

Creating a zone

Similar Messages

Maybe you are looking for