Re: [zones-discuss] zone config issues

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Brian
packages are installed in dependency order, ie SUNWcsr always installs 
before any other package that requires it, no matter the ordering of 
them in /var/sadm/pkg. Basically any patch can change the order of the 
packages in /var/sadm/pkg in relation to time stamps etc, so we do need 
to do this in dependency order.
Basically SUNWtnetr has /var/sadm/pkg/SUNWtnetr/install/depend which 
calls out SUNWcsr.


I mv'ed packages in /var/sadm/pkg around and it had no effect on the 
ordering, see /root/var/sadm/system/logs/install_log


it should never change with respect to SUNWcsr really, basically SUNWcsr 
will always install before any other package that calls out a dependency 
installs.


Could I see a log of a failed install, seems some package is installing 
pam.conf without a dependency on SUNWcsr?


But unless the system is corrupted the packages you mention:

SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

all install after SUNWcsr.



what does grep etc/pam.conf /var/sadm/install/contents  say?


Enda

Brian Kolaci wrote:

Well, I finally solved this obscure case.  I think this is a silly
way to determine package ordering and dependencies which can cripple
an installation.  I believe a bug should be filed, but I'm not sure
what to file it against.

Due to a failed patch update, something happened with the on-disk
directory ordering in /var/sadm/pkg.  I found that /etc/pam.conf
is referenced in the packages SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr
SUNWwebminu SUNWman.  Apparently their installation order is based
on the order they're returned by opendir/readdir.  There should be a
dependency on SUNWcsr by all packages that reference /etc/pam.conf
in any class action scripts, since SUNWcsr needs to install it
before any other package can modify it.

So the logic to determine package installation order needs to
be updated to include the above dependency.  What dependency checks
are used to calculate the order?  Is there any "official" order the
packages should be installed in (so that I may rebuild the /var/sadm/pkg
directory to be in the proper order)?


Should you run into this problem, I'll quickly post how I fixed this.

# cd /var/sadm/pkg
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

if SUNWcsr isn't at the top of the list, you're going to have problems.

I fixed it by creating a directory and moving the one at the top of the 
list
into the tmp folder, then mv SUNWcsr to the tmp folder, then mv SUNWcsr 
back

followed by moving the other directory back.

# mkdir tmp
# mv SUNWtnetr tmp
# mv SUNWcsr tmp
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu
SUNWcsr: No such file or directory
SUNWtnetr: No such file or directory
drwxr-xr-x   4 root root 512 Jul 18 15:22 SUNWsshdr
drwxr-xr-x   4 root root 512 Jul 18 15:21 SUNWrcmdr
drwxr-xr-x   4 root root 512 May  3  2005 SUNWwebminu
# mv tmp/SUNWcsr .
# mv tmp/SUNWtnetr .
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

and maybe I just got lucky, but SUNWcsr was now at the top of the list.
All zone creations now work properly and /etc/pam.conf matches the 
global zone.






Brian Kolaci wrote:



Thanks for the reply.
I'm digging through i.pamconf to find out why its not copying the file.
This seems to be the problem.  Its doing the editing, but not the
initial copy of the file. I checked the CLEANUP_FILE and found that
it had logged messages "default entries updated", which means it is
not copying the file which means it already exists.

Perhaps there's some kind of package installation ordering issue.
The i.pamconf script checks for the existence of /etc/pam.conf and
only copies it if it doesn't exist.  If another package gets installed
before SUNWcsr that tries to manipulate /etc/pam.conf and actually
creates it, then the copy will never be done.  This looks like what is
happening.

What order are the packages installed in?  Is there a way to adjust
that order to assure that SUNWcsr comes before the other one(s) that
are manipulating the file?  What is the correct order for package 
installation?



Renaud Manus wrote:

SUNWcsr pkgmap defines /etc/pam.conf as a 'e' (editable) type file 
with a class
action script 'pamconf'. In this situation, when you install a new 
zone, when
it comes to install the SUNWcsr package, the class action script will 
just copy

the file from /var/sadm/pkg/SUNWcsr/save/... to [ZONEROOTPATH]/etc.

After that, it's possible that some packages need to modify the pam.conf
(eg. SUNWtnetr), to add new entries for example, then they do so in 
their

postinstall script.

You could find all the files on both systems that manipulate pam.conf 
and compare them.


eg.

# find /var/sadm/pkg/SUNWcsr -type f -exec /usr/xpg4/bin/grep -q 
pam.conf {} \; -print


-- Renaud


Brian Kolaci wrote:


Hi,

I'm still having zone creation issues where my /etc/pam.conf is 
corrupt.


I have 2 machines, one works fine, the other always creates the
zone with a bad /etc/pam.conf.

Re: [zones-discuss] zone config issues

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Brian
Not clear to me why this is happening, my system appears to have correct 
dependencies on SUNWcsr, the only way that I know that this could happen 
is if etc/pam.conf got converted to type "f" by mistake, which does not 
appear to be the case in your failed machine.

or
A package creates pam.conf without a dependency on SUNWcsr.
oe the pspool/SUNWcsr/pkgmap entry for pam.conf is damaged.

what is the pam.conf entry like in
/var/sadm/pkg./SUNWcsr/save/pspool/SUNWcsr/pkgmap  ( is it type e and 
pamconf CAS ? )



Almost looks like the system is somehow corrupted by a patchrm failure.
But that is just a guess without any concrete evidence.
Did you remove any patches ( if so which ones )
Do you have an install_log from a failed zone install, ( in 
/var/sadm/system/logs in the non global zone )


What release and what patches have you applied to the failed system
Brian Kolaci wrote:

Hi Enda,

the grep returns:

/etc/pam.conf e pamconf 0644 root sys 3224 28137 1106348054 SUNWcsr

Yes, there was one of the other packages.  I looked and it appears
it was SUNWkrbu.

Strange but when I mv'd the directories around (at least the way I did),
the order they came back from ls, enough to make it start working again.
My rationale was to look at the directories there, then clear the directory
entry toward the top of the list by moving the directory out of the way,
then moving SUNWcsr back into the package directory (again assuming that
it will be assigned to the first free slot), then move the other directory
back in.  Like I said, it did work, but having that work didn't give a
warm & fuzzy feeling...

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
packages are installed in dependency order, ie SUNWcsr always installs 
before any other package that requires it, no matter the ordering of 
them in /var/sadm/pkg. Basically any patch can change the order of the 
packages in /var/sadm/pkg in relation to time stamps etc, so we do 
need to do this in dependency order.
Basically SUNWtnetr has /var/sadm/pkg/SUNWtnetr/install/depend which 
calls out SUNWcsr.


I mv'ed packages in /var/sadm/pkg around and it had no effect on the 
ordering, see /root/var/sadm/system/logs/install_log


it should never change with respect to SUNWcsr really, basically 
SUNWcsr will always install before any other package that calls out a 
dependency installs.


Could I see a log of a failed install, seems some package is 
installing pam.conf without a dependency on SUNWcsr?


But unless the system is corrupted the packages you mention:

SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

all install after SUNWcsr.



what does grep etc/pam.conf /var/sadm/install/contents  say?


Enda

Brian Kolaci wrote:


Well, I finally solved this obscure case.  I think this is a silly
way to determine package ordering and dependencies which can cripple
an installation.  I believe a bug should be filed, but I'm not sure
what to file it against.

Due to a failed patch update, something happened with the on-disk
directory ordering in /var/sadm/pkg.  I found that /etc/pam.conf
is referenced in the packages SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr
SUNWwebminu SUNWman.  Apparently their installation order is based
on the order they're returned by opendir/readdir.  There should be a
dependency on SUNWcsr by all packages that reference /etc/pam.conf
in any class action scripts, since SUNWcsr needs to install it
before any other package can modify it.

So the logic to determine package installation order needs to
be updated to include the above dependency.  What dependency checks
are used to calculate the order?  Is there any "official" order the
packages should be installed in (so that I may rebuild the /var/sadm/pkg
directory to be in the proper order)?


Should you run into this problem, I'll quickly post how I fixed this.

# cd /var/sadm/pkg
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

if SUNWcsr isn't at the top of the list, you're going to have problems.

I fixed it by creating a directory and moving the one at the top of 
the list
into the tmp folder, then mv SUNWcsr to the tmp folder, then mv 
SUNWcsr back

followed by moving the other directory back.

# mkdir tmp
# mv SUNWtnetr tmp
# mv SUNWcsr tmp
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu
SUNWcsr: No such file or directory
SUNWtnetr: No such file or directory
drwxr-xr-x   4 root root 512 Jul 18 15:22 SUNWsshdr
drwxr-xr-x   4 root root 512 Jul 18 15:21 SUNWrcmdr
drwxr-xr-x   4 root root 512 May  3  2005 SUNWwebminu
# mv tmp/SUNWcsr .
# mv tmp/SUNWtnetr .
# ls -ltd SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

and maybe I just got lucky, but SUNWcsr was now at the top of the list.
All zone creations now work properly and /etc/pam.conf matches the 
global zone.






Brian Kolaci wrote:



Thanks for the reply.
I'm digging through i.pamconf to find out 

Re: [zones-discuss] zone config issues

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
There should be a file 
/var/sadm/pkg/SUNWkrbu/save/pspool/SUNWkrbu/install/depend


which should explicitly call out SUNWcsr.

Coudl you check the /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/pkgmap and 
tell me what the entry is for pam.conf?

I suspect that this entry is corrupt.

Very much suspect that update manager has caused the system to become 
out of sync.


Basically in my experience updatemanager needs a lot of space in /var 
to work. It downloads and uncompresses the patches, which if installing 
a lot of patches can be space consuming, given that the avg patch is 6m 
zipped to start with.



Enda


Brian Kolaci wrote:

I believe that SUNWkrbu is creating the file /etc/pam.conf.
How are the dependencies expressed?  What tells (or should tell)
the system that SUNWcsr must be installed before SUNWkrbu (or
any other package)?

I don't have the logs from the failed update, but this all started
when "updatemanager" failed to update patches on the system.  The
reason for updatemanager failing is clear though (zonepath for the
local zones was on the root filesystem and it filled to 100% and
couldn't boot the zones since the /zones filesystem wasn't mounted).

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
Not clear to me why this is happening, my system appears to have 
correct dependencies on SUNWcsr, the only way that I know that this 
could happen is if etc/pam.conf got converted to type "f" by mistake, 
which does not appear to be the case in your failed machine.

or
A package creates pam.conf without a dependency on SUNWcsr.
oe the pspool/SUNWcsr/pkgmap entry for pam.conf is damaged.

what is the pam.conf entry like in
/var/sadm/pkg./SUNWcsr/save/pspool/SUNWcsr/pkgmap  ( is it type e and 
pamconf CAS ? )



Almost looks like the system is somehow corrupted by a patchrm failure.
But that is just a guess without any concrete evidence.
Did you remove any patches ( if so which ones )
Do you have an install_log from a failed zone install, ( in 
/var/sadm/system/logs in the non global zone )


What release and what patches have you applied to the failed system
Brian Kolaci wrote:


Hi Enda,

the grep returns:

/etc/pam.conf e pamconf 0644 root sys 3224 28137 1106348054 SUNWcsr

Yes, there was one of the other packages.  I looked and it appears
it was SUNWkrbu.

Strange but when I mv'd the directories around (at least the way I did),
the order they came back from ls, enough to make it start working again.
My rationale was to look at the directories there, then clear the 
directory

entry toward the top of the list by moving the directory out of the way,
then moving SUNWcsr back into the package directory (again assuming that
it will be assigned to the first free slot), then move the other 
directory

back in.  Like I said, it did work, but having that work didn't give a
warm & fuzzy feeling...

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
packages are installed in dependency order, ie SUNWcsr always 
installs before any other package that requires it, no matter the 
ordering of them in /var/sadm/pkg. Basically any patch can change 
the order of the packages in /var/sadm/pkg in relation to time 
stamps etc, so we do need to do this in dependency order.
Basically SUNWtnetr has /var/sadm/pkg/SUNWtnetr/install/depend which 
calls out SUNWcsr.


I mv'ed packages in /var/sadm/pkg around and it had no effect on the 
ordering, see /root/var/sadm/system/logs/install_log


it should never change with respect to SUNWcsr really, basically 
SUNWcsr will always install before any other package that calls out 
a dependency installs.


Could I see a log of a failed install, seems some package is 
installing pam.conf without a dependency on SUNWcsr?


But unless the system is corrupted the packages you mention:

SUNWsshdr SUNWtnetr SUNWrcmdr SUNWwebminu

all install after SUNWcsr.



what does grep etc/pam.conf /var/sadm/install/contents  say?


Enda

Brian Kolaci wrote:


Well, I finally solved this obscure case.  I think this is a silly
way to determine package ordering and dependencies which can cripple
an installation.  I believe a bug should be filed, but I'm not sure
what to file it against.

Due to a failed patch update, something happened with the on-disk
directory ordering in /var/sadm/pkg.  I found that /etc/pam.conf
is referenced in the packages SUNWcsr SUNWsshdr SUNWtnetr SUNWrcmdr
SUNWwebminu SUNWman.  Apparently their installation order is based
on the order they're returned by opendir/readdir.  There should be a
dependency on SUNWcsr by all packages that reference /etc/pam.conf
in any class action scripts, since SUNWcsr needs to install it
before any other package can modify it.

So the logic to determine package installation order needs to
be updated to include the above dependency.  What dependency checks
are used to calculate the order?  Is there any "official" order the
packages shou

Re: [zones-discuss] zone config issues

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
I strongly suspect that somehow updatemanager has created some 
inconsistency.


If the old BE list pam.conf as type e pamconf in /var/sadm/install/contents

Then as long as the pspool/pkgmap  is also e pamconf this should just 
install.


