[zones-discuss] Simple question... An inherit-pkg-dir resource with the dir '/lib' already
I'm getting an error on trying to create a second zone. -bash-3.00# zonecfg -z test123 -f test123-zone-cmd.txt On line 7 of test123-zone-cmd.txt: An inherit-pkg-dir resource with the dir '/lib' already exists. resource specification incomplete Zone test123 failed to verify test123: Insufficient specification Configuration not saved. Here is the start of the command file: create set zonepath=/zones/test123 set autoboot=true set pool=test add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end I think this is probably a simple error. Does anyone know what I'm doing incorrectly? This is S10U4. Thanks, David This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Simple question... An inherit-pkg-dir resource with the dir '/lib' already
David Smith wrote: I'm getting an error on trying to create a second zone. -bash-3.00# zonecfg -z test123 -f test123-zone-cmd.txt On line 7 of test123-zone-cmd.txt: An inherit-pkg-dir resource with the dir '/lib' already exists. resource specification incomplete Zone test123 failed to verify test123: Insufficient specification Configuration not saved. Here is the start of the command file: create set zonepath=/zones/test123 set autoboot=true set pool=test add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end I think this is probably a simple error. Does anyone know what I'm doing incorrectly? When you just 'create' the zone it uses the default template which already has the standard inherit-pkg-dirs defined. If you want to define them yourself then you should use the 'blank' template. You can do that by changing 'create' to 'create -b'. You can read more about the create sub-command options in the zonecfg(1M) manpage. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] netmask warning, misconfiguration
Antonello Cruz wrote: I would definitely run zonecfg -z int-sagent-1-z1 info to check what the zone thinks is the netmask. Doesn't display a netmask. I suspect if you haven't defined the '/24' it will pick the default for the address class. In this case, '/16' IIRC. Sometimes documentation gets old... Sure seems like a bug. Did you use, in zonecfg: zonecfg:int-sagent-1-z1:net set address=172.20.46.188/24 ? No, no /24. (I see how that could affect the picture, but it seems like /etc/netmasks should work too, and the message certainly suggests it.) Actually, I just remembered that I didn't specify the address this way. I used set address=int-sagent-1-z1. (I don't like using IP addresses when I don't absolutely have to.) ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] netmask warning, misconfiguration
zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0. but my /etc/netmasks (on both the global and local zone) looks good: What does the netmasks entry in /etc/nsswitch.conf say? A common issue is that a user changes their local /etc/netmasks file but their the switch says to use something like nis. (I also tried 172.20.0.0 on the theory that maybe it wanted me to set the netmask for the entire Class B, but no dice.) Actually, that's exactly what you should be using in your local /etc/netmasks entry. Although I do suggest that specifying the prefix length (such as /24) via zonecfg(1M) is the best solution. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Can't install zone after 10_recommended
This was the problem. Thanks to Richard Lowe and Enda Oconnor for getting me on the right track and pointing me to the workaround. -Original Message- From: Richard Lowe [EMAIL PROTECTED] Sent: Nov 29, 2007 11:38 AM To: Mangan [EMAIL PROTECTED] Cc: zones-discuss@opensolaris.org Subject: Re: Can't install zone after 10_recommended Mangan [EMAIL PROTECTED] writes: 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? CR 6614543 sysidtool doesn't run in zones on systems pre u3 patched up to 120011-14 http://bugs.opensolaris.org/view_bug.do?bug_id=6614543 perhaps? -- Rich ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Shared-ip routing and VNI interface
On (11/30/07 08:25), Mike Gerdts wrote: The 10.1.1.100 address must not be reachable. The last time I tried this in Nevada it causes a panic. The last time I tried it on S10 it causes one kernel thread to spin (mpstat will show one CPU at 100% sys). Through bugs.opensolaris.org I opened a bug (6422863) but now I cannot see that bug through bugs.opensolaris.org. Anyone from Sun care to comment? That bug was fixed in SXDE 9/07 See also: http://unix.derkeiler.com/Newsgroups/comp.unix.solaris/2006-11/msg01251.html --Sowmini ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] netmask warning, misconfiguration
Jordan, How did you setup the IP address for that zone? Did you use, in zonecfg: zonecfg:int-sagent-1-z1:net set address=172.20.46.188/24 ? Antonello Jordan Brown (Sun) wrote: I get: zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0. but my /etc/netmasks (on both the global and local zone) looks good: 172.20.46.0255.255.255.0 (I also tried 172.20.0.0 on the theory that maybe it wanted me to set the netmask for the entire Class B, but no dice.) I see many instances of this message in BugTraq and Google searches, but I don't immediately see any resolutions. ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Simple question... An inherit-pkg-dir resource with the dir '/lib' alre
Thank you to everyone who replied so quickly... Basically the inherit-pkg-dir's are by default. Thanks, David This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Solaris Containers Replication
Hi Paul, 1. Clone them localy 2. Detach the Cloned Zones (zoneadm -z zonename detach) 3. Tar or pax them over starting from the zonepath and remote copy the tarballs or simply export/import SAN DG hosting the zones. 4. Prepare them for attachment, zonecfg -z zonename and at prompt create -a target-zonepath 5. Attach the Untared Zones on Target (zoneadm -z zonename attach) 6. Boot them. Make sure when you do all of the above that Source and Target servers are upto the same patch levels and all other resources (Network, SAN FS(s)) same as on source, otherwise you would be looking for troubles for reconciliations Ihsan Paul F Mazzola wrote: Need recommendation to determine the best way for replicating Solaris Containers. Here is the situation: (1) We built 4 containers for a customer on 2 different physical hosts. Root file systems are shared. (2) Customer installed all their applications, packages etc. Now customer wants us to replicate those 4 containers exactly as it is now so that on new containers they need not to install the apps/packages again. What is the best way to handle this case and replicate the containers within same or different physical hosts? -- NOTICE: This email message is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ zones-discuss mailing list zones-discuss@opensolaris.org -- ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] netmask warning, misconfiguration
Antonello Cruz wrote: zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0. How did you setup the IP address for that zone? Did you use, in zonecfg: zonecfg:int-sagent-1-z1:net set address=172.20.46.188/24 ? No, no /24. (I see how that could affect the picture, but it seems like /etc/netmasks should work too, and the message certainly suggests it.) ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Simple question... An inherit-pkg-dir resource with the dir '/lib' already
David Smith wrote: I'm getting an error on trying to create a second zone. -bash-3.00# zonecfg -z test123 -f test123-zone-cmd.txt On line 7 of test123-zone-cmd.txt: An inherit-pkg-dir resource with the dir '/lib' already exists. resource specification incomplete Zone test123 failed to verify test123: Insufficient specification Configuration not saved. Here is the start of the command file: create set zonepath=/zones/test123 set autoboot=true set pool=test add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end I think this is probably a simple error. Does anyone know what I'm doing incorrectly? This is S10U4. Hi you are creating a default zone so it already has lib inherited I suspect, also not sure if typo in above but add inherit-pkg-dir set dir=/platform add inherit-pkg-dir set dir=/sbin end missing an end there. But the defaul from create already has these libs /lib /sbin /platform and /sbin inherited already. Enda Enda Thanks, David 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] netmask warning, misconfiguration
[EMAIL PROTECTED] wrote: What does the netmasks entry in /etc/nsswitch.conf say? A common issue is that a user changes their local /etc/netmasks file but their the switch says to use something like nis. Bingo! Thanks! (I also tried 172.20.0.0 on the theory that maybe it wanted me to set the netmask for the entire Class B, but no dice.) Actually, that's exactly what you should be using in your local /etc/netmasks entry. I'm not sure, but reading netmasks(4) I don't think so. Note that it has an example entry: 128.32.27.16 255.255.255.240 and says that the system uses the longest prefix found. OTOH, I don't immediately understand how the example can work. It says that 128.32.*.* (except for the exclusions) gets a 24-bit netmask, but I don't see how that can be unambiguously determined. The example *seems* to want to explicitly specify a 28-bit netmask for several ranges and a 24-bit netmask for the rest, but how can it distinguish between requesting that 128.32.*.* is all 24-bit and requesting that 128.32.0.* is all 24-bit? (For that matter, why isn't it specifying that 128.001?.*.* is 24-bit?) Although I do suggest that specifying the prefix length (such as /24) via zonecfg(1M) is the best solution. Point-specifying a global value seems like the wrong answer. Normalization says that you should specify the global value in one place, not replicated across many. (Less abstractly, that you should specify the netmask in one place, not individually for each address that uses it.) ___ zones-discuss mailing list zones-discuss@opensolaris.org
