zone creation failed

First of all I am new to Solaris platform and I am trying to create zones in my Solaris box. I am using the zonemgr script that is available at BigAdmin.

Here is my command to create a zone:

./zonemgr -a add -n webtest1-1 -P "password" -I 192.168.0.1 -t w -s lock -R /root -C /etc/ssh/sshd_config -C /etc/profile -C /etc/resolv.conf -S ssh -z /usr/local/zones

Preparing to install zone <webtest1-1>.

Creating list of files to copy from the global zone.

Copying <190480> files to the zone.

Initializing zone product registry.

Determining zone package initialization order.

Preparing to initialize <1545> packages on the zone.

Initialized <1545> packages on zone.

Zone <webtest1-1> is initialized.

Installation of these packages generated errors: <SUNWcakr SUNWcart200 SUNWckr SUNWcnetr SUNWcsl SUNWcsr SUNWcsu SUNWcsd SUNWtftpr SUNWdtdmr SUNWib SUNWjhrt SUNWmdb SUNWmdbr SUNWhea SUNWcslr SUNWmdr SUNWarcr SUNWintgige SUNWipfr SUNWipfu SUNWjhdev SUNWkey SUNWdfbh SUNWdtrc SUNWdtrp SUNWmddr SUNWftdur>

Installation of these packages generated warnings: <SUNWgnome-a11y-libs-share>

The file </usr/local/zones/webtest1-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.

zoneadm: zone 'webtest1-1': WARNING: bge0:1: no matching subnet found in netmasks(4) for 192.168.0.1; using default of 255.255.0.0.

zoneadm: zone 'webtest1-1': mount of /etc/mnttab failed: No such file or directory

zoneadm: zone 'webtest1-1': call to zoneadmd failed

The package errors might be due to the fact that I have recently run an update on my OS using smpatch. Will that have caused the problem? If so how to I rectify the situation? Thanks.

Message was edited by:

rovingeyes

[1859 byte] By [rovingeyes] at [2007-11-26 8:41:02]
# 1
Please to do a `zoneadm -z webtest1-1 verify` to see if there are any problems. For address you can also use the cidr notation and give 192.168.0.1/24 for example.
hspaans at 2007-7-6 22:18:26 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 2

I tried to use the cidr notation but the zonemgr script throws out this error:

Error: The zone ip (192.168.0.1/24) doesn't match the IP address (192.168.0.1) for the host (webtest1-1)

But at this point I am not too worried about it. I ran the verify command and it didn't throw any errors. But when I checked the install log, I see a bunch of package errors a sample of which is here:

pkgadd: ERROR: packaging file </var/sadm/pkg/SUNWcakr/save/pspool/SUNWcakr/pkginfo> is corrupt

file size <3211> expected <3809> actual

Installation of <SUNWcakr> on zone <webtest1-1> failed (internal

error).

No changes were made to the system.

*** package <SUNWcar> successfully installed.

*** package <SUNWcart200> failed to install - interrupted:

pkgadd: ERROR: packaging file </var/sadm/pkg/SUNWcart200/save/pspool/SUNWcart200/pkginfo> is corrupt

file size <2763> expected <3343> actual

Installation of <SUNWcart200> on zone <webtest1-1> failed (internal

error).

No changes were made to the system.

So it seems like packages are corrupt. But what I don't understand is the package corrupt in global zone? And could that be the reason why the zone is not booting?

rovingeyes at 2007-7-6 22:18:26 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 3
See this thread: http://swforum.sun.com/jive/thread.jspa?threadID=75709
kstailey at 2007-7-6 22:18:26 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 4

I think the issue is that before you apply any patches you need to patch the patch tools themselves. I'm guessing that the current recommended patch cluster does this automatically now.

Someone here applied a few patches by hand before I got the recommeded cluster on and now we see this during zone installation:

pkgadd: ERROR: packaging file </var/sadm/pkg/SUNWcakr/save/pspool/SUNWcakr/pkginfo> is corrupt

file size <558> expected <1441> actual

Installation of <SUNWcakr> on zone <zone1> failed (internal error).

No changes were made to the system.

kstailey at 2007-7-6 22:18:26 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 5

We have found several issues

1) smpatch sometimes download corrupted patch packages

2) doing a zoneadm -z <zonename> install can produce errors if the root directory of the zone has permission set to 700 this is due to checkinstall scripts in the packages that inproperly search at the wrong level a work around is to set the permission or the root dir of the zone to 755 during install then you can set it back or in the case of SUNWjhrt and SUNWjhdev remove the check install from the package. SUn found the bug over a year ago and was to do this but it never seem to have made any releases yet.

johnb at 2007-7-6 22:18:26 > top of Java-index,Solaris Operating System,Solaris 10 Features...