Perhaps grep for pam.conf in
/var/sadm/pkg/*/save/pspoo/*/install/*

and see if somehow something else is modifying this file outside of 
those packages that depend on SUNWcsr.


I'm running out of ideas short of a reinstall.

Enda



Brian Kolaci wrote:


Yep, its there.  And the dependency is listed there.

The save/pspool... pkgmap entry is:

1 e pamconf etc/pam.conf 0644 root sys 3224 28137 1106348054

I'm just stunned/amazed that the "directory swapping" actually worked.
But I know that was the only change that fixed the issue.  I had created
a zone right before it, did the directory entry swapping and created 
another

zone right after it, and the second zone was OK.

Also before the directory swapping I used DTrace to confirm that
something else was manipulating /etc/pam.conf in the zone prior
to the pamconf action script.

I still have an old BE that had the issue (with solaris 10 U3 beta 3).
I can boot into that to diagnose this further (just go to single user,
mount it and luactivate it, right?)  Let me know what I should do/try
to find out what is being installed in the zone prior to SUNWcsr.


Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi
There should be a file 
/var/sadm/pkg/SUNWkrbu/save/pspool/SUNWkrbu/install/depend


which should explicitly call out SUNWcsr.

Coudl you check the /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/pkgmap 
and tell me what the entry is for pam.conf?

I suspect that this entry is corrupt.

Very much suspect that update manager has caused the system to become 
out of sync.


Basically in my experience updatemanager needs a lot of space in /var 
to work. It downloads and uncompresses the patches, which if 
installing a lot of patches can be space consuming, given that the avg 
patch is 6m zipped to start with.



Enda


Brian Kolaci wrote:


I believe that SUNWkrbu is creating the file /etc/pam.conf.
How are the dependencies expressed?  What tells (or should tell)
the system that SUNWcsr must be installed before SUNWkrbu (or
any other package)?

I don't have the logs from the failed update, but this all started
when "updatemanager" failed to update patches on the system.  The
reason for updatemanager failing is clear though (zonepath for the
local zones was on the root filesystem and it filled to 100% and
couldn't boot the zones since the /zones filesystem wasn't mounted).

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
Not clear to me why this is happening, my system appears to have 
correct dependencies on SUNWcsr, the only way that I know that this 
could happen is if etc/pam.conf got converted to type "f" by 
mistake, which does not appear to be the case in your failed machine.

or
A package creates pam.conf without a dependency on SUNWcsr.
oe the pspool/SUNWcsr/pkgmap entry for pam.conf is damaged.

what is the pam.conf entry like in
/var/sadm/pkg./SUNWcsr/save/pspool/SUNWcsr/pkgmap  ( is it type e 
and pamconf CAS ? )



Almost looks like the system is somehow corrupted by a patchrm failure.
But that is just a guess without any concrete evidence.
Did you remove any patches ( if so which ones )
Do you have an install_log from a failed zone install, ( in 
/var/sadm/system/logs in the non global zone )


What release and what patches have you applied to the failed system
Brian Kolaci wrote:


Hi Enda,

the grep returns:

/etc/pam.conf e pamconf 0644 root sys 3224 28137 1106348054 SUNWcsr

Yes, there was one of the other packages.  I looked and it appears
it was SUNWkrbu.

Strange but when I mv'd the directories around (at least the way I 
did),
the order they came back from ls, enough to make it start working 
again.
My rationale was to look at the directories there, then clear the 
directory
entry toward the top of the list by moving the directory out of the 
way,
then moving SUNWcsr back into the package directory (again assuming 
that
it will be assigned to the first free slot), then move the other 
directory

back in.  Like I said, it did work, but having that work didn't give a
warm & fuzzy feeling...

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
packages are installed in dependency order, ie SUNWcsr always 
installs before any other package that requires it, no matter the 
ordering of them in /var/sadm/pkg. Basically any patch can change 
the order of the packages in /var/sadm/pkg in relation to time 
stamps etc, so we do need to do this in dependency order.
Basically SUNWtnetr has /var/sadm/pkg/SUNWtnetr/install/depend 
which calls out SUNWcsr.


I mv'ed packages in /var/sadm/pkg around and it had no effect on 
the ordering, see /root/var/sadm/system/logs/install_log


it should never chang

Re: [zones-discuss] zone config issues

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
I'd suggest a reinstall and if this occurs again I will investigate further.
Not a great solution I grant, but I suspect that one or more patches did 
not install/backoff properly.


Enda

Brian Kolaci wrote:

Thats what I was thinking - do a re-install.  I ran broken for a month.
I was at my limit and gave the directory moves a shot.

Prior to that I did updates, and even upgrades (it originally happened
on a U1 install), but continued to fail after the U2 and even U3b3 
upgrades.


I did the grep and only the packages SUNWrcmdr and SUNWtnetr have
postinstalls that reference pam.conf.

But like I said, ever since I did the "move the directory entry of SUNWcsr
before the others", the system has been working again.  But I believe I
can still recreate this on my other BE.

Let me know if you want me to investigate further with the other BE
and I will, otherwise I'll just forget about it and hope it doesn't
happen again...

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi
I strongly suspect that somehow updatemanager has created some 
inconsistency.


If the old BE list pam.conf as type e pamconf in 
/var/sadm/install/contents


Then as long as the pspool/pkgmap  is also e pamconf this should just 
install.


Perhaps grep for pam.conf in
/var/sadm/pkg/*/save/pspoo/*/install/*

and see if somehow something else is modifying this file outside of 
those packages that depend on SUNWcsr.


I'm running out of ideas short of a reinstall.

Enda



Brian Kolaci wrote:



Yep, its there.  And the dependency is listed there.

The save/pspool... pkgmap entry is:

1 e pamconf etc/pam.conf 0644 root sys 3224 28137 1106348054

I'm just stunned/amazed that the "directory swapping" actually worked.
But I know that was the only change that fixed the issue.  I had created
a zone right before it, did the directory entry swapping and created 
another

zone right after it, and the second zone was OK.

Also before the directory swapping I used DTrace to confirm that
something else was manipulating /etc/pam.conf in the zone prior
to the pamconf action script.

I still have an old BE that had the issue (with solaris 10 U3 beta 3).
I can boot into that to diagnose this further (just go to single user,
mount it and luactivate it, right?)  Let me know what I should do/try
to find out what is being installed in the zone prior to SUNWcsr.


Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi
There should be a file 
/var/sadm/pkg/SUNWkrbu/save/pspool/SUNWkrbu/install/depend


which should explicitly call out SUNWcsr.

Coudl you check the /var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/pkgmap 
and tell me what the entry is for pam.conf?

I suspect that this entry is corrupt.

Very much suspect that update manager has caused the system to 
become out of sync.


Basically in my experience updatemanager needs a lot of space in 
/var to work. It downloads and uncompresses the patches, which if 
installing a lot of patches can be space consuming, given that the 
avg patch is 6m zipped to start with.



Enda


Brian Kolaci wrote:


I believe that SUNWkrbu is creating the file /etc/pam.conf.
How are the dependencies expressed?  What tells (or should tell)
the system that SUNWcsr must be installed before SUNWkrbu (or
any other package)?

I don't have the logs from the failed update, but this all started
when "updatemanager" failed to update patches on the system.  The
reason for updatemanager failing is clear though (zonepath for the
local zones was on the root filesystem and it filled to 100% and
couldn't boot the zones since the /zones filesystem wasn't mounted).

Enda O'Connor ( Sun Micro Systems Ireland) wrote:


Hi Brian
Not clear to me why this is happening, my system appears to have 
correct dependencies on SUNWcsr, the only way that I know that 
this could happen is if etc/pam.conf got converted to type "f" by 
mistake, which does not appear to be the case in your failed machine.

or
A package creates pam.conf without a dependency on SUNWcsr.
oe the pspool/SUNWcsr/pkgmap entry for pam.conf is damaged.

what is the pam.conf entry like in
/var/sadm/pkg./SUNWcsr/save/pspool/SUNWcsr/pkgmap  ( is it type e 
and pamconf CAS ? )



Almost looks like the system is somehow corrupted by a patchrm 
failure.

But that is just a guess without any concrete evidence.
Did you remove any patches ( if so which ones )
Do you have an install_log from a failed zone install, ( in 
/var/sadm/system/logs in the non global zone )


What release and what patches have you applied to the failed system
Brian Kolaci wrote:


Hi Enda,

the grep returns:

/etc/pam.conf e pamconf 0644 root sys 3224 28137 1106348054 SUNWcsr

Yes, there was one of the other packages.  I looked and it appears
it was SUNWkrbu.

Strange but when I mv'd the directories around (at least the way 
I did),
the order they came back from ls, enough to make it start working 
again.
My rationale

Re: [zones-discuss] How to get global zone information from non-global zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

prakash wrote:

How to get global zone information from non-global zone,
any coomand or any file to get the information ?
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi
Basically you would access any info re the global zone in the same way 
you would access info on any remote system. This is part of the security 
of zones. If you really needed this info in the local zone, then it 
would have to be provided by the global zone in some form. Be that over 
nfs, or updating a file on a shared mount, that is ro.
But there are no provided tools to do this, as the idea is that they 
global zone is a sperate entity in the same way any remote system would be.


Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: making local zone's /var a separate filesystem

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
I need to investigate this ( is there a CR open for this issue ), but as 
a workaround, it it possible to boot the zones prior to patching 
119254-31, then proceed with patching halted zones.



Enda

Renaud Manus wrote:



You should be able to apply the patch if the local zones
are booted in single-user mode too.

-- Renaud

Andreas Koppenhoefer wrote:


This is a bug in patchadd, 6438808, the fix is
currently under test and should appear on SunSolve shortly, days that 
is.

The patch is
119254-31  ( sparc )



Unfortunately we are not able to apply patch 119254-31 on our servers.
See thread

for a detailed description.
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: making local zone's /var a separate filesystem

[Enda O'Connor ( Sun Micro Systems Ireland)]

Andreas Koppenhoefer wrote:

This is a bug in patchadd, 6438808, the fix is
currently under test and 
should appear on SunSolve shortly, days that is.

The patch is
119254-31  ( sparc )



Unfortunately we are not able to apply patch 119254-31 on our servers.
See thread

for a detailed description.
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


as a workaround,
Try unsetting your locale setting, as this is what caused our systems to 
die, whiel adding 119254-31

What locale settign are you using and I'dd try and replicate this.

But the fix will involve applying the sh to fix sh before patchadd can run.

Enda

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone configuration questions

[Enda O'Connor ( Sun Micro Systems Ireland)]

Dave Bevans wrote:

Hi.

I have a customer using SOL 10 1/06 on a development box, needs to 
control Hardware resource allocation for software licensing.  Wants to 
create container/zone, with a separate /var.  Also wants to know about 
shared packages for creating minimal or sparse zone. Using VxVM and 
Vxfs, needs to know if using vxvm vxfs in non-global zone causes any issues.


Does anyone have any information on this.



resource capping are explained in the following by Menno Lageman
http://www.sun.com/blueprints/0505/819-2679.pdf
and docs.sun.com at
http://docs.sun.com/app/docs/doc/817-1592/6mhahuogv?a=view

Not clear what you meant by shared packages, basically one can create a 
sparse root zone, and that is the smallest zone in terms of 
size/footprint on the system that is possible.
As such with some exception all the global zones package will get 
installed in the non global zone ( at least all ON related will anyway ).
Some application software packages such as JES ( Java Enterprise System) 
will only install onthe global zone and will not get propogated into 
nany future or presnet non global zones, but that is different.


As an aside you coudl perhaps add the zones packages to a minimal 
cluster say SUNWCreq

I can provide a list of packgaes to add.
But you would need to test that that meets all your application needs.


If using a seperate /var please ensure that 119254-31/119155-31 is 
installed, this is the patch utilites patch and is needed to patch 
zopnes with a seperate /var in single user mode.


As for vxfs, it is all good, the only possible issue is upgrade, if the 
zone's rootpath is on the vxfs. Nedd someone to clarify that.


otherwise if the zones data is on vxfs then it will all be ok.

Enda


--
Regards,
Dave
--



Sun Microsystems
Mailstop ubur04-206
1 Network Drive
Burlington, MA  01803

*Dave Bevans - Technical Support Engineer*
*Phone: 800-872-4786
(opt-1), (opt-2), (case #)
* *Email:   david.bevans @Sun.com 


TSC Systems Group-OS / Hours: 6AM - 2PM EST / M - F
*
Submit, Check & Update Cases at the Online Support Center 






___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Newly created zones will not boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jay Morrison wrote:

We are running a number of servers with Solaris 10 installed.  All, but one, 
are running the 6/06 release on SunFire V240s, and the remaining one is now 
running the 11/06 release on a SunBlade 150.  Most of the servers already have 
zones running on them, however, now when we create a new zone on any of the 
machines, we are getting the following error when we try to boot:

# zoneadm -z  boot
zoneadm: zone '': These file-systems are mounted on subdirectories of 
/zones//root:
zoneadm: zone '':   /zones//root/var
zoneadm: zone '': call to zoneadmd failed

The zone was created using the following command:
# zonecfg -z  -f .config

Where .config file looks like:

create
set zonepath=/zones/
set autoboot=true
add net
set physical=
set address=
end
set pool=pool_default
add rctl
set name=zone.cpu-shares
add value (priv=privileged,limit=2,action=none)
end
add fs
set dir=/var
set special=/var/zones//var
set type=lofs
set options=[rw,nodevices]
end
add fs
set dir=/export/home
set special=/export/home/zones//home
set type=lofs
set options=[rw,nodevices]
end
add fs
set dir=/usr/local/etc
set special=/zones//usr/local/etc
set type=lofs
set options=[rw,nodevices]
end
verify
commit
exit

Any thoughts and/or suggestions would be greatly appreciated.

Thanks,
Jay Morrison
UNIX System Administrator
Software Unit
NY State Education Department
(518) 474-3703
[EMAIL PROTECTED]
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


add fs
 set dir=/var
 set special=/var/zones//var
 set type=lofs
 set options=[rw,nodevices]
end

So you are setting the non global zones /var to be a sub dir of the 
global zones /var


This is not allowed as such, perhaps if special was not a subdir of 
global /var/ itself, but on someother data store ie /export/zones/...
What are you trying to achieve with this setup and perhaps we can 
provide an answer


Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone configuration questions

[Enda O'Connor ( Sun Micro Systems Ireland)]

Steve Zinck wrote:



On 1/9/07, *Dave Bevans* <[EMAIL PROTECTED] 
> wrote:


I have a customer using SOL 10 1/06 on a development box, needs to
control Hardware resource allocation for software licensing.  Wants
to create container/zone, with a separate /var.  Also wants to know
about shared packages for creating minimal or sparse zone. Using
VxVM and Vxfs, needs

to know if using vxvm vxfs in non-global zone causes any issues.

Does anyone have any information on this.


I can't speak to the VxVM / Vxfs but creating a sparse zone is as simple 
as using 'create -b' instead of the usual 'create' in zonecfg. 


zonecfg creates sparse by default.
the -b is only for whole root zone creation, effectively -b says create 
a blank configuration, such that it does not have the default inherited 
pkg dirs.

so create -b will always give a whole root zone.

Enda




Take a look at 
http://docs.sun.com/app/docs/doc/819-2450/6mhahuokl?a=view for resource 
capping.  We use it for software (Oracle) licensing reasons as well, to 
limit a particular zone to 4 CPUs.


Steve




___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Newly created zones will not boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jay Morrison wrote:
This method has worked for us in the past (with the zones that we've created prior to the original problem) - the reason we are put the zone's /var in /var/zones//var is to keep the /zones filesystem from filling up with log files in case something on the server goes awry.  


FYI, we have used the following as a guide for splitting out a zone's /var:
http://www2.petervg.nl/cgi-bin/docs.cgi?a=read&doc=186

Thanks,
Jay Morrison
UNIX System Administrator
Software Unit
NY State Education Department
(518) 474-3703
[EMAIL PROTECTED]
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


Hmm, so I was wrong, what was the original problem you mention above, 
from looking at the code on opensolaris, it appears that a mount point 
for /zones//root/var is already in place in the zone.



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Newly created zones will not boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jay Morrison wrote:

UPDATE:
We created another zone on one of our test servers but this time watched df -Z to see 
what was actually being mounted during the zonadm -z  install.  It 
turns out that everything comes up as a LOFS mount during the installation, and the 
appropriate files are copied to their respective places.  Then, when the installation 
is complete, all of the LOFS are unmounted - all except the zone's /var filesystem.

Hopefully this will spark some ideas.  


Thanks,
Jay Morrison
UNIX System Administrator
Software Unit
NY State Education Department
(518) 474-3703
[EMAIL PROTECTED]
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi
I tried to reproduce and have not been successful,
what is the global zones /var, is it on a different disk or slice etc.
Could I get some idea of /etc/mnttab entries

You say this worked fine then stopped working, any idea what patches 
were installed,
on the 11/06 what patches are installed, did this work on 11/06 and if 
so what software was installed post it working.



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] DST patch on a whole root zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Bill Casale wrote:
How do you update the DST patch on a whole root zone? Patch # 122032-03 
has been applied to the global zone but it does not appear to have been

passed to the non global zone. On the global zone the time stamps on
the files included in that patch are changed. On the non global zone
the files have not been updated. When attempting to patch the non
global zone directly a failure occurs:

Patch 122032-03 is for global zone only - cannot be installed on 
non-global zone.



Thanks in advance.

Bill



___
zones-discuss mailing list
zones-discuss@opensolaris.org


Hi Bill

on my FCS system with one whole root and one sparse root zone
plus the latest patch utilties patch added

I added 122032-03, which has the following pkgmap excerpt:

...
1 f none usr/share/lib/zoneinfo/Africa/Bamako 0644 root bin 95 4581 
1167290851

usr/share/lib/zoneinfo/Africa/Timbuktu=../../../../../usr/share/lib/zoneinfo/Africa/Bamako



After patchadd, my global zone has
# ls -li /usr/share/lib/zoneinfo/Africa/Bamako 
/usr/share/lib/zoneinfo/Africa/Timbuktu
   847 -rw-r--r--   2 root bin   95 Dec 28 07:27 
/usr/share/lib/zoneinfo/Africa/Bamako
   847 -rw-r--r--   2 root bin   95 Dec 28 07:27 
/usr/share/lib/zoneinfo/Africa/Timbuktu

#
# zlogin whole-4
[Connected to zone 'whole-4' pts/3]
Last login: Tue Jan 30 14:36:20 on pts/3
Sun Microsystems Inc.   SunOS 5.10  Generic January 2005
# ls -li /usr/share/lib/zoneinfo/Africa/Bamako 
/usr/share/lib/zoneinfo/Africa/Timbuktu
375312 -rw-r--r--   2 root bin   95 Dec 28 07:27 
/usr/share/lib/zoneinfo/Africa/Bamako
375312 -rw-r--r--   2 root bin   95 Dec 28 07:27 
/usr/share/lib/zoneinfo/Africa/Timbuktu

#


which matches the pkgmap from the patch
# echo "0t1167290851=Y" | adb
2006 Dec 28 07:27:31
#
where 1167290851 is the timestamp from the patch package for this file

Prior to installing this patch I had

# ls -li /usr/share/lib/zoneinfo/Africa/Timbuktu 
usr/share/lib/zoneinfo/Africa/Bamako
373975 -rw-r--r--   1 root bin   73 Jan 21  2005 
/usr/share/lib/zoneinfo/Africa/Timbuktu
373932 -rw-r--r--   1 root bin   95 Jan 21  2005 
usr/share/lib/zoneinfo/Africa/Bamako

#

So these files are now hardlinks, as opposed to regular files.

Seems the patch applied ok for me.

my zonecfg for whole-4 is
# zonecfg -z whole-4 export
create -b
set zonepath=/export/zones/whole-4
set autoboot=true
add net
set address=129.156.239.149/24
set physical=bge1
end
#

The latest patch utilites patch is

119254-34
119254-34

What rev of these have you got installed?


Enda






___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Strange phenomenon with zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ian Brown wrote:

I must add the following:

ps -z 0 
does NOT hang and is OK.


ps -z 0,3 
DOES hang (again after sched)

and "3" is the id of the zone I created.

Regads,
Ian
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi Ian
Where does the ssh tie into this exactly.
ie are you connecting through ssh to issue the ps etc

haven't seen this before so just curious.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zwho command?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Peter Guthrie wrote:

Is there such a thing as a command I can run in the global zone which will tell 
me who is logged into my non-global zones?

Peter
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


Hi
would zlogin zone-name who

should do
ie
# zlogin pandabear_zone7 who
root   pts/18   Feb 14 13:37(pandabear)
#


Enda

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] OS update and zones question

[Enda O'Connor ( Sun Micro Systems Ireland)]

Russ Petruzzelli wrote:

Zones gurus,

Got this note from our lab tech...
In response to the lab tech's question would we just halt and uninstall the zone, but not 
"delete" it?
Would that allow us to restore it after the installation upgrade?
No not really, basically one would then have to run zoneadm install 
again, to create the zone on the filesystem.
So in efect he is suggesting removing the zone, leaving the zone config, 
then after the upgrade just reinstall the zone again.
But any configuration particular to that zone outside of zonecfg will be 
lost, you would also need to ireinstall the application software that 
was installed in the zone and so on.





Thanks,
Russ

It looks like the upgrade failed. I had to upgrade the firmware but
because of that I
need to get a newer version of the OS installed for the system to
work right. Thehmm, pretty much the same as deleting, as you cannot just reinstate ( as opposed to install )the zone after the upgrade, as it would be out of sync with the global zone at that stage. 
problem seems to be the zones setup. They are causing a package to

fail during the
install so the install is backed out.

The only thing I can suggest is for you to remove the zones you
configured to make
the system not know about them. I'm not saying delete the zones, but
just make the
system not know of them so the upgrade can work without the
condition that the
upgrade work around the zones.

Not clear what is meant by
"I'm not saying delete the zones, but just make the system not know of 
them so the upgrade can work"


If this means fudge the system so that the zones are no longer visible 
by the global zone, then later after the upgrade make them visible 
again, this will not work, as the global zone will be running the later 
OS and the zones will be out of sync, completely unsupported and likely 
to either not work at all, or worse fail badly at some later point.



What is the exact error that causes upgrade to fail, might be able to 
provide better help that way.


once you unintall, then the software in the zone is effectively removed, 
all that is left is the zone configuration after that.


So it might be better to try and fix the issue first, before going down 
the uninstall route.


Enda



Issue Type: Installation
Synopsis : request to upgrade Solaris 10 from U2 to U3

Description :
have the OS on ps-niagara1 upgraded from U2 to U3.
(not a fresh install - we have software installed in zones on the
machine).





___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Patching problem with whole root zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Phil Freund wrote:

When is it necessary to patch whole root zones directly?

I was trying to make sure that I had all of my zones ready to be updated with DST patch 122034-04 so I made sure to install patch utilities patch 119254-34 on all of the global zones. I never thought to install it on the whole root zones separately. 

However, after applying kernel patch 118833-36 and the DST 122034-04 patch  yesterday, I find that although all of the sparse zones show 118833-36 as being applied, none of the whole root zones do. 


In checking out possible reasons, I looked to make sure that 119254-34 was 
installed in the whole root zones and found that it was not. I'm guessing that 
is why 118833-36 doesn't show as installed (and in fact doesn't appear to have 
been installed in the whole root zones based on missing changes in a script in 
/lib/svc/method). However, 122034-04 applied fine to both whole and sparse 
zones and shows up correctly with showrev -p commands.

What am I missing?

TIA,
Phil
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org


Hi
do you have logs for 119254-34 119578-30 and 118833-36 install ( the 
actual patchadd logs from the global zone )


does zlogin  patchadd -p |grep 119254-34
show the patch as being installed.

What OS update etc is this on.

Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone start order

[Enda O'Connor ( Sun Micro Systems Ireland)]

Paul Davis wrote:


Is there a way to control the (auto) start order of zones or better yet 
even dependencies? We have a complete, tiered environment in zones and 
would like to control the start order:


   DB zone -> APP zone -> WEB zone

Thanks,
Paul



___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi
I guess one question is what would happen if these were on seperate 
systems ( ie different global zones as such ).


ie if these were on different systems thne the sart order is going to be 
hard to control anyway. If the various systems are all well integrated, 
the order shoudl not make much of a difference?


But I guess one could write a svc service to boot the various zones in a 
set order, one would then set autoboot to false, as the boot is then 
controlled by a seperate script.
I have attached a sample svc script, one nes to write the exec METHOD 
script though.


svccfg import zones.xml
svcadm enable site/startzones

/lib/svc/method/svc-zones is a good example of how to write the 
start/stop METHODS exec script's, ie one scritp that handles start/stop etc.


Make sure to disable autoboot inthe zonecfg  and also svc:/system/zones

Enda


























___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone in mounted state

[Enda O'Connor ( Sun Micro Systems Ireland)]

Sivakumar Shanmugasundaram wrote:
I have a non-global zone which shows in a 'mounted' state. (Guess, I hit 
on the CR#6217053

Now, I cant boot or halt it.

Any help/workaround is much appreciated.

Siva
___
zones-discuss mailing list
zones-discuss@opensolaris.org


were you adding patches to the system at the time?

run zoneadm -z zonename unmount

then boot the zone and see if the zone boots, check that any 
patches/packages have applied properly, assuming that is what caused the 
issue



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone in mounted state

[Enda O'Connor ( Sun Micro Systems Ireland)]

Sivakumar Shanmugasundaram wrote:

Shivani/Enda,

Thanks.

This worked. 'unmount' is undocumented, is it?
It's an internal zone state used by the patch/packaging tools to manage 
zones that are halted.


Enda, yes. I was doing a pkgadd when I interrupted it. (to run pkgadd -G 
again).

hmm, did the interrupt cause the software to be partially installed?
if so a pkgrm is in order beforehand perhaps.

Enda


Siva


shivani khosa wrote:


Hi Sivakumar,
First unmount the zone and then boot it since booting a mounted zone 
isn't permitted.So, you need to do the following:


zoneadm -z  unmount
zoneadm -z  boot

Regards
Shivani
Sivakumar Shanmugasundaram wrote:

I have a non-global zone which shows in a 'mounted' state. (Guess, I 
hit on the CR#6217053

Now, I cant boot or halt it.

Any help/workaround is much appreciated.

Siva
___
zones-discuss mailing list
zones-discuss@opensolaris.org





___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Re: Re: Re: Patching problem with whole root zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

The Real Warren Belfer wrote:

EndaO'Connor wrote:


The Real Warren Belfer wrote:


Phil Freund wrote:



Hi
119254-32 contains a fix that is vital to patching in single user mode 
with zones ( that is zones that are halted )
it is necessary to install this patch in Multi User Mode ( actually 
patch does not specify any dependency on Single user Mode ) But I will 
clarify this in a patch README note in 119254/119255-36 which will b e 
released in the coming days


In general the patch README specifiies if the patch is reboot 
immediate, reboot required etc.


Enda



Thanks Edna, that helps a lot. But most folks apply patches in bulk,
and if one, like the Kernel patch requires single user, then typically
they all get installed in single user. I have never heard of anyone
breaking up the Rec and Sec cluster into pieces that may be installed
in multi user versus those that cannot.

It seems to me that if a patch _must_ be installed in multi-user, that
fact should be flagged in big letters at the top of the patch README.

I would still like to know if there are any resources that explain
patching systems with zones - or should it just work no matter how
we do it ? :-)

Thanks,


Hi Warren
One option is to boot the system ( global zone ) to single user mode  ( 
SUM ) and then boot eh zones to SUM as well.

so boot global zone to SUM, then
 #zoneadm -z  boot -s
for each zone.

then apply the cluser, once 119254-32 or greater is installed, Single 
User Mode should all just work going forward after that.


basially a zones need to be booted at least once in order for patchadd 
to work,

so say you run
#zoneadm -z zone-test install
 
#patchadd 118833-36
this will fail, you must boot the zone at least once before patching, in 
order to set up the zones device tree etc. Remember that the although 
the zone will show as "running" sysidtool and svc etc all need to run 
after this. if booting a zone for the first time prior to patching, best 
to zlogin -C to determine of zone setup has finished.


zones in a state of "configured" can just be patched as is.
Enda


=wb
___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Re: Re: Re: Patching problem with whole root zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Adding back the zone-discuss list
Possibly something around CR 6522362, which is due to how patchadd in 
119254-34 handles patches that are THISZONEONLY=true, in particular JES 
patches/packages.


I will try and replicate this, what rev of 119254 was installed prior to 34.


Enda



Freund, Phil wrote:
I believe it's JES Identity Suite 2005 Update 4 and so far we installed 
only the Directory Server portion. I intend to update to current soon 
but so far no time! These are T2000 servers running Solaris 10 01/06 
patched at the minimum with the Sol 10 Recommended clusters thru the 
beginning of 11/06.


Phil


-Original Message-
From: Enda O'Connor [mailto:[EMAIL PROTECTED]
Sent: Wed 3/14/2007 11:37 AM
To: Freund, Phil
Subject: Re: [zones-discuss] Re: Re: Re: Re: Patching problem with whole 
root zones


Hi
Looks fine, nothing special really, what version of JES IS have you
installed though?
I take it this is T2000 on 6/06?

Enda


Freund, Phil wrote:
 > I'd have sent this to the list but I've waited for almost an hours and
 > this messages hasn't shown up on it yet.
 >
 > Here's the info for the four whole-root zones:
 >
 > clv1udw11:root> zonecfg -z cludsim001 info
 > zonepath: /zones/cludsim001
 > autoboot: false
 > pool: pool_default
 > fs:
 > dir: /cdrom
 > special: /cdrom
 > raw not specified
 > type: lofs
 > options: [ro,nodevices]
 > net:
 > address: 10.1.51.11
 > physical: e1000g1
 > net:
 > address: 10.20.51.11
 > physical: e1000g5
 > rctl:
 > name: zone.cpu-shares
 > value: (priv=privileged,limit=1,action=none)
 > attr:
 > name: comment
 > type: string
 > value: "Zone cludsim001"
 > clv1udw11:root>
 >
 > clv1udw11:root> zonecfg -z cludsim002 info
 > zonepath: /zones/cludsim002
 > autoboot: false
 > pool: pool_default
 > fs:
 > dir: /cdrom
 > special: /cdrom
 > raw not specified
 > type: lofs
 > options: [ro,nodevices]
 > net:
 > address: 10.1.51.12
 > physical: e1000g7
 > net:
 > address: 10.20.51.12
 > physical: e1000g5
 > rctl:
 > name: zone.cpu-shares
 > value: (priv=privileged,limit=1,action=none)
 > attr:
 > name: comment
 > type: string
 > value: "Zone cludsim002"
 > clv1udw11:root>
 >
 > clv1upw11:root> zonecfg -z clupsim001 info
 > zonepath: /zones/clupsim001
 > autoboot: false
 > pool: pool_default
 > fs:
 > dir: /cdrom
 > special: /cdrom
 > raw not specified
 > type: lofs
 > options: [ro,nodevices]
 > net:
 > address: 10.1.50.19
 > physical: e1000g0
 > net:
 > address: 10.20.50.19
 > physical: e1000g6
 > rctl:
 > name: zone.cpu-shares
 > value: (priv=privileged,limit=1,action=none)
 > attr:
 > name: comment
 > type: string
 > value: "Zone clupsim001"
 > clv1upw11:root>
 >
 >  clv1upw12:root> zonecfg -z clupsim002 info
 > zonepath: /zones/clupsim002
 > autoboot: false
 > pool: pool_default
 > fs:
 > dir: /cdrom
 > special: /cdrom
 > raw not specified
 > type: lofs
 > options: [ro,nodevices]
 > net:
 > address: 10.1.50.49
 > physical: e1000g0
 > net:
 > address: 10.20.50.49
 > physical: e1000g6
 > rctl:
 > name: zone.cpu-shares
 > value: (priv=privileged,limit=1,action=none)
 > attr:
 > name: comment
 > type: string
 > value: "Zone clupsim002"
 > clv1upw12:root>
 >
 > All very consistent. All whole root zones because they all have JES
 > Identity Suite installed on them.
 >
 > Phil
 >
 > -Original Message-
 > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 > Sent: Wednesday, March 14, 2007 9:44 AM
 > To: Freund, Phil
 > Cc: zones-discuss@opensolaris.org
 > Subject: Re: [zones-discuss] Re: Re: Re: Re: Patching problem with whole
 > root zones
 >
 > Phil Freund wrote:
 >  
 >> Enda,

 >>
 >> All of the zones were booted to milestone all when 119254-34 was
 >>
 > applied. Since the patch didn't require a reboot, I did it with all

 > zones and global fully operational.
 >  
 >> Phil
 >> 
 >> 
 >> This message posted from opensolaris.org

 >> ___
 >> zones-discuss mailing list
 >> zones-discuss@opensolaris.org
 >>  
 >>
 > Hi

 > what is the layout of the failing zones, ie zonecfg -z  info
 >
 >
 > Enda
 >  





___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re: Patching for zones with own /usr

[Enda O'Connor ( Sun Micro Systems Ireland)]

mario heimel wrote:

hi steffen,

+1 from me

why you must find the statement, that it is not supported on a mailing list or 
forum and not in the official docs/man pages, and why you can install zones 
with this unsupported setup ?
 
 
This message posted from opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi
But it is supported?
No doc mentions that it is not supported. ( or at least none that I am 
aware of )


ie
patching a zone with
/lib /platform /sbin inherited

will lead to the same result as one with
all four default dirs inherited.

That is patching will work, the /usr in the first will be patched with 
any binaries etc that are relevant to /usr, the patch undo that is 
reated to patchrm the patch will contain the binaries that existed prior 
to patchadd and so on.


If there is a case where this does not exist and the customer was 
running the latest patchadd patch ( 119254/119255, SPARC/x86 
respectively )then it is a bug IMHO.




Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org

[zones-discuss] heads up that 119254-36 119255-36 ( patchadd patch )has been released

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Just a heads up that a new patchadd patch revision has been released to 
SunSolve.


Revision 36 fixes issues with patchadd failing due to a bug in patchadd 
that determined if a patch wazx a global zone only patch "-G" 
functionality released with revision 34.


Also fixes issues with patchrm of certain patches that can lead to zone 
creation failign with errors.


I would advise installing this patch before any further patching 
operations are carried out



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Boot order

[Enda O'Connor ( Sun Micro Systems Ireland)]

Matt Santimore wrote:

All,

Does any one have an idea of how to get my non-global zones (14 of them) 
to boot in a certain order after a global zone reboot.
I'm thinking autoboot false then write my own global zone xml to boot 
them one at a time, but was hoping there is something easier.


Thanks


--Matt




___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi
Please see the following for a pretty comprehensive discussion on this topic
http://www.opensolaris.org/jive/thread.jspa?messageID=99149𘍍

regards
Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Why is mount disabled for branded zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Tirthankar wrote:

Hi,

On my machine (running s01u4_06) I have 3 local zones.

pship2 @ / $ zoneadm list -cv
 ID NAME STATUS PATH   BRANDIP
  0 global   running/   
native   shared
  2 cz2  running/zones/cz2 my_brand  
shared
  5 cz4  running/zones/cz4 native   
shared
  - cz3  installed  /zones/cz3 lx   
shared

pship2 @ / $

cz2 is "my_brand" branded zone

pship2 @ / $ zoneadm -z cz2 mount
zoneadm: zone 'cz2': mount operation is invalid for branded zones.

Why is mount command disallowed for a branded zone ?
I can boot the zone, using the normal zoneadm -z cz2 boot command

Note: The config.xml and platform.xml for "my_brand" is identical to the 
"native" brand except for the brand name.



Hi
mount is an internal state used by the patch/package commands only.
It basically does some mount magic, such that the zone's zone is mounted 
in from the global lofs, plus /dev etc. Not really applicable to a zone 
that is not native as it cannot be patched.



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Why is mount disabled for branded zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Ellard
Thanks for the info, very interesting, some questions

So Brandz zone types that use the patch+packaging commands will be 
running some flavour of Solaris, but not necessarily the same kernel as 
the global, or perhaps different libs/binaries as oppose to kernel.


If so how will they be patched?
ie will they have differenet package versions that those in global zone?


regards
Enda


Ellard Roush wrote:

Hi Enda,

This provides a good opportunity to clear up some misinformation.

The BrandZ "lx" zone type does not use standard patch/package
commands.

There will be BrandZ zone types that do use standard patch/package
commands. The Cluster group is developing now a "cluster" BrandZ
zone type that uses the BrandZ callbacks to enhance a zone.
The "cluster" BrandZ uses standard patch/package commands.
The Zones & BrandZ team in Solaris told us that a BrandZ approach
was the correct way to enhance a zone.

We are now in the middle of correcting these problems.

If you have information about places where this problem
appears, please let us know so that we can fix the problem.

Thanks,
Ellard


Enda O'Connor ( Sun Micro Systems Ireland) wrote:

Tirthankar wrote:

Hi,

On my machine (running s01u4_06) I have 3 local zones.

pship2 @ / $ zoneadm list -cv
 ID NAME STATUS PATH   
BRANDIP
  0 global   running/   
native   shared
  2 cz2  running/zones/cz2 
my_brand  shared
  5 cz4  running/zones/cz4 
native   shared
  - cz3  installed  /zones/cz3 
lx   shared

pship2 @ / $

cz2 is "my_brand" branded zone

pship2 @ / $ zoneadm -z cz2 mount
zoneadm: zone 'cz2': mount operation is invalid for branded zones.

Why is mount command disallowed for a branded zone ?
I can boot the zone, using the normal zoneadm -z cz2 boot command

Note: The config.xml and platform.xml for "my_brand" is identical to 
the "native" brand except for the brand name.



Hi
mount is an internal state used by the patch/package commands only.
It basically does some mount magic, such that the zone's zone is 
mounted in from the global lofs, plus /dev etc. Not really applicable 
to a zone that is not native as it cannot be patched.



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Why is mount disabled for branded zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Bob Netherton wrote:

On Wed, 2007-05-09 at 13:56 +0100, Enda O'Connor ( Sun Micro Systems
Ireland) wrote:


If so how will they be patched?
ie will they have differenet package versions that those in global zone?



non-native zones would have to use non-native methods - specifically
they would have to be patched from within the zone itself.  The
SUNWlx zone does this very nicely today (up2date, yum, ...)

They may have different package versions, they may not have
packages at all (again as in the case of the SUNWlx brand).

Bob


Hi Bob
Thanks, all I need to know, much as I suspected, thanks for clarifying.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Problem with install zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Usually indicates a hardware problem, and a reboot (panic ) was induced 
to try and preserve the system integrity.


To get more info run the FMA commands
what does fmdump ( see fmdump(1m) ) indicate,
run fmdump then fmdump -V on the uuid ie fmdumo -u  -V

what type of system is this as well. ( output from prtdiag perhaps )


I might not be able to help personally, but the info will be of use to 
people on this list


Enda
Wesley Naves de faira wrote:

Hello,
When i going to install the new zone ( zoneadm -z zone01 install ) 
the system reboot. After that appears the following messages in the  
/var/adm/messages, someone how about this error ?

 I am using solaris 10 11/06 patch 118855-36, with zfs in:

NAMESTATE READ WRITE CKSUM
zonas   ONLINE   0 0 0
  mirrorONLINE   0 0 0
c0t2d0  ONLINE   0 0 0
c0t4d0  ONLINE   0 0 0
  mirrorONLINE   0 0 0
c0t3d0  ONLINE   0 0 0
c0t5d0  ONLINE   0 0 0

Error in messages :

May 14 16:09:27 host1 cpu.generic: [ID 369736 kern.warning] WARNING: 
Machine-Check Exception in kernel mode
May 14 16:09:27 aga253distp205 genunix: [ID 843051 kern.info 
] NOTICE: SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, 
VER: 1, SEVERITY: Major

May 14 16:09:27 host1 unix: [ID 836849 kern.notice]
May 14 16:09:27 host1 ^Mpanic[cpu0]/thread=fe805c80:
May 14 16:09:27 host1 genunix: [ID 663943 kern.notice] Unrecoverable 
Machine-Check Exception

May 14 16:09:27 host1 unix: [ID 10 kern.notice]
May 14 16:09:27 host1 genunix: [ID 655072 kern.notice] fe805b20 
unix:cmi_mca_trap+4d ()
May 14 16:09:27 host1 genunix: [ID 655072 kern.notice] fe805b30 
unix:mcetrap+17b ()
May 14 16:09:27 host1 genunix: [ID 655072 kern.notice] fe805c40 
unix:cpu_halt+b2 ()
May 14 16:09:27 host1 genunix: [ID 655072 kern.notice] fe805c60 
unix:idle+89 ()
May 14 16:09:27 host1 genunix: [ID 655072 kern.notice] fe805c70 
unix:thread_start+8 ()

May 14 16:09:27 host1 unix: [ID 10 kern.notice]
May 14 16:09:27 host1 genunix: [ID 672855 kern.notice] syncing file 
systems...

May 14 16:09:27 host1 genunix: [ID 904073 kern.notice]  done
May 14 16:09:28 host1 genunix: [ID 111219 kern.notice] dumping to 
/dev/dsk/c0t0d0s1, offset 860356608, content: kernel
May 14 16:09:28 host1 aac: [ID 831342 kern.warning] WARNING: This system 
contains a scsi hba card/driver that doesn't support softwar
e reset. This means that memory being used by the hba for DMA based 
reads could have been updated after we panic'd.
May 14 16:10:02 host1 genunix: [ID 409368 kern.notice] ^M100% done: 
371082 pages dumped, compression ratio 2.51,

May 14 16:10:02 host1 genunix: [ID 851671 kern.notice] dump succeeded




___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zones and Veritas Volume Manager... easy upgrades/LU usage possible ?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Gael wrote:
With the current thread about upgrades, I was wondering if it would be 
possible to upgrade our currents frames to U4 as I would like to use the 
memory capping capabilities of U4...
the one apparent issue here is that we are using Veritas for BOTH the BE 
and the zones filesystems themselves. It is understood that we will need 
to desencapsulate to upgrade
the boot disks, but are we going to be able to upgrade the zones 
themselves ? Will liveupgrade be able to work with Veritas Volumes 
(using ufs) using SAN. ?
 
Or easier, will the RM upgrades be a simple patch applicable to U2/U3  ?
 
Regards

--
Gael Martinez

http://www.unixwiki.net/




___
zones-discuss mailing list
zones-discuss@opensolaris.org

Hi Gael
I suspect it will be the u4 KU 120011/120012 ( not yet released, but 
will be post u4 )



Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Finding out properties of a directory within a zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Andrew Black wrote:

Is there a way of finding out the status of a particular directory from within a
nonglobal zone.
I would like to find out whether a directory is
 -  inherirted package directory (read only in the zone)
 - zone has its own copy
 - shared with the global zone

Forgive me if I have the wrong terminology - I am new to zones.




___
zones-discuss mailing list
zones-discuss@opensolaris.org



Hi
In the non global zone, you could examine the output from
mount -p

or look at /etc/mnttab

# cat /etc/mnttab
/   /   ufs 
rw,intr,largefiles,logging,xattr,onerror=panic,dev=dc0087   1181900125

/dev/devlofszonedevfs,dev=4640002   1181915583
/lib/liblofsro,nodevices,nosub,dev=dc0080   1181915583
/platform   /platform   lofsro,nodevices,nosub,dev=dc0080 
1181915583

/sbin   /sbin   lofsro,nodevices,nosub,dev=dc0080   1181915583
/usr/usrlofsro,nodevices,nosub,dev=dc0080   1181915583

so /lib, /platform, /sbin and /usr are all lofs mounted ( inherited )

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Migrating ZFS pool with zones from one host to another

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Essentially the zone info must be created on the destination system ( 
this is stored in /etc/zones, so not under zone root )


See step 5 in the second page ( How to Migrate A Non-Global Zone )
http://docs.sun.com/app/docs/doc/819-2450/6n4o5mdga?a=view

other than the the zpool import will handle importing the zpool to the 
new system



Enda

Robert Bailey wrote:
This might help you.  I have some ZFS and some VxFS / VCS examples of 
zone migration.


http://web.mac.com/robert.bailey

Check it out, and let me know if it helps.


On Jun 20, 2007, at 9:50 PM, Hector De Jesus wrote:

I have created a zfs pool and I have installed a zone in the pool. For 
example my pool name is hec pool /hecpool and I have installed my zone 
to the following location /hecpool/zones/heczone. Is there away to 
migrate all of my pool data and zones to another SUN host if my pools 
are created on provisioned storage from a SAN. I have found an 
interesting blog article that discusses this but it does not seem to 
work. I am able to import the pool on another machine, but the zone 
info is not there. zoneadm -z heczone attach or zoneadm -z heczone 
boot do not work. Can anyone help with a set of steps to do a 
migration thanks in advance.


PS. please see this link, these are the steps that i followed to try 
the migration

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6162


This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] patch added in GZ not seen in NGZ

[Enda O'Connor ( Sun Micro Systems Ireland)]

F.V.(Phil)Porcella wrote:
> HI Folks,
> I recently installed a patch in the GZ of my zoned machine, it installed 
> without any problem.
> 
> Sun Microsystems Inc.   SunOS 5.10  Generic January 2005
> -bash-3.00$ patchadd -p|grep 122231
> Patch: 122231-01 Obsoletes: Requires: 121453-02 Incompatibles: Packages: 
> SUNWcctpx
> -bash-3.00$ uname -a
> SunOS sbv120-1 5.10 Generic_125100-08 sun4u sparc SUNW,UltraAX-i2
> -bash-3.00$ zoneadm list -civ
>   ID NAME STATUS PATH
>0 global   running/
>6 CIS2 running/zones/roots/CIS2
> 
> I looked on the NGZ to see if the patch was there also, and it wasnt.
> I tried a reboot of the NGZ and looked again, it still was not there.
> # uptime
>   2:13pm  up 20 min(s),  1 user,  load average: 0.03, 0.03, 0.05
> # uname -a
> SunOS CIS2 5.10 Generic_125100-08 sun4u sparc SUNW,UltraAX-i2
> # patchadd -p |grep 122231-01
> #
> 
> Is this a bug or a feature, or does the patch viewing on the zone, depend on 
> the patch?
> 
> Thanks,
> Phil
>  
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
How did you apply the patch i.e.
in Single mode with zones halted

or were the zones running?

What rev of 119254 was installed when this patch was installed.

Is SUNWcctpx installed in the non global zone?

Do you have the patchadd output for this patch?
Enda

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zones and Dtrace

[Enda O'Connor ( Sun Micro Systems Ireland)]

[EMAIL PROTECTED] wrote:
> On Thu, Jul 12, 2007 at 10:38:56AM -0700, Penelope Cotten wrote:
>> Regarding new features in S10 U4:
>>
>> I neglected to include another new feature.
>>
>> The ability to use Live Upgrade on a system with zones 
>> installed is also a new feature for S10 U4.
> 
> Does it work only with S10 U4 and next releases ?
> Or can I install LU packages (taken from S10 U4) on earlier S10
> releases (with zones installed) and still be able to use the feature ?
You will have to also install the U4 KU when it is released to use this 
feature, I believe.

Enda

> 
> Regards
> przemol
> 
> --
> http://przemol.blogspot.com/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> Kopsnij sie na plaze
> Kliknij 
 http://link.interia.pl/f1af8
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Creating a sparse root zone via a package's postinstall script

[Enda O'Connor ( Sun Micro Systems Ireland)]

Fat Ted wrote:
> Hi,
> 
> Is it possible to create a sparse root zone from within a package's 
> postinstall script?
> I've created a package; and via the postinstall script, I want to create a 
> basic sparse root zone. Despite the postinstall script working fine as a 
> stand alone script (creates zone no problemo), it fails as a "postinstall" 
> script during a pkgadd...
> 
> Error comes out as (from zoneadm ... install):
> 
> ERROR: Unable to acquire zone administration lock for this system; please try 
> again later
> ERROR: cannot create zone boot environment
> zoneadm: zone 'bose-zone': '/usr/lib/lu/lucreatezone' failed with exit code 
> 94.
> 
> (I've tried deleting the /tmp/.ai.pkg.zone.lock-xxx... file, and the zone 
> partially installs, but gives errors for just about every package: 
> "Installation of these packages generated errors:  FJSVvplu SUNWcakr SUNWcar SUNWkvm FJSVhea SUNWjdmk-base SUNWckr SUNWcnetr 
> SUNWcsl SUNWcsr SUNWcsu... and about another 600 :)".
> If you then try and boot, the zone mounts (STATUS = mounted, which was a new 
> one for me, [i]zoneadm -z zone unmount[/i] to cancel this:))
> 
> Any hot tips?
> 
> Cheers!
>  
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
Basically zoneadm install cannot run if pkgadd itself is running in the 
global for the package you are installing, as the package is locked down 
until we finish.

Why are you doing this in a package postinstall script?
Doesn't seem like a suitable place for this kind of work at all, 
basically postinstall is ideally meant to finalise the package install 
for the particular package being installed, not for doing other sysadmin 
work such as creating zones.

Basically even if this worked, and assuming we waited till the zone got 
created before exiting postinstall, pkgadd would run for perhaps half 
hour depending, which would not be good.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zonecfg question

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
What does zonadm -z labv490-01z5 have to say, ie is the zone in a state 
other than installed?

so the complete steps for an installed zone are:
zoneadm list -cv ( just to see zone state )

zoneadm -z labv490-01z5 halt  ( if not in installed state )
zoneadm -z labv490-01z5 uninstall -F
zonecfg -z labv490-01z5 delete -F

if above fails then give the complete output from above commands, 
including the zoneadm list -cv.


Enda


Yanakiev, Vladimir wrote:
> Here is the output:
> 
> [EMAIL PROTECTED] zonecfg -z labv490-01z5 delete -F
> labv490-01z5: Zone state is invalid for the requested operation
> [EMAIL PROTECTED] 
> 
> -Original Message-
> From: Mike Gerdts [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, August 01, 2007 5:30 PM
> To: Yanakiev, Vladimir
> Cc: zones-discuss@opensolaris.org
> Subject: Re: [zones-discuss] zonecfg question
> 
> On 8/1/07, Yanakiev, Vladimir <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] zonecfg -F -z labv490-01z5 delete
>> zonecfg: illegal option -- F
>> usage:  zonecfg help
>> zonecfg -z(interactive)
>> zonecfg -z  
>> zonecfg -z  -f 
>> [EMAIL PROTECTED]
> 
> Try this:
> 
> zonecfg -z labv490-01z5 delete -F
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zonecfg question

[Enda O'Connor ( Sun Micro Systems Ireland)]

Yanakiev, Vladimir wrote:
>  
> Here it is:
> 
> [EMAIL PROTECTED] zoneadm list -cv
>   ID NAME STATUS PATH  
>0 global   running/ 
>1 labv490-01z3 running/export/zones/labv490-01z3/main
>2 labv490-01z2 running/export/zones/labv490-01z2/main
>4 labv490wsz2  running/export/zones/labv490wsz2/main
>5 labv490wsz3  running/export/zones/labv490wsz3/main
>6 labv490-01z1 running/export/zones/labv490-01z1/main
>7 labv490wsz1  running/export/zones/labv490wsz1/main
>8 labv490-01z6 running/export/zones/labv490-01z6/main
>   16 labv490-01z7 running/export/zones/labv490-01z7/main
>   43 labv490-01z4 running/export/zones/labv490-01z4/main
> [EMAIL PROTECTED]
> 
> As you can see, because the index file doesn't have info for the zone,
> zoneadm will report nothing about it!

Ok, wasn't aware of this problem :-)
Any idea on how this occurred, i.e. steps taken to create the zonecfg 
for the zone without the index file getting updated, is this in a 
veritas cluster by any chance?


Is there an xml file in /etc/zones for labv490-01z5?
If not one could run zonecfg to create one, otherwise the only route I 
can see is to update the index file manually ( need to be careful here ) 
to include a reference to the missing zone, then retry.

But I'd be interested in why this missing entry occurred to start with.

Enda


> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 02, 2007 9:16 AM
> To: Yanakiev, Vladimir
> Cc: Mike Gerdts; zones-discuss@opensolaris.org
> Subject: Re: [zones-discuss] zonecfg question
> 
> Hi
> What does zonadm -z labv490-01z5 have to say, ie is the zone in a state 
> other than installed?
> 
> so the complete steps for an installed zone are:
> zoneadm list -cv ( just to see zone state )
> 
> zoneadm -z labv490-01z5 halt  ( if not in installed state )
> zoneadm -z labv490-01z5 uninstall -F
> zonecfg -z labv490-01z5 delete -F
> 
> if above fails then give the complete output from above commands, 
> including the zoneadm list -cv.
> 
> 
> Enda
> 
> 
> Yanakiev, Vladimir wrote:
>> Here is the output:
>>
>> [EMAIL PROTECTED] zonecfg -z labv490-01z5 delete -F
>> labv490-01z5: Zone state is invalid for the requested operation
>> [EMAIL PROTECTED] 
>>
>> -Original Message-
>> From: Mike Gerdts [mailto:[EMAIL PROTECTED] 
>> Sent: Wednesday, August 01, 2007 5:30 PM
>> To: Yanakiev, Vladimir
>> Cc: zones-discuss@opensolaris.org
>> Subject: Re: [zones-discuss] zonecfg question
>>
>> On 8/1/07, Yanakiev, Vladimir <[EMAIL PROTECTED]> wrote:
>>> [EMAIL PROTECTED] zonecfg -F -z labv490-01z5 delete
>>> zonecfg: illegal option -- F
>>> usage:  zonecfg help
>>> zonecfg -z(interactive)
>>> zonecfg -z  
>>> zonecfg -z  -f 
>>> [EMAIL PROTECTED]
>> Try this:
>>
>> zonecfg -z labv490-01z5 delete -F
>>
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zonecfg question

[Enda O'Connor ( Sun Micro Systems Ireland)]

Yanakiev, Vladimir wrote:
> That was my first question - I can not figure out how this did happened.
> We have the xml, but the entry in the index file is missing. Maybe, the
> zoneadm -z...delete command got interrupted in the middle?... Fixing the
> problem by deleting the file is obvious, but the second question is,
> isn't it more adequate zonecfg to be able to handle this set problems?
> Isn't it better the -F option to disregard the status (or, the lack of
> it at all)? If we agree that this is not correct action, we have to open
> bug/fix?

hmm, hard to tell what happened I guess.
the zoneadm delete was run was it?
or is this some kind of say veritas cluster env, where the zonecfg did 
not get propogated to the node in question?

I'm not in development, but I'd tend to agree that if such an 
inconsistency is detected, it would be good if we could somehow force 
the cleanup. But I'd let zones dev comment more on that one.

Enda
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, August 02, 2007 9:31 AM
> To: Yanakiev, Vladimir
> Cc: Mike Gerdts; zones-discuss@opensolaris.org
> Subject: Re: [zones-discuss] zonecfg question
> 
> Yanakiev, Vladimir wrote:
>>  
>> Here it is:
>>
>> [EMAIL PROTECTED] zoneadm list -cv
>>   ID NAME STATUS PATH  
>>0 global   running/ 
>>1 labv490-01z3 running/export/zones/labv490-01z3/main
>>2 labv490-01z2 running/export/zones/labv490-01z2/main
>>4 labv490wsz2  running/export/zones/labv490wsz2/main
>>5 labv490wsz3  running/export/zones/labv490wsz3/main
>>6 labv490-01z1 running/export/zones/labv490-01z1/main
>>7 labv490wsz1  running/export/zones/labv490wsz1/main
>>8 labv490-01z6 running/export/zones/labv490-01z6/main
>>   16 labv490-01z7 running/export/zones/labv490-01z7/main
>>   43 labv490-01z4 running/export/zones/labv490-01z4/main
>> [EMAIL PROTECTED]
>>
>> As you can see, because the index file doesn't have info for the zone,
>> zoneadm will report nothing about it!
> 
> Ok, wasn't aware of this problem :-)
> Any idea on how this occurred, i.e. steps taken to create the zonecfg 
> for the zone without the index file getting updated, is this in a 
> veritas cluster by any chance?
> 
> 
> Is there an xml file in /etc/zones for labv490-01z5?
> If not one could run zonecfg to create one, otherwise the only route I 
> can see is to update the index file manually ( need to be careful here )
> 
> to include a reference to the missing zone, then retry.
> 
> But I'd be interested in why this missing entry occurred to start with.
> 
> Enda
> 
> 
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
>> Sent: Thursday, August 02, 2007 9:16 AM
>> To: Yanakiev, Vladimir
>> Cc: Mike Gerdts; zones-discuss@opensolaris.org
>> Subject: Re: [zones-discuss] zonecfg question
>>
>> Hi
>> What does zonadm -z labv490-01z5 have to say, ie is the zone in a
> state 
>> other than installed?
>>
>> so the complete steps for an installed zone are:
>> zoneadm list -cv ( just to see zone state )
>>
>> zoneadm -z labv490-01z5 halt  ( if not in installed state )
>> zoneadm -z labv490-01z5 uninstall -F
>> zonecfg -z labv490-01z5 delete -F
>>
>> if above fails then give the complete output from above commands, 
>> including the zoneadm list -cv.
>>
>>
>> Enda
>>
>>
>> Yanakiev, Vladimir wrote:
>>> Here is the output:
>>>
>>> [EMAIL PROTECTED] zonecfg -z labv490-01z5 delete -F
>>> labv490-01z5: Zone state is invalid for the requested operation
>>> [EMAIL PROTECTED] 
>>>
>>> -Original Message-
>>> From: Mike Gerdts [mailto:[EMAIL PROTECTED] 
>>> Sent: Wednesday, August 01, 2007 5:30 PM
>>> To: Yanakiev, Vladimir
>>> Cc: zones-discuss@opensolaris.org
>>> Subject: Re: [zones-discuss] zonecfg question
>>>
>>> On 8/1/07, Yanakiev, Vladimir <[EMAIL PROTECTED]>
> wrote:
 [EMAIL PROTECTED] zonecfg -F -z labv490-01z5 delete
 zonecfg: illegal option -- F
 usage:  zonecfg help
 zonecfg -z(interactive)
 zonecfg -z  
 zonecfg -z  -f 
 [EMAIL PROTECTED]
>>> Try this:
>>>
>>> zonecfg -z labv490-01z5 delete -F
>>>
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone stuck in shutting_down state

[Enda O'Connor ( Sun Micro Systems Ireland)]

Steve Zinck wrote:
> For future reference, here's an update to my zone hung problem. It 
> reoccurred late last week so I updated my case with Sun with a crash 
> dump.  After analysing it, they reported the following:
> 
> "It appears you are runnning into bug 6570859 "zfs deadlock upon 
> shutdown" which got closed as a duplicate
> of 6569877, there is no offical patch yet. There is an IDR."
> 
> Apparently the patch is part of U4, but since these zones live on ZFS 
> and afaik U4 isn't going to support upgrading zones on ZFS, I'll likely 
> apply the IDR. Perhaps move the zones to UFS.  I'll have to think about it.
> 
If there is no patch, then it's not in u4, and as there is no patch ( I 
checked ), then it will be u5 at the earliest I assume.

BTW you do not have to upgrade to get bug fixes, the official patch will 
apply fine to your system once it releases ( apply latest patch add first ).

But it appears the IDR is your only solution for now, post applying the 
IDR, you will not be able to patch SUNWzfskr package, which means you 
will not be able to apply the U4 KU 120011/120012, without first running 
patchrm on the IDR, as IDR's lock the package to stop further patching 
of the package.

Just so you are aware.

Enda
> Thanks,
> 
> Steve
> 
> On 7/20/07, *Jeff Victor* <[EMAIL PROTECTED] 
> > wrote:
> 
> Hi Steve,
> 
> When you place the call with Sun Service, ask them to compare your
> situation to:
> 
> CR 6547153: GZ should be able to 'halt' a non-global zone (when a
> NGZ process
> is in biowait)
> 
> Steve Zinck wrote:
>  > I've run into the problem of a zone refusing to cleanly shut down
> a few
>  > times now.  It gets stuck in the shutting_down state:
>  >
>  >6 as39 shutting_down  /zones/as39
>  >
>  >
>  > Here's ps -efZ |grep as39 from the global zone:
>  >
>  > as39root   584 1   0   Jun 24 ?   0:00 zsched
>  >   globalroot   575 1   0   Jun 24 ?   0:00
> zoneadmd -z as39
>  > as39  svctag  4914  4890   0- ?   0:00 
>  > as39root  4890 1   0   Jul 04 ?   1:25
>  > /apps/oracle/oas/10.1.3.1/Apache/Apache/bin/httpd -d
>  > /apps/oracle/oas/10.1.3.1/
>  >
>  > I tried to kill -9 4914 and 4890 with no luck.  I tried to preap
> (w/ and
>  > w/o -F) 4914 with no luck.  I've googled and I've seen this
> discussed in
>  > the past but I want to know if there's any new suggestions.  I'm
> going
>  > to open a call with Sun, what information should I gather for them?
>  > halt -d?
>  >
>  > This server is a T2000, S10 11/06:
>  > SunOS gc16 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T200
>  >
>  > This zone is a whole root zone and it lives on a zfs filesystem.
>  >
>  > Thanks,
>  >
>  > Steve
>  >
>  >
>  >
> 
>  >
>  > ___
>  > zones-discuss mailing list
>  > zones-discuss@opensolaris.org 
> 
> --
> --
> 
> Jeff VICTOR  Sun Microsystemsjeff.victor @
> sun.com 
> OS AmbassadorSr. Technical Specialist
> Solaris 10 Zones FAQ:
> http://www.opensolaris.org/os/community/zones/faq
> --
> 
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Accessing CD from a non global zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Andrew Black wrote:
> Hi
> Is there a way of allowing a non global zone to see the CD drive on a 
> machine?
> Failing that, any alternative ways forward, eg creating an image of the CD 
> and sharing this as a file?
> 
> Andrew
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
something like


zonecfg:zone-1>add fs
zonecfg:zone-1:fs>set dir=/cdrom
zonecfg:zone-1:fs>set special=/cdrom
zonecfg:zone-1:fs>set type=lofs
zonecfg:zone-1:fs>set options=[nodevices]
zonecfg:zone-1:fs>end
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone stuck in shutting_down state

[Enda O'Connor ( Sun Micro Systems Ireland)]

Enda O'Connor ( Sun Micro Systems Ireland) wrote:
> Steve Zinck wrote:
>> For future reference, here's an update to my zone hung problem. It 
>> reoccurred late last week so I updated my case with Sun with a crash 
>> dump.  After analysing it, they reported the following:
>>
>> "It appears you are runnning into bug 6570859 "zfs deadlock upon 
>> shutdown" which got closed as a duplicate
>> of 6569877, there is no offical patch yet. There is an IDR."
>>
>> Apparently the patch is part of U4, but since these zones live on ZFS 
>> and afaik U4 isn't going to support upgrading zones on ZFS, I'll 
>> likely apply the IDR. Perhaps move the zones to UFS.  I'll have to 
>> think about it.
>>
> If there is no patch, then it's not in u4, and as there is no patch ( I 
> checked ), then it will be u5 at the earliest I assume.
> 
> BTW you do not have to upgrade to get bug fixes, the official patch will 
> apply fine to your system once it releases ( apply latest patch add 
> first ).
> 
> But it appears the IDR is your only solution for now, post applying the 
> IDR, you will not be able to patch SUNWzfskr package, which means you 
> will not be able to apply the U4 KU 120011/120012, without first running 
> patchrm on the IDR, as IDR's lock the package to stop further patching 
> of the package.
> 
> Just so you are aware.

Ok, so George Wilson clarified things a bit more for me on this one.
The real fix for this is 6447701, which is in u4, the patch will release 
approx mid September ( post official u4 release ).

The patchid's to fiox above will be:
120011-14 ( or higher )  SPARC
120012-14  ( or higher )  X86

These are the u4 KU's and require a lot of patches ( SPARC has 18 
requirements, x86 about the same )

Sorry for any confusion.

Enda

> 
> Enda
>> Thanks,
>>
>> Steve
>>
>> On 7/20/07, *Jeff Victor* <[EMAIL PROTECTED] 
>> <mailto:[EMAIL PROTECTED]>> wrote:
>>
>> Hi Steve,
>>
>> When you place the call with Sun Service, ask them to compare your
>> situation to:
>>
>> CR 6547153: GZ should be able to 'halt' a non-global zone (when a
>> NGZ process
>> is in biowait)
>>
>> Steve Zinck wrote:
>>  > I've run into the problem of a zone refusing to cleanly shut down
>> a few
>>  > times now.  It gets stuck in the shutting_down state:
>>  >
>>  >6 as39 shutting_down  /zones/as39
>>  >
>>  >
>>  > Here's ps -efZ |grep as39 from the global zone:
>>  >
>>  > as39root   584 1   0   Jun 24 ?   0:00 zsched
>>  >   globalroot   575 1   0   Jun 24 ?   0:00
>> zoneadmd -z as39
>>  > as39  svctag  4914  4890   0- ?   0:00 
>> 
>>  > as39root  4890 1   0   Jul 04 ?   1:25
>>  > /apps/oracle/oas/10.1.3.1/Apache/Apache/bin/httpd -d
>>  > /apps/oracle/oas/10.1.3.1/
>>  >
>>  > I tried to kill -9 4914 and 4890 with no luck.  I tried to preap
>> (w/ and
>>  > w/o -F) 4914 with no luck.  I've googled and I've seen this
>> discussed in
>>  > the past but I want to know if there's any new suggestions.  I'm
>> going
>>  > to open a call with Sun, what information should I gather for 
>> them?
>>  > halt -d?
>>  >
>>  > This server is a T2000, S10 11/06:
>>  > SunOS gc16 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T200
>>  >
>>  > This zone is a whole root zone and it lives on a zfs filesystem.
>>  >
>>  > Thanks,
>>  >
>>  > Steve
>>  >
>>  >
>>  >
>> 
>> 
>>  >
>>  > ___
>>  > zones-discuss mailing list
>>  > zones-discuss@opensolaris.org 
>> <mailto:zones-discuss@opensolaris.org>
>>
>> --
>> 
>> -- 
>>
>>
>> Jeff VICTOR  Sun Microsystemsjeff.victor @
>> sun.com <http://sun.com>
>> OS AmbassadorSr. Technical Specialist
>> Solaris 10 Zones FAQ:
>> http://www.opensolaris.org/os/community/zones/faq
>> 
>> -- 
>>
>>
>>
>>
>> 
>>
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
> 
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] trying to login with solaris Ldap client

[Enda O'Connor ( Sun Micro Systems Ireland)]

> <= bdb_equality_candidates: (uid) index_param failed (18)
> conn=76 op=98 SEARCH RESULT tag=101 err=0 nentries=1 text=
> conn=76 op=99 SRCH base="ou=users,dc=tel,dc=uva,dc=es" scope=1 deref=3 
> filter="(&(objectClass=posixAccount)(uid=dpercam))"
> conn=76 op=99 SRCH attr=cn uid uidnumber gidnumber gecos description 
> homedirectory loginshell
> <= bdb_equality_candidates: (uid) index_param failed (18)
> conn=76 op=99 SEARCH RESULT tag=101 err=0 nentries=1 text=
> 
> Does anybody know what could be the problem??? I'm desesperate!
> 
> Thank you very much.
> 
> Daniel Pérez
> 
> _
> MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Looks like a pam issue?

the server is finding the entry (nentries=1)

What have you configured in /etc/pam.conf
read man -s5 pam_ldap to get an idea

so at a guess from your env above
change

 auth required pam_unix_auth.so.1
to

 auth binding pam_unix_auth.so.1 server_policy

for all lines that match and add
 auth required pam_ldap.so.1

once for each srvice name that you changed.


Also add the line
other password required   pam_authtok_store.so.1 server_policy


other than that not too clear what is wrong.
Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Detect pkgs installed with -G?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ihsan Zaghmouth wrote:
> Hi Jeff,
> 
> Here is my 2 cents, after assuming that pkginfo should hold such an 
> information post installation.
> The */var/sadm/pkg//pkginfo* file lists among other info the 
> *SUNW_PKG_ALLZONES*=true | false for the installed package.
> pkginfo should have an option to display that, I tried them all ... in 
> vain !
> 
> if you write a small script, you can display the 
> /var/sadm/pkg//pkginfo, you should be able to distinguish:
> :
> cat /var/sadm/pkg//pkginfo* | *grep SUNW_PKG_ALLZONES, and if:
> 
>1. SUNW_PKG_ALLZONES=true  ... Then installed on all Zones
>2. SUNW_PKG_ALLZONES=false ... *Only Global -G*
> 
> Ihsan
> 
Hi
ALLZONES is not the same as -G
-G is identical in behaviour to SUNW_PKG_THISZONE=true

