Re: [zones-discuss] Installing a specific dev release into a zone?

2009-12-27 Thread Frank Batschulat (Home)
On Sun, 27 Dec 2009 04:55:21 +0100, Tristan Ball 
tristan.b...@leica-microsystems.com wrote:

 I've got a Opensolaris snv_129 VM with which I'm playing around with
 zones.. Initially everything was fine, however since my initial install
 the opensolaris dev repository has updated to release 130, and now I
 can't install new zones, I get:

 t...@osol-test:~#  zoneadm -z z1 install
 A ZFS file system has been created for this zone.
 Publisher: Using opensolaris.org (http://pkg.opensolaris.org/dev/ ).
 Image: Preparing at /data/zones/z1/root.
 Cache: Using /var/pkg/download.
 Sanity Check: Looking for 'entire' incorporation.
 ERROR: Unable to locate the incorporation
 'ent...@0.5.11,5.11-0.129:20091205T134302Z' in the preferred publisher
 'opensolaris.org'.
 Use -P to supply a publisher which contains this package.

 It looks like the zone install process only gathers information on the
 latest version of each package?

 t...@osol-test:~# pkg -R /data/zones/z1/root list -a |grep -i entire
 entire0.5.11-0.130known
 -


 Is there some way to tell zoneadm install to install a specific dev
 release, in this case 129?  Actually, it looks like zoneadm is trying to

maybe there is a specific repo for dev build versions, but I'm not aware of any,
perhaps you may want to ask on the IPS or on-discuss alias for it 

 install that release, but the defaults on the pkg tools it uses to do
 the install is hiding the availability of 129 on the dev package
 servers. Is there a way around this?

 I realise that I could upgrade my global zone to 130, but I'd really
 like to have the option of picking a given release and sticking with it
 for longer than the dev version release cycles!

the non-global zone runs the native OS of the global zone
(except for branded zones like solaris10(5) branded zone) which is 
in your case 129. however since your publisher defaults to the dev repo, zone 
install will
pick up 130 which is current for the dev repo. so you have to update the global 
zone
to run 130 before you can run 130 in the on-global zone.

for possible issues with 130, refer to: 
http://opensolaris.org/jive/thread.jspa?threadID=120631

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


[zones-discuss] Zone and Apache 2.2

2009-12-27 Thread godefroy montegommery
Hi,

I hope it is the correct place to post this.  

I have created a zone to run Apache 2 on it.  After having installed the 
packages for apache, I have tried to start it, without any success : 

r...@zoneapache:/usr/apache2/2.2/bin# ./apachectl start
r...@zoneapache:/usr/apache2/2.2/bin# ./apachectl stop 
[b]httpd (no pid file) not running[/b]

Here is what i found in the error log :
r...@zoneapache:/var/apache2/2.2/logs# cat error_log 
[Sun Dec 27 18:45:21 2009] [alert] (EAI 8)node name or service name not known: 
mod_unique_id: unable to find IPv4 address of zoneApache
Configuration Failed

What could be the cause of this error?

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


Re: [zones-discuss] Zone and Apache 2.2

2009-12-27 Thread Mike Gerdts
On Sun, Dec 27, 2009 at 9:35 PM, godefroy montegommery
dunkell...@hotmail.com wrote:
 Hi,

 I hope it is the correct place to post this.

 I have created a zone to run Apache 2 on it.  After having installed the 
 packages for apache, I have tried to start it, without any success :

 r...@zoneapache:/usr/apache2/2.2/bin# ./apachectl start
 r...@zoneapache:/usr/apache2/2.2/bin# ./apachectl stop
 [b]httpd (no pid file) not running[/b]

 Here is what i found in the error log :
 r...@zoneapache:/var/apache2/2.2/logs# cat error_log
 [Sun Dec 27 18:45:21 2009] [alert] (EAI 8)node name or service name not 
 known: mod_unique_id: unable to find IPv4 address of zoneApache
 Configuration Failed

 What could be the cause of this error?

Looks to me like something in mod_unique_id.so is calling
gethostbyname() to find the IP address or fully qualified name for
zoneApache.  My guess is that if you try getent hosts zoneApache it
will return nothing, suggesting a DNS or
/etc/{hosts,nsswitch.conf,resolv.conf} configuration problem.  Do your
debugging in the zone, not in the global zone.

-- 
Mike Gerdts
http://mgerdts.blogspot.com/
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Zone and Apache 2.2

2009-12-27 Thread godefroy montegommery
Wonderful, it works.  The hosts files in the global zone and the zoneApache 
zone were the same : 

# Internet host table 
#
::1 localhost
127.0.0.1   localhost loghost opensolaris

I changed opensolaris for zoneApache in the hosts file of zoneApache to 
solve the problem.

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