So if a package does not define any of the zones variables including
SUNW_PKG_THISZONE
Adding said package with pkgadd -G will lead to identical behaviour as 
though the package had
SUNW_PKG_THISZONE=true defined, but it does not cause this variable to 
get defined in the pkginfo, rather a file
/var/sadm/install/gz-only-packages gets populated with this package

Now remember that one could have
SUNWfoo and SUNWfoor, so a simple grep fro SUNWfoo in said file is not 
sufficent, it might match SUNWfoor which is not what is wanted.

Also
pkgparam is what is used to display pkginfo variables

# pkgparam SUNWcsu SUNW_PKG_ALLZONES
true
#

Enda
> Jeff Victor wrote:
>> How can someone learn whether a package was installed in the global zone 
>> *with* -G - or without it?
>>
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
>>   
> 
> -- 
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Patching a machine with local zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ron Halstead wrote:
> When patching a machine with local zones, should the local zones be halted or 
> left running? I can't seem to find a definitive answer.
> 
apply latest patchadd patch
119254 SPARC
119255 x86

Once the latest patch is applies, then either halted or running will work.


One other thing, make sure to run
patchadd -a 
first, -a basically does a dryrun, boots any halted zones etc and does 
dependency checks.
if there are any issues with a zone not being bootable the output should 
clearly indicate this ( examine the output carefully! ), and must be 
remedied prior to running the actual patchadd. Might also catch issues 
where a patch will not apply to one zone out of a list of zones, which 
might also need to be examined depending on the patch etc.


Enda


> ron
>  
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Detect pkgs installed with -G?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Enda O'Connor ( Sun Micro Systems Ireland) wrote:
> Ihsan Zaghmouth wrote:
>> Hi Jeff,
>>
>> Here is my 2 cents, after assuming that pkginfo should hold such an 
>> information post installation.
>> The */var/sadm/pkg//pkginfo* file lists among other info the 
>> *SUNW_PKG_ALLZONES*=true | false for the installed package.
>> pkginfo should have an option to display that, I tried them all ... in 
>> vain !
>>
>> if you write a small script, you can display the 
>> /var/sadm/pkg//pkginfo, you should be able to distinguish:
>> :
>> cat /var/sadm/pkg//pkginfo* | *grep SUNW_PKG_ALLZONES, and if:
>>
>>1. SUNW_PKG_ALLZONES=true  ... Then installed on all Zones
>>2. SUNW_PKG_ALLZONES=false ... *Only Global -G*
just to be clear so there's no confusion:

If a package has
SUNW_PKG_ALLZONES=false
basically it means that the package does not have to be "identical" 
across all the zones, but the default behaviour of pkgadd is to add the 
package  to all available zones ( both global and local ) unless -G was 
specified or SUNW_PKG_THISZONE is true in installing pkginfo, even with 
ALLZONES=false.

So  packages with SUNW_PKG_ALLZONES=false, will actually get installed 
in all the zones by default by calling pkgadd.

The variable that corresponds to -G is SUNW_PKG_THISZONE
see man -s4 pkginfo for a description of the 3 pkginfo variables that 
affect zones

cheers
Enda
>>
>> Ihsan
>>
> Hi
> ALLZONES is not the same as -G
> -G is identical in behaviour to SUNW_PKG_THISZONE=true
> 
> So if a package does not define any of the zones variables including
> SUNW_PKG_THISZONE
> Adding said package with pkgadd -G will lead to identical behaviour as 
> though the package had
> SUNW_PKG_THISZONE=true defined, but it does not cause this variable to 
> get defined in the pkginfo, rather a file
> /var/sadm/install/gz-only-packages gets populated with this package
> 
> Now remember that one could have
> SUNWfoo and SUNWfoor, so a simple grep fro SUNWfoo in said file is not 
> sufficent, it might match SUNWfoor which is not what is wanted.
> 
> Also
> pkgparam is what is used to display pkginfo variables
> 
> # pkgparam SUNWcsu SUNW_PKG_ALLZONES
> true
> #
> 
> Enda
>> Jeff Victor wrote:
>>> How can someone learn whether a package was installed in the global zone 
>>> *with* -G - or without it?
>>>
>>> ___
>>> zones-discuss mailing list
>>> zones-discuss@opensolaris.org
>>>   
>> -- 
>>
>>
>> 
>>
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Patching a machine with local zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Mike Gerdts wrote:
> On 9/6/07, Enda O'Connor ( Sun Micro Systems Ireland)
> <[EMAIL PROTECTED]> wrote:
>> One other thing, make sure to run
>> patchadd -a 
>> first, -a basically does a dryrun, boots any halted zones etc and does
>> dependency checks.
> 
> Hmmm, I've been looking for dryrun support.  A quick look at the man
> page shows why I haven't found it yet.  Is the fact that the -a option
> is not documented a bug or an indication that it is a private feature?
>  I just need to know what to put in the bug report.
it's actually private, but is so useful in terms on zones patching, that 
I just tell all people too run it.
Might log an RFE to get it converted to public as it's hard to get by in 
a zones system without dryrun really.
> 
>> if there are any issues with a zone not being bootable the output should
>> clearly indicate this ( examine the output carefully! ), and must be
> 
> Is any work being done on improving the output of patchadd?  As it is
> today, the output is extremely tedious to read and worse to try to
> parse for automated checks.  I've been silently gnawing on my tongue
> waiting for pdo.c to become available to see what can be done to
> improve it, but the wait is getting to be quite long.
hmm, I agree, it should be improved, I logged quite a few bugs against 
pdo messaging, but overall this really should be improved.

I can log another one and provide some suggested ideas
any suggestions ( as I do not work in dev I cannot gaurantee what will 
or wil not get fixed by the way )

Enda
> 
> Mike
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Patching a machine with local zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ron Halstead wrote:
> Thanks for the quick response. I don't see the -a option to patchadd. 
> patchadd -a gives a usage message. Man patchadd doesn't show a -a option. The 
> 119254-38 patch is installed.
> 
> ron
>  
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
it's private ( but in my opinion vital to patching zones. RFE logged to 
get it moved to public hopefully )
patchadd -a will give usage
patchadd -a 119254-42 will give dryrun output :-)
it's there since fcs I believe


Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] S10 U3 Live Upgrade with zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Richard Weatherley wrote:
> Hi Enda
> 
> What is the ETA for 119255 (> -42) that addresses the problems with deferred 
> activation patching for ZFS and VxFS when trying to install 120012-14?
> 
> Thanks.
>  
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
I will try and get some preliminary dates ( it will not in 43 is all I 
can say )
I have added some people how are working on resolving these issues ( 
well it one issue really )

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] S10 U3 Live Upgrade with zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Enda O'Connor ( Sun Micro Systems Ireland) wrote:
> Richard Weatherley wrote:
>> Hi Enda
>>
>> What is the ETA for 119255 (> -42) that addresses the problems with deferred 
>> activation patching for ZFS and VxFS when trying to install 120012-14?
>>
>> Thanks.
>>  
>>  
>> This message posted from opensolaris.org
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
> Hi
> I will try and get some preliminary dates ( it will not in 43 is all I 
> can say )
> I have added some people how are working on resolving these issues ( 
> well it one issue really )
> 
> Enda
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
Also meant to say, sorry for the hassle incurred here, but we are 
working towards getting a fix for this out soon.


Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Dan Price wrote:
> On Tue 02 Oct 2007 at 07:35AM, Konstantin Gremliza wrote:
>>
>> Someone earlier stated that this was also broken in SXDE-- as far as
>> I know that is *not* the case.  One of the reasons this has been a
>> troublesome area is that in Nevada the /dev zones implementation is
>> radically different from S10, due to the existence of the "devnames"
>> project in Nevada.  Hence the S10 and Nevada code is pretty in this
>> area.
>>
>> -dp
>>
>>
>> Before I posted this to [zone-discuss] I tried again on SXDE 09/07, and the
>> same problem occured.
>> Adding a device match will not create any device files in ZONEPATH/dev.
> 
> Konstantin, we'll go back and retest SXDE 9/07, although at present we
> don't have a bug for this problem open against SXDE.  As I said, the
> code is basically completely different in that area between SXDE and
> S10, so it would have to be a new and different bug.
> 
> My desktop is a SPARC box running build 72 (which AFAIK is SXDE 9/07)
> and I don't see this there; this is an example of adding, then
> removing a pseudo device in a basic test:
>   
>   # uname -a 
>   SunOS snowdog 5.11 snv_72 sun4u sparc SUNW,A70
>   # ls -l /aux/foo/root/dev/lockstat
>   /aux/foo/root/dev/lockstat: No such file or directory
>   # zonecfg -z foo 'add device; set match=/dev/lockstat; end'
>   # zoneadm -z foo reboot
>   # ls -l /aux/foo/root/dev/lockstat
>   crw-r--r--   1 root sys   89,  0 Oct  3 02:55 
> /aux/foo/root/dev/lockstat
>   # zonecfg -z foo 'remove device match=/dev/lockstat'
>   # zoneadm -z foo reboot
>   # ls -l /aux/foo/root/dev/lockstat
>   /aux/foo/root/dev/lockstat: No such file or directory
> 
> (Please note that I'm not advising that anyone add /dev/lockstat to
> their zone; I simply used it as a test case).
> 
> Perhaps you could post your SXDE test case?
> 
> -dp
> 
> - 
> Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - 
> blogs.sun.com/dp
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
I tried build 74,
add device
set match=/dev/dsk/c0t0d0s7
end
add device
set match=/dev/rdsk/c0t0d0s7
end

rebooted zone and device is there ( verified it wasn't before hand )
We need the user case that fails.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jerry Jelinek wrote:
> Enda O'Connor ( Sun Micro Systems Ireland) wrote:
>> I tried build 74,
>> add device
>> set match=/dev/dsk/c0t0d0s7
>> end
>> add device
>> set match=/dev/rdsk/c0t0d0s7
>> end
>>
>> rebooted zone and device is there ( verified it wasn't before hand )
>> We need the user case that fails.
> 
> Enda,
> 
> I thought the original email used a wildcard match like this:
> 
> set match=/dev/*dsk/c1t15d0s*
> 
> I just tried that on build 74 and it worked fine though, so I agree
> that we need more info.
> 
> Jerry
Hi Jerry
hadn't spotted the wildcard :-)
but it does appear to work non the less.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] /dev/ttyp* to non-global zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Bangalore, Suresh wrote:
> Hi Gurus
>  
> We have a non-global zone which is currently configured, installed and 
> running.
> Now Customer wants to add /dev/ttyp* to the non-global zone.
>  
> Tried adding to the zonecfg using adding
> device
> match: /dev/ttyp*
>  
> and then rebooted the zone. This doesn't work.
Hi
It should work, what is your customer running ( 8/07 has a problem with 
adding devices, or systems running 120012-14/120011-14 )

Also why are they doing this, adding one half of the pseudo teminal to a 
non-global zone?


Enda
> Is there any way to configure this without uninstalling and reinstalling 
> the zone again.
>  
> Thanks
> Suresh
> 
> 
> This e-mail and any attachments may contain confidential information 
> that is intended solely for the use of the intended recipient and may be 
> subject to copyright. If you receive this e-mail in error, please notify 
> the sender immediately and delete the e-mail and its attachments from 
> your system. You must not disclose, copy or use any part of this e-mail 
> if you are not the intended recipient. Any opinion expressed in this 
> e-mail and any attachments is not an opinion of RailCorp unless stated 
> or apparent from its content. RailCorp is not responsible for any 
> unauthorised alterations to this e-mail or any attachments. RailCorp 
> will not incur any liability resulting directly or indirectly as a 
> result of the recipient accessing any of the attached files that may 
> contain a virus.
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] troubleshooting zone boot issues - failed with exit code 32

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jerry Kemp wrote:
> I have a Sun T2000 running Solaris 10u2, all UFS file systems that has 
> been in place for several months.  This morning during a reboot, I had a 
> zone that would not come back up.  It failed to boot due to an inability 
> to mount /svc with an error of "failed with exit code 32".
> 
> I did many Yahoo and Google searches and also looked at the most recent 
> "Solaris Containers - Resource Management and Solaris Zones" guide that 
> was just released this summer.  I did see that several people has 
> encountered this issue, but did not find any resolutions.
> 
> Posted below are some specifics about the zone in question.  tech3 is 
> the global zone and tech10 is the zone with booting problems.  The 
> "zoneadm" that shows the error had to be recreated from memory as I 
> needed to get a work-around in place and did not get a capture of the 
> error, but the error code is accurate.
> 
> Where can I research this error code in more detail?
> 
> TIA,
> 
> Jerry K
> 
> 
> 
> 
> -
> tech3 / 170 # uname -a
> 
> SunOS tech3 5.10 Generic_118833-18 sun4v sparc SUNW,Sun-Fire-T200
> 
> tech3 / 171 # zonecfg -z tech10 info
> zonepath: /export/zones/tech10
> autoboot: false
> pool:
> inherit-pkg-dir:
>  dir: /lib
> inherit-pkg-dir:
>  dir: /platform
> inherit-pkg-dir:
>  dir: /sbin
> inherit-pkg-dir:
>  dir: /usr
> fs:
>  dir: /opt
>  special: /dev/md/dsk/d71
>  raw: /dev/md/rdsk/d71
>  type: ufs
>  options: [logging]
> fs:
>  dir: /usr/local
>  special: /dev/md/dsk/d70
>  raw: /dev/md/rdsk/d70
>  type: ufs
>  options: [logging]
> fs:
>  dir: /prod
>  special: /dev/md/dsk/d72
>  raw: /dev/md/rdsk/d72
>  type: ufs
>  options: [logging]
> fs:
>  dir: /svc
>  special: /dev/md/dsk/d73
>  raw: /dev/md/rdsk/d73
>  type: ufs
>  options: [logging]
> net:
>  address: 10.9.3.79
>  physical: ipge1
> attr:
>  name: comment
>  type: string
>  value: "tech10 zone"
> tech3 / 172 #
> 
> tech3 / 173 # cat /etc/release
> Solaris 10 6/06 s10s_u2wos_09a SPARC
> Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.
>  Use is subject to license terms.
>   Assembled 09 June 2006
> 
> tech3 / 174 # zoneadm -z tech10 boot
> zoneadm: zone 'tech10': "/usr/lib/fs/dev/mount -o
> attrdir=/export/tech10/svc /svc /dev/md/dsk/d73" failed
> with exit code 32
> zoneadm: zone 'tech10': call to zoneadmd failed
> 
> tech3 / 175 #
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
could be a range of things as Jerry mentioned,
is the d73 shared out in the global zone by any chance since last zone 
boot, is it some how busy in the global zone?

perhaps run the failing mount command in a truss, ie truss -o 
/tmp/mount.txt -fae mount ... from the command line in the global

Might give some more indication of why the mount is failing.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Problem patching zones with kernel patch 120011-14

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
your sparse zone's zonepath in in /usr and it inherits /usr as well.

In our testing pkgadd calls getcwd in 
/dev/.SUNW_patches_0909107281-1123512-01035723188c/120011-14 inside 
the zone, which instead of returning /dev/.SUNW.. as the absolute 
path returns the absolute path
/usr/local/zones/[zonename]/lu/dev/.SUNW

and this is the what causes the failure in the sparse zone.
Need to do some more investigation as to why the whole root zone is 
failing to see if it's the same problem.

What is the zonecfg of the whole root zone.

Enda




Philip Nelson wrote:
> Path /usr/local/zones, and the zonepath under it, are part of the global 
> zone's /usr/local filesystem.  They are not separate mounts.  On the 
> system where the kernel patch worked, the zonepaths are separate mounts.
> 
> -Philip
> 
> Enda O'Connor wrote:
>> Philip Nelson wrote:
>>> Enda O'Connor wrote:
 Philip Nelson wrote:
> They're 755, all the way to /.
>
> Here's the actual error message a small zone gets:
>
> /usr/local/zones/[zonename]/lu/dev/.SUNW_patches_0909107281-1123512-01035723188c/120011-14/SUNWbart/install/checkinstall:
>  
> /usr/local/zones/[zonename]/lu/dev/.SUNW_patches_0909107281-1123512-01035723188c/120011-14/SUNWbart/install/checkinstall:
>  
> cannot open
> pkgadd: ERROR: checkinstall script did not complete successfully
> Dryrun complete.
> No changes were made to the system.
 Hi Philip
 what is the premissions on the directory structure containing the 
 patch being added?
>>> 775.

 can you boot and halt the zone prior to running patchadd
>>>
>>> Yes--that's how I did it.
>>>
>>> I just patched a 6/01 server with containers, successfully this 
>>> time.  The only differences I can see are that the failing servers 
>>> are 6/06 instead of 6/01 (my earlier 6/01 problem was with a ZFS zone 
>>> root), and that the working 6/01 server has the container roots 
>>> mounted on their own UFS partitions.  The zone roots are still 
>>> permissions 700, but the underlying mount points (what you see if you 
>>> unmount the zone roots) are 755.  On the failing servers, the zone 
>>> roots are not mounted on their own partitions;  they are simply part 
>>> of the /usr/local partition.
>> hmm, need to test this locally to see what is up, suspect that the 
>> code in patchadd that mounts things up for installing the 120011 patch 
>> is getting confused somewhere.
>> So just to be clear, /usr/local/zones is part of the root filesystem, 
>> it's not a seperate mount.
>>
>> Enda
>>>
>>> Any idea if nobody would be able to reference an underlying mount 
>>> point, and ignore the perms of the filesystem mounted on top of it?
>>>
>>> -Philip

 Enda
>
> -Philip
>
> Enda O'Connor wrote:
>> Philip wrote:
>>> I've run into difficulty installing sparc kernel patch 120011-14 
>>> from the Oct/03/07 recommended patch cluster onto 6/01 and 6/06 
>>> systems with non-global zones (whether small or large).
>>>
>>> As long as all non-global zones are halted (and don't have ZFS 
>>> roots), the patch installs all right in the global zone.  
>>> However, it gives a failure message for installation in the 
>>> non-global zones because user nobody can't read the zone roots 
>>> (due to the required 700 permissions on those directories).  If I 
>>> try to give nobody read access to those directories, the patch 
>>> fails anyhow because it can't boot the non-global zone (it fails 
>>> on the 700 perms check).  I can't run the patch with the zones 
>>> already started because the kernel patch requires them to be 
>>> halted (for deferred activation patching).  So, I'm boxed in.
>>>
>>> There are a couple other patches not installing into the 
>>> non-global zones because they fail a dependency check on the 
>>> kernel patch.  I'm hoping that the small zones are inheriting the 
>>> patches anyhow, but I don't know what to do with the big zones.
>>>
>>> Any thoughts?
>>>  
>>>  
>>> This message posted from opensolaris.org
>>> ___
>>> zones-discuss mailing list
>>> zones-discuss@opensolaris.org
>>>   
>> Hi
>> wierd, my zonepaths are all 700 and it works fine, what is the 
>> permission of the parent of zonepath?
>>
>> Enda
>>


>>
>>

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Problem patching zones with kernel patch 120011-14

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Philip
Just to be absolutely clear

the zonepath is in an inherited dir of the zone?
ie /usr/lcoal/zones which is the zonepath is also inherited as it's a 
sparse zone.
Could I see your zonecfg info for the failing sparse zone ( also one for 
the whole root zone that fails )

If the zonepath is also on an inherited dir of the zone, then this will 
not work, and actually zoneadm should probably stop one from doing this
But if it's not the case then please forward the zonecfg info as I need 
to try and determine the root of the problem.

Enda


Philip Nelson wrote:
> Path /usr/local/zones, and the zonepath under it, are part of the global 
> zone's /usr/local filesystem.  They are not separate mounts.  On the 
> system where the kernel patch worked, the zonepaths are separate mounts.
> 
> -Philip
> 
> Enda O'Connor wrote:
>> Philip Nelson wrote:
>>> Enda O'Connor wrote:
 Philip Nelson wrote:
> They're 755, all the way to /.
>
> Here's the actual error message a small zone gets:
>
> /usr/local/zones/[zonename]/lu/dev/.SUNW_patches_0909107281-1123512-01035723188c/120011-14/SUNWbart/install/checkinstall:
>  
> /usr/local/zones/[zonename]/lu/dev/.SUNW_patches_0909107281-1123512-01035723188c/120011-14/SUNWbart/install/checkinstall:
>  
> cannot open
> pkgadd: ERROR: checkinstall script did not complete successfully
> Dryrun complete.
> No changes were made to the system.
 Hi Philip
 what is the premissions on the directory structure containing the 
 patch being added?
>>> 775.

 can you boot and halt the zone prior to running patchadd
>>>
>>> Yes--that's how I did it.
>>>
>>> I just patched a 6/01 server with containers, successfully this 
>>> time.  The only differences I can see are that the failing servers 
>>> are 6/06 instead of 6/01 (my earlier 6/01 problem was with a ZFS zone 
>>> root), and that the working 6/01 server has the container roots 
>>> mounted on their own UFS partitions.  The zone roots are still 
>>> permissions 700, but the underlying mount points (what you see if you 
>>> unmount the zone roots) are 755.  On the failing servers, the zone 
>>> roots are not mounted on their own partitions;  they are simply part 
>>> of the /usr/local partition.
>> hmm, need to test this locally to see what is up, suspect that the 
>> code in patchadd that mounts things up for installing the 120011 patch 
>> is getting confused somewhere.
>> So just to be clear, /usr/local/zones is part of the root filesystem, 
>> it's not a seperate mount.
>>
>> Enda
>>>
>>> Any idea if nobody would be able to reference an underlying mount 
>>> point, and ignore the perms of the filesystem mounted on top of it?
>>>
>>> -Philip

 Enda
>
> -Philip
>
> Enda O'Connor wrote:
>> Philip wrote:
>>> I've run into difficulty installing sparc kernel patch 120011-14 
>>> from the Oct/03/07 recommended patch cluster onto 6/01 and 6/06 
>>> systems with non-global zones (whether small or large).
>>>
>>> As long as all non-global zones are halted (and don't have ZFS 
>>> roots), the patch installs all right in the global zone.  
>>> However, it gives a failure message for installation in the 
>>> non-global zones because user nobody can't read the zone roots 
>>> (due to the required 700 permissions on those directories).  If I 
>>> try to give nobody read access to those directories, the patch 
>>> fails anyhow because it can't boot the non-global zone (it fails 
>>> on the 700 perms check).  I can't run the patch with the zones 
>>> already started because the kernel patch requires them to be 
>>> halted (for deferred activation patching).  So, I'm boxed in.
>>>
>>> There are a couple other patches not installing into the 
>>> non-global zones because they fail a dependency check on the 
>>> kernel patch.  I'm hoping that the small zones are inheriting the 
>>> patches anyhow, but I don't know what to do with the big zones.
>>>
>>> Any thoughts?
>>>  
>>>  
>>> This message posted from opensolaris.org
>>> ___
>>> zones-discuss mailing list
>>> zones-discuss@opensolaris.org
>>>   
>> Hi
>> wierd, my zonepaths are all 700 and it works fine, what is the 
>> permission of the parent of zonepath?
>>
>> Enda
>>


>>
>>

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] RSC cards and zlogin -C to a zone clash of interest

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ihsan Zaghmouth wrote:
> Here's one issue that was raised by a Sun customer ... Looks like we 
> have a clash of ineterst on "~."
>  
> They have v490s with RSC cards (Remote System Control) and Zones.
>  
> When they do *console -C "zone"* , then do a *~.*  to disconnect from 
> that zones console, it takes them to the *RSC> prompt.*
> If they "console" from there, they go back to the zone console. 
> 
> They can't escape back to the global zone.
>  
> Anyone seen this before... Any thoughts ?
does ~~. help
> 
> cheers
> Ihsan
> 
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] RSC cards and zlogin -C to a zone clash of interest

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ihsan Zaghmouth wrote:
> Well I recommended the customer to use the -e option when they zlogin 
> and change it to ? or > or any other character they wish for, at least 
> for now.
> 
> zlogin *-e ?*  -C  zonename
> 
> *-e* c
> 
> Specifies a different escape character, c, for the key sequence used
> to access extended functions and to disconnect from the login. 
> 
> *The default escape character is the tilde (~).*
> 
> 
as both use tilde, you need the double ~~. ie escape the tilde itself as 
I suggested ( try it and it should work )

Enda
> 
> Enda O'Connor ( Sun Micro Systems Ireland) wrote:
>> Ihsan Zaghmouth wrote:
>>> Here's one issue that was raised by a Sun customer ... Looks like we 
>>> have a clash of ineterst on "~."
>>>  
>>> They have v490s with RSC cards (Remote System Control) and Zones.
>>>  
>>> When they do *console -C "zone"* , then do a *~.*  to disconnect from 
>>> that zones console, it takes them to the *RSC> prompt.*
>>> If they "console" from there, they go back to the zone console.
>>> They can't escape back to the global zone.
>>>  
>>> Anyone seen this before... Any thoughts ?
>> does ~~. help
>>>
>>> cheers
>>> Ihsan
>>>
>>>
>>>
>>> 
>>>
>>> ___
>>> zones-discuss mailing list
>>> zones-discuss@opensolaris.org
>>
> 
> -- 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zlogin invoked by cron hangs after a few minutes

[Enda O'Connor ( Sun Micro Systems Ireland)]

Damien Carbery wrote:
>> are you piping /dev/null to STDIn in the commands, I
>> can see you did 
>> that on the commands line, but not clear if you did
>> it in the script or not.
> For every command in the script?
> The script is:
> http://cvs.opensolaris.org/source/xref/jds/spec-files/trunk/cron-script.sh
> 
> I would like to get my single command experiment working first, 
> proof-of-concept if you will.
> 
> Where does the redirection go? Inside the quoted command or for zlogin?
> zlogin -l gbuild big-zone "the_command  zlogin -l gbuild big-zone "the_command"   
>  
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Non-interactive zone creation

[Enda O'Connor ( Sun Micro Systems Ireland)]

Bryan Allen wrote:
> On Nov 6, 2007, at 8:18 AM, Nicolas Dorfsman wrote:
> 
>> Hi all,
>>
>> Is there anyone here working on something able to create/configure/ 
>> boot a zone without interactivity ?  I tried to update  
>> create_zone.sh but it's a little bit hard to maintain it in shell.
>> So, an alternative would be to create a brand new one in Perl...or  
>> to work on something different directly in Solaris source.
> 
> 
> http://www.madstop.com/managing-solaris-zones.html
> 
> I have my own set of zone-creation scripts (newzone.sh, then various  
> nnn-foo.sh scripts which get iterated over), though I will soon be  
> moving to using puppet to manage creation. I already use puppet to  
> manage configuration, so it's not much of a stretch for me. I will be  
> much happier when adding a new zone to a system simply involved adding  
> a bittova config to a puppet node class. :-)
> 
> It's somewhat kludgey with the shell scripts, though I wouldn't say  
> it's particularly tedious.
> 
> Cheers.
> --
> bda
> cyberpunk is dead. long live cyberpunk.
> http://bda.mirrorshades.net/
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
I looked at your site and I see the following ( sorry about formating )


{
puppet -d -e 'zone { myzone: ensure => running }'

This won't get any inherited directories or any network addresses, but 
you can always add them later:

puppet -d -e ' zone { myzone: ensure => running, inherits => ["/usr", 
"/sbin"] }'

Yes, that will modify the configuration of your existing zone, not try 
to create a new one or any some such.}

}

Now one cannot modify the inherited directories once a zone is 
installed. ( you can up to that point alright )

ie if you create a whole root zone ( ie install it via zoneadm install ) 
then the only way to add inherited dir's is by a reinstall as far as I know.

You can modify the ip etc on the fly, but the inherited dirs bit in 
relation to the default dirs such as /lib /sbin /bin & /platform cannot 
be changed once installed.


Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Configuration on first boot of a zone

[Enda O'Connor ( Sun Micro Systems Ireland)]

Andrew Black wrote:
> When I first create a zone, it normally asks you some questions such as the 
> time zone and whether you want NIS etc.
> 
>  - is there any way of autmating this so you always get the same answer
>  - today I created a zone and it didnt ask me these questions. I wasnt 
> aware of doing anything different.
> 
> Andrew
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
Did you clone the zone by any chance as this does not go through sysidcfg?
Else how did you create the zone?


To automate it I usually insert a sysidcfg file in ${zonepath}/root/etc 
such as
# cat sysidcfg
system_locale=C
terminal=xterm
network_interface=PRIMARY {
 hostname=myzone
 ip_address=
 default_route=
 protocol_ipv6=no
 netmask=255.255.255.0
 }
name_service=NIS {
 domain_name=lab1.ireland.sun.com
 }
security_policy=NONE
root_password=
timezone=GB-Eire
nfs4_domain=sun.com
timeserver=server1
#

default route from netstat -rn and so on.


Enda

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Can't install zone after 10_recommended

[Enda O'Connor ( Sun Micro Systems Ireland)]

Mangan wrote:
> I installed the 10_recommended patchset on a machine that had a running zone. 
> The host machine and the running zone appear to be ok but when I try to 
> install an additional zone the new zone gets created but it won't go through 
> the sys config routine and you can't change the root password ( permission 
> denied) even though you can login via zlogin. I took an identical T2000 
> without the 10_reccommended patchset and I can create as many working zones 
> as I want. Could this be a part of 120011-14 patch problem?
> 
> ---Paul Mangan
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
could we get some info on the setup
ie os release ( cat /etc/release )
what patches got applied as part of this cluster install. ( just the 
newly applied ones )
what patches are applied in total ls -tr1 /var/sadm/patch + patchadd -p 
output
also cat /var/sadm/system/admin/CLUSTER

Were there errors during zone install, have a look at
/root/var/sadm/system/logs and verify that no errors are present.

what exactly happens during the sysconfig part?

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] [zfs-discuss] 3510 Array and ZFS/Zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Mangan wrote:
> Is this a release that can be downloaded from the website and will work on 
> SPARC systems. The write up says it is for VMware. Am I missing something?
> 
> 
>> Use Solaris 10 9/07.  It has more than a year's worth of improvements
>> and enhancements to Solaris.
>> -- richard
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
Haven't been following this thread so I might be off topic ..

I think this should be 8/07 ( Solaris 10 update 4 )
If so then it's on the download site ( or should be ) and works for 
SPARC/x86 ( same as any Solaris 10 release )

What writeup are you looking at?


Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] [zfs-discuss] 3510 Array and ZFS/Zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Richard Elling wrote:
> Morris Hooten wrote:
>> I looked through the solarsinternals zfs best practices and not
>> completly sure
>> of the best scenario.
>>   
> 
> ok, perhaps we should add some clarifications...
> 
>> I have a Solaris 10 6/06 Generic_125100-10 box with attached 3510 array
>> and would like to use zfs on it. Should I create multiple logical disks
>> thru the raid
>> controller then create zfs raid file systems across the LD's?
>>
>>   
> 
> That method will work ok.  Many people do this with various RAID
> arrays.  We can't answer the question "is it the best way?" because we
> would need more detailed information on what you are trying to
> accomplish and how you want to make design trade-offs.  So for now,
> I would say it works just like you would expect.
> 
>> Can I also migrate zones that are on a ufs file system now into a newly
>> created zfs file system
>> although knowing the limitations with zones and zfs in 06/06?
>>   
> 
> Zone limitations with ZFS should be well documented in the admin
> guides.  Currently, the install and patch process is not ZFS aware, which
> might cause you some difficulty with upgrading or patching.  There are
> alternative methods to solve this problem, but you should be aware of the
> current limitation.

the patch to fix the patch of zones on zfs is pending.
119254/119255 revision 49, we hope to release this in the coming days ( 
maybe by COB today even )
> 
>> Recommendations?
>>   
> 
> Use Solaris 10 9/07.  It has more than a year's worth of improvements
> and enhancements to Solaris.
I think you mean 8/07, ( update 4 ) release?
But yes this release is most advised,
Enda
>  -- richard
> 
> ___
> zfs-discuss mailing list
> [EMAIL PROTECTED]
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] [zfs-discuss] 3510 Array and ZFS/Zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Mangan wrote:
> The 9/07 release appears to be for X86 only. The 8/07 release appears to be 
> for Sparc or X86. The 9/07 release is also titled " Express Developers 
> Edition 9/07".
> 
> Apparently not a release I can use.
> 
> Thanks for the quick feedback.
ok my mistake, getting confused by release numbers, 9.07 was what 
Richard meant.

Enda

> When is the next release for Sparc due out?
> 
> Paul
> 
> 
> -----Original Message-
>> From: "Enda O'Connor ( Sun Micro Systems Ireland)" <[EMAIL PROTECTED]>
>> Sent: Dec 21, 2007 9:15 AM
>> To: Richard Elling <[EMAIL PROTECTED]>
>> Cc: [EMAIL PROTECTED], zones-discuss@opensolaris.org, [EMAIL PROTECTED]
>> Subject: Re: [zones-discuss] [zfs-discuss] 3510 Array and ZFS/Zones
>>
>> Richard Elling wrote:
>>> Morris Hooten wrote:
>>>> I looked through the solarsinternals zfs best practices and not
>>>> completly sure
>>>> of the best scenario.
>>>>   
>>> ok, perhaps we should add some clarifications...
>>>
>>>> I have a Solaris 10 6/06 Generic_125100-10 box with attached 3510 array
>>>> and would like to use zfs on it. Should I create multiple logical disks
>>>> thru the raid
>>>> controller then create zfs raid file systems across the LD's?
>>>>
>>>>   
>>> That method will work ok.  Many people do this with various RAID
>>> arrays.  We can't answer the question "is it the best way?" because we
>>> would need more detailed information on what you are trying to
>>> accomplish and how you want to make design trade-offs.  So for now,
>>> I would say it works just like you would expect.
>>>
>>>> Can I also migrate zones that are on a ufs file system now into a newly
>>>> created zfs file system
>>>> although knowing the limitations with zones and zfs in 06/06?
>>>>   
>>> Zone limitations with ZFS should be well documented in the admin
>>> guides.  Currently, the install and patch process is not ZFS aware, which
>>> might cause you some difficulty with upgrading or patching.  There are
>>> alternative methods to solve this problem, but you should be aware of the
>>> current limitation.
>> the patch to fix the patch of zones on zfs is pending.
>> 119254/119255 revision 49, we hope to release this in the coming days ( 
>> maybe by COB today even )
>>>> Recommendations?
>>>>   
>>> Use Solaris 10 9/07.  It has more than a year's worth of improvements
>>> and enhancements to Solaris.
>> I think you mean 8/07, ( update 4 ) release?
>> But yes this release is most advised,
>> Enda
>>>  -- richard
>>>
>>> ___
>>> zfs-discuss mailing list
>>> [EMAIL PROTECTED]
>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] execute process from global

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Not that I'm aware of.
Is there a reason you are you doing this, ie executing a process in the 
local zone from global zone, you could use zlogin, but I assume that 
this too is not acceptable.


Enda
Caroline Carol wrote:
> Hi,
>  
>  
> is it possible to execute a process (on the local zone) from global zone 
> without using ssh or rsh ?
>  
> Thanks a lot
>  
> Carol
>  
> 
> 
> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails 
> 
>  
> vers Yahoo! Mail
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Re : execute process from global

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Caroline
I've added back zones-disucss to my reply ( hope that's ok )

Licence issues aside as I'm not sure how my reply ties in with same

if you install the app such that's it inherited by the zone(s)
ie using add fs in zonecfg perhaps or just having it in an inherited 
directory
then depending on the app and configuration details, you could zlogin to 
the zone and execute it in the zone. But I'm not familiar enough with 
licencing or this apps licencing in particular to say much.

There is no way of actually launching it in the global zone with local 
zone context. You can see the zones PID's from the global, but as I'm 
not familiar with your app, it's hard to say what best approach is.


Enda

Caroline Carol wrote:
> yes
> the reason :
> monitor process from global zone, so I'll have to install monitoring 
> agent only in global zone and adapt all scripts to monitor local zones 
> ---> So I will not install agent in all local zones ---> Save licences
>  
> Thanks
> 
> - Message d'origine 
> De : Enda O'Connor ( Sun Micro Systems Ireland) <[EMAIL PROTECTED]>
> À : Caroline Carol <[EMAIL PROTECTED]>
> Cc : zones-discuss@opensolaris.org
> Envoyé le : Lundi, 28 Janvier 2008, 16h45mn 44s
> Objet : Re: [zones-discuss] execute process from global
> 
> Hi
> Not that I'm aware of.
> Is there a reason you are you doing this, ie executing a process in the
> local zone from global zone, you could use zlogin, but I assume that
> this too is not acceptable.
> 
> 
> Enda
> Caroline Carol wrote:
>  > Hi,
>  > 
>  > 
>  > is it possible to execute a process (on the local zone) from global zone
>  > without using ssh or rsh ?
>  > 
>  > Thanks a lot
>  > 
>  > Carol
>  > 
>  >
>  > 
>  > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails
>  > 
> <http://fr.rd.yahoo.com/mail/mail_taglines/trueswitch/*http://www.trueswitch.com/yahoo-fr/>
>  
> 
>  > vers Yahoo! Mail
>  >
>  >
>  > 
>  >
>  > ___
>  > zones-discuss mailing list
>  > zones-discuss@opensolaris.org <mailto:zones-discuss@opensolaris.org>
> 
> 
> 
> 
> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails 
> <http://fr.rd.yahoo.com/mail/mail_taglines/trueswitch/*http://www.trueswitch.com/yahoo-fr/>
>  
> vers Yahoo! Mail

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Zone creation Hangs.

[Enda O'Connor ( Sun Micro Systems Ireland)]

Morris Hooten wrote:
> I've crated many zones but haven't seen this one yet and have tried
> a few things and can't get it past this point in installing the new zone.
> 
> it just hangs at the point below
> 
> any hinsts? i looked in sunsolve but nothing specific
> 
> thanks
> 
> 
> 
> Creating list of files to copy from the global zone.
> Copying <2873> files to the zone.
> Initializing zone product registry.
> Determining zone package initialization order.
> Preparing to initialize <1165> packages on the zone.
> Initializing package <1164> of <1165>: percent complete: 99%
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
what does the last entry in the zone install log look like ( although it 
mightn't have flushed the relevant data to file it might be worth a look )
so /root/var/sadm/system/logs/install_log

what does ptree say for the global zone ( ptree -z global )
maybe a truss of the hung process mighgt shed some light.

also what is the OS release etc
Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Moving zones to a new system

[Enda O'Connor ( Sun Micro Systems Ireland)]

Crambit Team wrote:
> Hi all,
> I need to move two zones to a 2 different systems as global zone. In one 
> of them I have Oracle. 
> My questions are:
> 
> 1) What is the best way to do so?
what Solaris release are you on?
If it's the Solaris 10 updates, then best to have both systems in sync in terms 
of patches 
+ packages really. After that then, zoneadm detach/attach are your best bet.
> 2) From the zone that has Oracle is there anything I have to be aware of 
> when I move it?
ah yes Oracle, well how are you managing the migration of the Oracle datafiles 
and so on, 
I assume you probably have some storage available to the zone via zonecfg add 
device etc?

I assume memory etc on the new system is sufficient for Oracle.

In general moving an app like an Oracle DB, would require large amounts of 
testing, so 
that things like performance don't take a nosedive.
In my experience with Oracle, moving from one system to another can induce 
performance 
issues with respect to how say access is configured to storage on the new 
system, or say 
how a later OS release might impact on the current optimised database, ie if 
your database 
is highly optimised with respect to one system, it might take some time to get 
it to say 
level on a later OS update etc.
Very hard to tell with Oracle, so I'd strongly suggest trying to setup a test 
zone on 
target system and replicate the DB to this, in order to test performance etc 
beforehand.

Enda


> 
> TIA
> 
> Fred
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Moving zones to a new system

[Enda O'Connor ( Sun Micro Systems Ireland)]

Crambit Team wrote:
> Hi Enda,
> the Solaris  release is 8/07. 
> What I really need is move the zone (doing like an ufsdump) and let it 
> becaming a global zone and not a zone in a another system. 

not that I'm aware of ( making a non-global zone be a global zone somewhere 
else)
Sorry I missed that bit of vital info in previous mail.

un-doable I would imagine as zones would not have the files/binaries need to 
actually 
physically boot a system ( due to SUNW_PKG_HOLLOW=true on some core packages )

I'd suggest installing oracle on target machine and importing DB to it.
then rebuild indexes etc.

Is there some other reason for not being able to do above ( ie import oracle DB 
)

Enda
> 
> This is because we didn't have a new Sun blade so we created a zone in 
> another machine then the oracle/application people could work in the 
> meantime we order another system.
> 
> Fred
> 
> 
> On Mon, Mar 31, 2008 at 1:57 PM, Enda O'Connor ( Sun Micro Systems 
> Ireland) <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
> 
> Crambit Team wrote:
>  > Hi all,
>  > I need to move two zones to a 2 different systems as global zone.
> In one
>  > of them I have Oracle.
>  > My questions are:
>  >
>  > 1) What is the best way to do so?
> what Solaris release are you on?
> If it's the Solaris 10 updates, then best to have both systems in
> sync in terms of patches
> + packages really. After that then, zoneadm detach/attach are your
> best bet.
>  > 2) From the zone that has Oracle is there anything I have to be
> aware of
>  > when I move it?
> ah yes Oracle, well how are you managing the migration of the Oracle
> datafiles and so on,
> I assume you probably have some storage available to the zone via
> zonecfg add device etc?
> 
> I assume memory etc on the new system is sufficient for Oracle.
> 
> In general moving an app like an Oracle DB, would require large
> amounts of testing, so
> that things like performance don't take a nosedive.
> In my experience with Oracle, moving from one system to another can
> induce performance
> issues with respect to how say access is configured to storage on
> the new system, or say
> how a later OS release might impact on the current optimised
> database, ie if your database
> is highly optimised with respect to one system, it might take some
> time to get it to say
> level on a later OS update etc.
> Very hard to tell with Oracle, so I'd strongly suggest trying to
> setup a test zone on
> target system and replicate the DB to this, in order to test
> performance etc beforehand.
> 
> Enda
> 
> 
>  >
>  > TIA
>  >
>  > Fred
>  >
>  >
>  >
> 
>  >
>  > ___
>  > zones-discuss mailing list
>  > zones-discuss@opensolaris.org <mailto:zones-discuss@opensolaris.org>
> 
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Moving zones to a new system

[Enda O'Connor ( Sun Micro Systems Ireland)]

Mike Gerdts wrote:
> On Mon, Mar 31, 2008 at 7:38 AM, Crambit Team <[EMAIL PROTECTED]> wrote:
>> Hi Enda,
>> the Solaris  release is 8/07.
>> What I really need is move the zone (doing like an ufsdump) and let it
>> becaming a global zone and not a zone in a another system.
>>
>> This is because we didn't have a new Sun blade so we created a zone in
>> another machine then the oracle/application people could work in the
>> meantime we order another system.
>>
> 
> Maybe this will help:
> 
> http://mail.opensolaris.org/pipermail/zones-discuss/2008-February/003622.html
> 
hmm, for Oracle probably best to just install it ( easier than copying over the 
oracle 
install and all it's bits ie password file , and those in /var/opt ) and then 
either use 
standard oracle procedure to migrate the database over.
transportable tablespaces are of grate help here really.
you'd need to build the DB instance on the target node first etc.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] RE : Re: dhcp/zones

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi
Can you access the following doc?
http://www.sunsolve.sun.com/search/document.do?assetkey=1-61-234401-1&searchclause=patch%2420ip-instances

it has a section on patches for ce driver and ip-instances
{
Getting CE driver to work with ip-instances.
To get the ce driver to work with ip-instances in 8/11 or earler releases, you 
need to add 
the following patches.
137042-01   SunOS 5.10: zoneadmd patch
137043-01   SunOS 5.10_x86: zoneadmd patch
as well as
118777-12   SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch
118778-11   SunOS 5.10_x86: Sun GigaSwift Ethernet 1.0 driver patch
}

please make sure to add the latest rev of patch utils first
119254 ( SPARC )
119255 ( x86 )
before adding other patches. If there are higher rev's of above patches, use 
the highest 
rev available.

Enda



elkhaoul elkhaoul wrote:
> Thanks for your answer.
>  
> I am using Solaris 10 U4 8/07
> And my interface is :
>  
> ### dladm show-link
> ce0 type: legacymtu: 1500   device: ce0
> ce1 type: legacymtu: 1500   device: ce1
> Is this interface support exclusive IP ?
>  
> Thanks
>  
> 
> 
> */James Carlson <[EMAIL PROTECTED]>/* a écrit :
> 
> Caroline Carol writes:
>  > Can you please let me know if DHCP works on local zones NOW ???
> 
> It's worked for quite some time now. You need to set up your
> non-global zones using "set ip-type=exclusive".
> 
>  > Is there any patch that fix this problem ???
> 
> OpenSolaris doesn't have patches. What are you running?
> 
> If you're using Solaris 10, you should be contacting Sun's support
> group instead. (I believe IP Instances went into Solaris 10 Update 4,
> but, unlike OpenSolaris, some Ethernet drivers are not supported, and
> you may need patches for others.)
> 
> -- 
> James Carlson, Solaris Networking
> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
> 
> 
> 
> Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les 
> tarifs exceptionnels pour appeler la France et l'international. 
> Téléchargez 
> 
>  
> la version beta.
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Patches vs Updates - Zone Features

[Enda O'Connor ( Sun Micro Systems Ireland)]

Ellard Roush wrote:
> Hi,
> 
> Solaris 10 update 4 introduced the BrandZ feature set.
> Solaris 10 update 5 will introduce more zone features.
> Today Sun Cluster requires the the Solaris 10 release be at
> least up to the Solaris 10 update 3 level.
> 
> We are proposing to ship a new feature in Sun Cluster
> that will use the BrandZ feature set and support
> the new zone features in Solaris 10 update 5.
> Naturally, this new feature will only be operational
> when the customer installs Solaris 10 update 5.
> 
> There are at least 2 ways to load new software.
> 
> 1) Install the Solaris 10 update 5 release
> 
> In this case we know that everything works fine.
> 
> 2) Install patches for Solaris 10 update 5.
> This approach loads all of the bug fixes,
> and does not load the new packages.
> 
> If a customer installs patches,
> will BrandZ and all the new zone features
> of Solaris 10 update 5 work ?
> Or will the customer just get the bug fixes ?
they'll get everything in this case.
127127-11/127128-11 is the u5 kernel patch that will deliver all this.
What features are you interested in.

As for installing patcehs on zones systems there are a few things they need to 
be aware of.
1 install latest patch utils first (119254/119255)
2 always run patchadd -a  first before installing the patch.

the -a does a dryrun and especially in the case of zones, will catch issues 
like zones 
dependency issues/unbootable zones etc. No files get modified, so it allows you 
to 
identify certain types of issues ( not all issues mind you ).
The patchadd -a output is pretty hard to parse, but make sure to examine 
closely for any 
issues relating to zones etc.

Enda

> 
> 
> ---
> Our people in the field say that customers are
> much more willing to install patch
> as opposed to installing an update.
> 
> Some aspects of patching are murky.
> So your help is appreciated.
> 
> Regards,
> Ellard
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] WARNING

[Enda O'Connor ( Sun Micro Systems Ireland)]

Sanjay Akula wrote:
> Did anybody saw this WARNING messages while loading patch cluster what 
> does it means.
> 
> Installing 120011-14...
> /kernel/drv/sparcv9/fcp: undefined symbol 'fc_ulp_hold_remote_port'
> WARNING: mod_load: cannot load module 'fcp'
> WARNING: fctl: ULP FCSM version mismatch; please upgrade FCSM
> 
> Can any one suggest me the solution.
> -- 
> Regards,
> 
> SysAdmin
> 
> 
> 
> 
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
The only time I have seen this is in the following scenario

user adds patch a-03 which delivers a newer incompatible kernel module ( by 
incompatible I 
mean that the new module depends on say a new genunix not loaded till next 
reboot )say 
module fcp-version3,without forcing a load of the old module it is replacing, 
later in the 
same patch session user applies 120011-14, which deliver fcp-version4 ( a newer 
incompatible fcp module ), but due to how this patch 120011-14 is installed, 
patchadd 
actually forces a load of the existing modules including the incompatible 
fcp-version3, 
leading to the warning.

These are benign and once a reboot has occurred, order will be restored, as the 
new 
genunix in 120012-14 will be compatible with the new fcp module.

so I suspect you applied another patch before 120011-14 that also delivered fcp 
module.
Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] convert sparse zone to whole root zone?!?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Krzys wrote:
> Is there way to convert sparse solaris zone to whole root zone? if yes what 
> or 
> how could I do that? Is it even possible to do so?
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
Hi
No it's not possible, currently you'd have to uninstall/delete the sparse zone 
and re do 
it as a whole root zone.

Why is it necessary to do this out of interest.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] S10U6 zone features

[Enda O'Connor ( Sun Micro Systems Ireland)]

James Carlson wrote:
> Henrik Johansson writes:
>> Any word if we will get any of these features/fix in S10U6, it would  
>> make life with zones quite a bit easier...
>>
>> Zone update on attach (PSARC/2007/621)
>> Attach/dettach between sun4u and sun4v (6480464)
>> Vanity naming (PSARC 2006/499)
>> 6637869 zone attach doesn't handle obsolete patches correctly
> 
> If you need information on S10 updates, you should contact your local
> support folks.  S10 updates aren't OpenSolaris, so there's no reason
> to discuss their schedules or content here, and there's no necessary
> relationship between features that get integrated into Nevada and ones
> that end up in any particular update.
> 
> I didn't look at the others, but the one networking (not zones)
> feature you list there -- vanity naming (CR 6577618) -- doesn't appear
> to have an MR entry for S10, so I would have to guess that no backport
> is in progress, at least right now.
> 
> The way a backport often ends up happening is that a contract customer
> for one of those older supported releases makes a formal request
> through Sun's support group.  That doesn't happen on opensolaris.org.
> 
yep not really opensolaris question, but other than vanity naming, the rest are 
targeted 
at u6 and already integrated into early builds of u6 it would seem.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Can I configure my zones on a ZFS filesystem?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Henrik Johansson wrote:
> Hello,
> 
> On Jun 26, 2008, at 6:46 PM, Enda O'Connor wrote:
>> Hi
>> As far as I know it will be available in s10_u6 release, Lu currently
>> does not handle zones on zfs.
>> you can patch zones on zfs, but not upgrade currently.
>>
>> Enda
> 
> Now we are talking Solaris 10 again, but we might as well talk S10 -> 
> Nevada.
> 
> Since you use the LU packages from the release you are upgrading too, 
> can you put the zones on ZFS now and wait with upgrades until U6 is 
> released? / Can you upgrade from Solaris 10 to Nevada if you have placed 
> your zonepaths on ZFS before upgrade?
> 
> Regards
> Henrik
Hi
well yes you can wait for u6 Lu packages to some on line.

As far as I know you can upgrade to nevada as well, but I've not done that so 
wouldn't 
like to say for sure.

Enda
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone install

[Enda O'Connor ( Sun Micro Systems Ireland)]

Maciej Browarski wrote:
> Hello,
> When I type zone install, all packages from global zone are installed in 
> non-global zone.
> How can I select packages which I like to have in non-global zone 
> (similar configuration  when install solaris  10 and we can custom 
> install) ?
> 
> 
> Regards,
> 
This isn't configurable at zonecfg level.
i.ei zoneadm install will just install all packages from global zone to each 
ngz being 
installed.
Packages installed via pkgadd -G are not installed in NGZ, but these would 
typically be 
packages for usrland software, like a webserver perhaps.

There is no concept of metaclusters in relation to zones, you just get the 
packages that 
are installed in the global zone replicated into each non global zone.
Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] zone install

[Enda O'Connor ( Sun Micro Systems Ireland)]

Maciej Browarski wrote:
> Hm,
> But if I try install packages (core libs and other) with option -R and 
> after that can I  enclose this directory with ZONE ?
> 
> 
sorry I don't understand what you intend, could you provide an example of this 
pkgadd -R 
and how you enclose this directory with ZONE.

thanks
Enda
> Maciej Browarski
> 
> 
> 
> 
> 
> Enda O'Connor ( Sun Micro Systems Ireland) wrote:
>> Maciej Browarski wrote:
>>> Hello,
>>> When I type zone install, all packages from global zone are installed 
>>> in non-global zone.
>>> How can I select packages which I like to have in non-global zone 
>>> (similar configuration  when install solaris  10 and we can custom 
>>> install) ?
>>>
>>>
>>> Regards,
>>>
>> This isn't configurable at zonecfg level.
>> i.ei zoneadm install will just install all packages from global zone 
>> to each ngz being installed.
>> Packages installed via pkgadd -G are not installed in NGZ, but these 
>> would typically be packages for usrland software, like a webserver 
>> perhaps.
>>
>> There is no concept of metaclusters in relation to zones, you just get 
>> the packages that are installed in the global zone replicated into 
>> each non global zone.
>> Enda
>>
>>

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Can I configure my zones on a ZFS filesystem?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Hi Elizabeth
This cluster should have worked, I will check what rev of patch utils is 
included.

The cluster would have installed a pretty recent rev of patch utils towards the 
start, 
which should have been able to patch your system. There is no need to apply the 
patch 
utilites outside of the cluster generally, unless you are applying a cluster 
that is not 
recent, although I do recommend checking SunSolve to see what the latest rev of 
119254 or 
119555 is ( SPARC|x86 patch utils patch ), if there is a more recent one, I'd 
suggest 
applying it beforehand though.

Do you have any logs from the failure, or even remember what the error was 
approximately,
We'd like to identify the issue if possible, as without some data it's hard to 
say what 
might have happened. There is an issue currently open around patchadd not 
properly 
resolving mountpoints in relation to adding 120011-14, but without some data 
it's not 
possible to tell. But I suspect the problem you had is slightly different, as 
it this case 
it appears that the patch partially applied?, whereas in the case I described 
the patch 
would have failed to apply to start with.

Enda
Elizabeth Schwartz wrote:
> I was using the patch cluster from June 3.
> I read all the README's for that patch cluster and there wasn't
> anything about upgrading patch utilities first - which patches are
> those?
> 
> At this point I can't roll back and see exactly what patches were on
> the system without going back to tape, but it hadn't been patched in
> a while. A more recently built and patched S10u3 server didn't have
> the same problems.
> 
> On Sun, Jun 29, 2008 at 7:49 AM, Henrik Johansson <[EMAIL PROTECTED]> wrote:
>> On Jun 29, 2008, at 10:57 AM, Enda O'Connor wrote:
>>
>>> Hi
>>> When was this, or to be precise what rev of patch utils was
>>> installed,119254/11955 SPARC/x86.
>>>
>>> Patching zones on zfs is supported at this point.
>>> Did you report this, what errors did you see etc.
>>>
>>> The original doc mentioned patch and upgrade, most recent mentions
>>> upgrade only.as not being supported.
>>>
>>> If you install 119254/119255 currently on sunsolve, patching zones on
>>> zfs will work, or if it doesn't then you need to report it, as it's
>>> a bug.
>>> Enda
>>> Elizabeth Schwartz wrote:
 It is NOT resolved in Solaris 10 u3, although the patch documentation
 does imply otherwise. . I built some zones on zfs root paths under u3
 and when I tried to install the 10_Recommended patch cluster, it
 bombed out at patch 120011-14. I ended up having to blow away all the
 zones, patch, and rebuild.

 Note that the original documentation only said that building zones
 with zfs zonepath would cause a problem with *upgrade*; it now talks
 about upgrade and *patching*. (Solaris patching seems to do more
 upgrading than it once did...)
>> 120011-14 is a deferred-activation patch, they did not work on ZFS
>> before 119254-46 (6581814), i've had the same problem. As Enda said,
>> it will probably work with the latest version of this patch.
>>
>> I've look at the latest recommended cluster, 119254-53 is patch no 14
>> in the patch_order file, and 120011-14 is patch no 30, do you have the
>> latest recommended cluster?
>>
>> Regards
>> Henrik
>>
>> ___
>> zones-discuss mailing list
>> zones-discuss@opensolaris.org
>>
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Can I configure my zones on a ZFS filesystem?

[Enda O'Connor ( Sun Micro Systems Ireland)]

Dick Davies wrote:
> Ah, that's really interesting ( a bigger deal than ZFS root boot for me).
> 
> Does Nevada LU support it yet? Or does anyone know when it will?
As far as I'm aware it's integrated into nevada ( I will check this out and 
find out build 
), and it will be going into s10 update 6.

Enda
> 
> On Thu, Jun 26, 2008 at 5:46 PM, Enda O'Connor <[EMAIL PROTECTED]> wrote:
>> Lewis Thompson wrote:
> 
>>> http://opensolaris.org/os/community/zones/faq/#sa_zfs states:
>>>
>>> Q: Can I configure my zones on a ZFS filesystem?
>>> A: Solaris 10 Update Release:
>>>  Support for zonepaths on ZFS is under development. [September 2006]
> 
>> As far as I know it will be available in s10_u6 release, Lu currently
>> does not handle zones on zfs.
>> you can patch zones on zfs, but not upgrade currently.
> 
> 

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] questions regarding applying patches on global/non-global zone. (Case 11273876)

[Enda O'Connor ( Sun Micro Systems Ireland)]

[EMAIL PROTECTED] wrote:
> Hi experts,
> 
> I would like consult you some questions regarding applying
> patches on global/non-global zone.
> 
> If non-global zone isn't inherited from global zone(for example,
> when created zone by zonecfg via removing inherit-pkg-dir), there
> is no relation between global zone and non-global zone when apply
> the patches, right ?
> 
> That is to say if flag SUNW_PKG_ALLZONES is set to true
> ("SUNW_PKG_ALLZONES=true"), even though the patches are applied on
> global zone, these patches won't be installed on non-global zone,
> right ?
> 
> Thank you very much.
> Best Regards
> chunhuan
Hi
No, SUNW_PKG_ALLZONES means that the patch can only be applied from the global 
zone, and 
will apply to all non global zones, regardless.
So it doesn't matter whether the zone is sparse or whole ( whole is where there 
are no 
inherited dirs, as in your case ).

The core os libs, ie libc have to be in sync, regardless of inherited 
directories. There 
is only one kernel actually running, so the various bits need to be kept in 
sync.

see man -s4 pkginfo, for a description of the variable.
Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] [smf-discuss] 6725004 - installing single-user-mode patches automatically

[Enda O'Connor ( Sun Micro Systems Ireland)]

Liane Praza wrote:
> I believe the original concern about making system/filesystem/local part 
> of single-user was that it changes the definition of single-user.  The 
> zones team was involved in that discussion, and I've just tried to 
> re-involve them in the resolution discussions.  (And have cc'ed them 
> here.  Apologies for the crosspost.)  It may just be morning, but I'm 
> currently having a hard time finding that argument too compelling on its 
> own -- it seems there must have been something more specific.
> 
> Creating a patch milestone has previously been my preferred direction 
> (as it requires actual definition and design of what the patching 
> frameworks need, rather than just hoping that single user is 
> appropriate), but I'm no longer certain this is a sensible investment, 
> as my understanding of IPS is that they're sticking to their guns and 
> there will be no live patching of the OS that leads us to these types of 
> scenarios.  Thankfully.
not clear when this will be included, today IPS allows you to update SUNWcsr 
for instance 
in the running system ( ie pkg update as opposed to pkg image-update which 
updates an 
alternate BE ), I have seen issues with compilers failing due to SUNWcsr and 
SUNWtoo 
getting out of sync, because user updated the live system.
Also IPS is not relevant to s10 users, who will be patching their systems for 
some time to 
come. ( i.e. many years )

I'd like to hear why fs/local being incorporated into single user milestone was 
not 
considered a good idea.
The patch milestone does sound interesting, as it would involve an agreed 
consensus

cheers
Enda

> 
> Given that, I wonder if a different option is to confirm that 
> system/filesystem/local is idempotent (and not already running), and 
> then have patchadd just run its method directly.  It leaves a bad taste 
> in my mouth, but then again so does the fact that we've got two 
> different patching systems which require the system to be in different 
> states when they run.
> 
> But, again, I think the zones team explored many of these options in the 
> first round and would like to make sure they have a chance to weigh in.
> 
> liane  (in theory, on vacation today.)
> 
> Renaud Manus wrote:
>> A solution could be to move system/filesystem/local in the single-user
>> milestone.
>>
>> -- Renaud
>>
>> Jordan Brown wrote:
>>> Could some SMFers please weigh in on 6725004 and give some opinions on 
>>> how best to address it?
>>>
>>> Here's a summary of the problem:
>>>
>>> Sun Update Connection Enterprise attempts to install "single-user" 
>>> patches using an rcS.d script.  This has historically been a problem, 
>>> since zone roots may not have been mounted yet.  Patchadd was recently 
>>> changed to partially work around this problem, by enabling 
>>> system/filesystem/local, but when that mechanism is triggered from an 
>>> rcS.d script (or, presumably, from a service on which 
>>> milestone/single-user depends), it yields a deadlock - 
>>> system/filesystem/local can't be run, because milestone/single-user 
>>> hasn't been reached.  (This is, I believe, in addition to the technical 
>>> issues surrounding performing SMF operations from an rcS.d script.)
>>>
>>> I believe that the most truly correct way to address this problem is to 
>>> have a deferred patching service that depends on 
>>> system/filesystem/local, and on which all other later services depend. 
>>> However, I think the only way to implement such a service would be to 
>>> modify the dependencies of those later services, and that seems awkward. 
>>>   (One could also rename system/filesystem/local, retain the original 
>>> name as something of a milestone, and insert the deferred patching 
>>> service as a new service between the renamed s/f/l and the original 
>>> s/f/l, but that  seems quite ugly.)
>>> ___
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

___
zones-discuss mailing list
zones-discuss@opensolaris.org