Build Solaris 8 branded zone with ufs /var etc
We have an ancient application which runs on Solaris 8 which we would like to move to a Branded zone. The issue we have is that the application does a fstyp (but within the binary) on any file system that its is writing to and barfs if it doesn't recognise the type. Unfortunately we are limited to basically ufs and vxfs.
The problem is that I need to have /var configured as a UFS filesystem during the zone build ......
Now I know all of the methods that can be used to mount a filesystem within a branded zone:
1) Add FS within zonecfg ... fstype doesn't return UFS
2) LOFS : Doesn't return UFS
3) Mounting a file system after zone boot .... Great for non-system filesystems but not for /var
4) "add device" ... might work BUT I need to build /var during zone configuration .,.....
Any ideas?
Edited by: user13012897 on Dec 8, 2010 5:41 AM
It's not straightforward, but I'd consider writing an interposer library that gets loaded via LD_PRELOAD and gives a different answer than fstyp() would normally give.
http://www.itworld.com/UIR000929interposers
Similar Messages
-
[Solved] Arch Linux in a Solaris branded Zone
Hello,
After having read this article at the Genunix WiKi, I 'd very much like to install Arch Linux (http://204.152.191.100/wiki/index.php/I … anded_zone) in a Solaris branded Zone. However, the Arch Linux file to download is about two years old now, so I 'd like to roll one with a bit more recent kernel.
I just wonder what might be the procedure to do so.
a) Is it just unpacking the ISO inside the zone and let it enroll whilst booting?, or
b) is it advisable to install the old package and upgrade from there?
I am quite curious to learn how this works.
TIA, Algey
Last edited by algernonz (2011-11-28 18:42:31)Hi,
it does indeed sound like an interesting little project. You should, however, revert to your procedure (a) and use one of the recent ISO images the Arch team has updated this year.
Using that old tar will give you numerous headaches when trying to upgrade. Doing a simple upgrade from that old file will most probably break the system, thats why they took the effort to provide the new ones.
Good luck. -
Cannot create solaris 10 zone with flar archive
Hello,
i'm trying to configure a solaris zones with a flar archive of a solaris 10 system.
i've followed the procedure described here : http://www.sun.com/bigadmin/content/submitted/branded_zones_flash.jsp
whenever i try to create a zone and use: set brand=solaris10 the commit will fail with Unknown brand Missing document.
solaris version is Solaris 10 5/08 s10s_u5wos_10 SPARC and i have both the Solaris 8 and Solaris 9 container software installed.
is there another way to install a zone with the native brand or solaris 10 using an archive of some sort?
kind regards,Thanks,
I've figured as much as using a whole root zone but i still struggle with the configuration of a solaris10 brand and the creation of a zone config with that brand.
I might be bettor of installing the zone without the flar image and try to copy the needed files and applications to the zone.
I only need the solaris10 brand zone to test the flar image so i can use it to restore the system with flar and jumpstart. -
Solaris Branded Zones, Unable to reboot/Halt
Hi People,
Hoping someone can help. Im running Solaris 10 on a Sun Workstation Ultra 45. I have two disks. One disk has the default install of solaris 10 all updated to the latest patches.The second disk is mounted as /zones and holds each of the zones on ZFS. I have then downloaded and installed successfully Solaris 8 and Solaris 9 and Solaris 10 zones. So I have 3 zones.
The problem I am facing is I can boot up all 3 zones fine and they work great, however when I halt or reboot either Solaris 8 or solaris 9, they never come back up. I try and zlogin to them and telnet and ssh and they are totally unresponsive and quite literally dont boot. I have tried to pkill -9 -z zonename ; umount /zonesfilesystem; zpool clear and even rebooted the Global zone. Still will not come up. The only way they will boot after being shutdown is if i shutdown the global zones and turn the server off and back on.
Solaris 10 Zone boots up and down fine with no isses. I have tried this on both UFS and ZFS thinking it might be a file lock issue. Still unable to reboot or halt a zone and bring it back up.
Any help please :)
Thanks in advance.When they are unable to come back up, what does 'zoneadm list -cv' say? If the state of the zone is "down" or "shutting_down", you can probably benefit from the fix for:
7038404 outstanding zone references should not cause zone_destroy(2) to hang
This is available in 147440-05 (sparc) / 147441-05 (x86) or later. -
Hi all,
When you create a zone though Ops Center does it try and format the file system as ZFS? Can you make a Zone with a UFS?
Thanks,
ShawnHi Shawn,
Ops Center can manage existing "brownfield" zones on other filesystems (i.e. UFS)... but any new ones that you have it create will be on ZFS (see here: http://wikis.sun.com/display/EM11gOC1/Creating+Zones)
Regards,
[email protected] -
Unstable network in zone with exclusive IP.
Hi,
I have a Solaris 9 zone with exclusive ip, host (global zone) is Solaris 10 (Oracle Solaris 10 9/10 s10s_u9wos_14a). Server is V480 (4 CPU, 16GB ram).
What I do:
1. boot my zone.
2. ping zone & host from another computer.
When I have answer from zone (S9) - host (S10) is down (no ping), when I have answer from S10 - S9 is down... Up/down interval ~ 10-15 sec.
Any idea?
zone cfg:
zonecfg -z z1 info
zonename: z1
zonepath: /33g/z1
brand: solaris9
autoboot: false
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
[cpu-shares: 2]
fs:
dir: /mnt
special: /mnt
raw not specified
type: lofs
options: [nodevices,logging]
net:
address not specified
physical: ce1
defrouter not specified
attr:
name: machine
type: string
value: sun4u
rctl:
name: zone.cpu-shares
value: (priv=privileged,limit=2,action=none)Hello,
# dladm show-dev
ce0 link: up speed: 100 Mbps duplex: full
---- zone z1 ce1 link: up speed: 100 Mbps duplex: full
--- global ce2 link: up speed: 1000 Mbps duplex: full
ce3 link: up speed: 100 Mbps duplex: full
Wow, MAC duplicated (from test host):
v480 (192.168.1.7) at 00:03:ba:2c:9a:48 [ether] on eth2
z1 (192.168.1.166) at 00:03:ba:2c:9a:48 [ether] on eth2
For test, I was plumbed all interfaces in global zone:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
zone cnf9
inet 127.0.0.1 netmask ff000000
ce0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 5
inet 0.0.0.0 netmask 0
ether 0:3:ba:2c:9a:48
ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:3:ba:2c:9a:48
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.7 netmask ffffff00 broadcast 192.168.1.255
ether 0:3:ba:2c:9a:48
ce2:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
zone cnf9
inet 192.168.1.140 netmask ffffff00 broadcast 192.168.1.255
ce3: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 0.0.0.0 netmask 0
ether 0:3:ba:2c:9a:48
All ifs has one MAC! How it possible??
# eeprom local-mac-address?
local-mac-address?=false
Im set it to true & restart server....
Yes!!! Its work ;)
# prtconf -pv |grep local-mac-address
local-mac-address?: 'true'
local-mac-address: 0003bacf.520c
local-mac-address: 0003bacf.520d
local-mac-address: 0003ba2c.9a49
local-mac-address: 0003ba2c.9a48
bash-3.00# ifconfig ce0 plumb
bash-3.00# ifconfig ce1 plumb
bash-3.00# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 0.0.0.0 netmask 0
ether 0:3:ba:cf:52:c
ce1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:3:ba:cf:52:d
ce2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.7 netmask ffffff00 broadcast 192.168.1.255
ether 0:3:ba:2c:9a:49
from test host arp table:
v480 (192.168.1.7) at 00:03:ba:2c:9a:49 [ether] on eth2
z1 (192.168.1.166) at 00:03:ba:cf:52:0d [ether] on eth2
Just more info here
[Why do all my ethernet interfaces have the same ethernet MAC address?|http://www.sun-rays.org/lib/sunsolve/16733.html]
Nik, thank you very much ! ;) -
Parameters maintenance for Oracle 10.2.0.4 on Solaris 10 zone
Hi!
We use SAP Solution Manager 7.0 on Solaris 10 Zone with Oracle.
We have updated Oracle from 10.2.0.2 to 10.2.0.4.
What are the parameter recommendation for Oracle 10.2.4?
What is the approach to do this?
Thank you very much!
regards
Thom> Does the SAP installation usually include the setup of oracle parameters?
partly.
> Is there some automatic report that check and set up the valeus to the rigtht values, e.g. according to SAP note 830576?
No. Many of those parameters (the events mainly) depend on specific patches that need to be installed to activate them. Did you apply all the interim patches for 10.2.0.4 or just that patch?
> What are the crucial/important parameters?
all of them are more or less important. Oracle is a complex beast.
> If not, what are the technical steps to do this manually?
You can use brtools to change them one by one - or write a script like the following. However, this implies that all single/interim/cumulative patches are installed, not only 10.2.0.4.
Check note 1137346 - Oracle Database 10g: Patches for Release 10.2.0.4 for the single patches and read all the linked notes to the patches so you can built your own script to set the parameters.
This is an example script for HP-UX but you could use a likewise one for Solaris:
alter system set
event='10027 trace name context forever, level 1',
'10028 trace name context forever, level 1',
'10183 trace name context forever, level 1',
'10191 trace name context forever, level 1',
'10629 trace name context forever, level 32',
'10891 trace name context forever, level 1',
'14532 trace name context forever, level 1',
'38068 trace name context forever, level 100',
'38085 trace name context forever, level 1',
'38087 trace name context forever, level 1',
'38095 trace name context forever, level 1',
'10411 trace name context forever, level 1',
'44951 trace name context forever, level 1014',
comment='M. Doehr 16.09.2008'
scope=spfile
alter system set HP_UX_SCHED_NOAGE = 178
alter system set open_cursors = 1500 scope=spfile;
alter system set optimizer_index_caching = 50 scope=spfile;
alter system set optimizer_index_cost_adj = 20 scope=spfile;
alter system set parallel_max_servers = 40 scope=spfile;
alter system set query_rewrite_enabled = 'false' scope=spfile;
alter system set star_transformation_enabled = 'true' scope=spfile;
alter system set "_b_tree_bitmap_plans" = false scope=spfile;
alter system set "_bloom_filter_enabled" = false scope=spfile;
alter system set "_fix_control" = '5705630:ON',
'5765456:7',
'6221403:ON',
'6440977:ON',
'6626018:ON',
'6972291:ON'
scope=spfile;
alter system set "_index_join_enabled" = false scope=spfile;
alter system set "_optim_peek_user_binds" = false scope=spfile;
alter system set "_optimizer_mjc_enabled" = false scope=spfile;
alter system set "_sort_elemination_cost_ratio" = 10 scope=spfile;
alter system set "_table_lookup_prefetch_size" = 0 scope=spfile;
alter system set "_in_memory_undo" = false scope=spfile; -
Solaris Express Zone install error with SUNWiiimr and SUNWcnetr
Hi all,
I got these errors when installing a new zone on a Solaris Express 1/08 (5.11) on a x64 box:
Installation of these packages generated errors: SUNWiiimr
Installation of these packages generated warnings: SUNWcnetr
The zone creation log shows:
*** package -SUNWiiimr- failed to install with fatal errors:
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postin stall: /export/zones/newzone/root/lib/postrun: not found
/export/zones/newzone/root/var/sadm/pkg/SUNWiiimr/install/postinstall: /export/zones/newzone/root/lib/postrun: not found
pkgadd: ERROR: postinstall script did not complete successfully
Installation of -SUNWiiimr- on zone -newzone- failed.
*** package -SUNWcnetr- installed with warnings:
pkgadd: ERROR: unable to create package object -/export/zones/newzone/root/etc/dladm-.
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/aggregation.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/linkprop.conf- failed
owner name -dladm- not found in passwd table(s)
ERROR: attribute verification of -/export/zones/newzone/root/etc/dladm/secobj.conf- failed
owner name -dladm- not found in passwd table(s)
Installation of -SUNWcnetr- on zone -newzone- partially failed.
-newzone- was configured to be a whole root zone. Are there any ways to solve these installation errors?
Thanks in advance.This problem seems some strange - this time with Solaris 10u4, from 10 containers installed on a brand new X2200 (2x cpu) only one do not output those errors, but just this one cannot install the dsee or proxy. This time the errors were from:
Installation of <SUNWxwplr> on zone <dsee-proxy> partially failed.
Installation of <SUNWdtdmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWmconr> on zone <dsee-proxy> partially failed.
Installation of <SUNWrmwbr> on zone <dsee-proxy> partially failed.
Installation of <SUNWlvmr> on zone <dsee-proxy> partially failed.
Installation of <SUNWzebrar> on zone <dsee-proxy> partially failed.
So the machine was, too, just installed. After several hours, anoter atempt to install a zone, this time just this one, returned no errors - and the dsee installed without any complains. All configurations were for whole root zones. Used was Solaris 10u4 with the most recent patch cluster applied. -
Solaris 10 Zone for Solaris 11.1 creation with template fails.
Hi,
We are trying to use the Oracle VM Template for Oracle Solaris 10 Zone to create a solaris 10 zone on a solaris 11.1 GZ
root@exsolh0005:/opt/scripts# ./solaris-10u11-sparc -v
This is an Oracle VM Template for Oracle Solaris Zones.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not
use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by
law for interoperability, is prohibited.
Version: 1.0.9.12
root@exsolh0005:/opt/scripts# ./solaris-10u11-sparc -p /rpool -a 10.83.128.35/24 -i net6 -z testzone
This is an Oracle VM Template for Oracle Solaris Zones.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not
use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by
law for interoperability, is prohibited.
IMAGE: ./solaris-10u11-sparc
ZONE: testzone
ZONEPATH: /rpool/testzone
VNIC: vnicZBI83273795
IP ADDR: 10.83.128.35
NETMASK: 255.255.255.0
DEFROUTER: 10.83.128.1
TIMEZONE: Europe/Copenhagen
Checking disk-space for extraction
Ok
Extracting in /opt/scripts/bootimage.8Ham6r ...
100% [===============================>]
Checking data integrity
Ok
Checking platform compatibility
The host and the image do not have the same Solaris release:
host Solaris release: 5.11
image Solaris release: 5.10
Will create a Solaris 10 branded zone.
Checking disk-space for installation
Ok
Installing in /rpool/testzone ...
100% [===============================>]
Attaching testzone
Problem attaching testzone.
More details in /var/sadm/install/logs/solaris-10u11-sparc.log
Cleaning up and exiting.
Friday, May 10, 2013 03:18:01 PM CEST: cleaning up
root@exsolh0005:/opt/scripts#
root@exsolh0005:/opt/scripts# cat /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:56 PM CEST] ==== Starting: /usr/lib/brand/solaris10/attach testzone /rpool/testzone -c /opt/scripts/bootimage.8Ham6r/sysidcfg.testzone ====
[Friday, May 10, 2013 03:17:56 PM CEST] Progress being logged to /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning datasets under rpool/testzone
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool/ROOT/zbe
[Friday, May 10, 2013 03:17:56 PM CEST] Log File: /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:57 PM CEST] Converting detached zone boot environment 'zbe'.
[Friday, May 10, 2013 03:17:57 PM CEST] Unmounting /rpool/testzone/root
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property zoned=on on rpool/testzone/rpool
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property canmount=noauto on rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property mountpoint=legacy on rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:01 PM CEST] Mounting boot environment in rpool/testzone/rpool/ROOT/zbe-0 at /rpool/testzone/root (including child datasets)
cannot open 'ERROR: Error: Command <zfs list -H -o name -t filesystem -r rpool/testzone/rpool/ROOT/zbe-0> exited with status 1': invalid dataset name
[Friday, May 10, 2013 03:18:01 PM CEST] ERROR: refresh of ERROR: Error: Command <zfs list -H -o name -t filesystem -r rpool/testzone/rpool/ROOT/zbe-0> exited with status 1 failed
[Friday, May 10, 2013 03:18:01 PM CEST] ERROR: Error: rpool/testzone/rpool/ROOT/zbe-0: No such dataset.
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning datasets under rpool/testzone
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool/ROOT/zbe
[Friday, May 10, 2013 03:18:01 PM CEST] Result: Attach Failed.
[Friday, May 10, 2013 03:18:01 PM CEST] Exiting with exit code 254
[Friday, May 10, 2013 03:18:01 PM CEST] ==== Completed: /usr/lib/brand/solaris10/attach testzone /rpool/testzone -c /opt/scripts/bootimage.8Ham6r/sysidcfg.testzone ====
Looks like a script bug..
Regards
ClausHello All,
I would love to know if someone has a solution to this as I am seeing a similar issue with a slightly different setup.
Solaris 8 and Netra 240. I get the same result with and without patches and finish scripts. After the jumpstart and the failed boot attempt from disk. I can boot from cd, copy the glm driver from the cd to disk, and then everything works as it should. Obviously this is not a solution but only a work around.
Is it something to do with the SCSI hardware architecture used in the *240s?
Edited by: Gareth_Mann on Oct 2, 2007 7:41 PM -
Inetd service/program crashes with core dump in Solaris 8 zone/container
I have developed a service in C that is launched from inetd when something comes on a specific port.
When a connection is opened to the port a core dump is created in the same directory where the executable file is located.
If you run the same service program from the command line everything is working perfect.
This is running in a Solaris 8 zone/container on a Solaris 10 machine.
Everything is set correctly in /etc/inetd.conf and in /etc/services.
I have even stripped down the program to a hello world program that is just printing a string to the screen and it is still crashing with a core dump.
# ldd test_srv
/usr/lib/secure/s8_preload.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1
The same service is running on a Linux machine and on a Solaris 10 machine without zones/containers without any problems.
Can you please help me figure out what am I missing. Is there something specific with zones/containers that should be set / configured?
Do I have to set some specific env. variables to work in a Solaris 8 zone/container environment or is it something very simple that I'm missing?Could you please examine the truss log and advice what the problem is and how to fix it?
(some lines deleted)
bash-2.03# truss -f -p 18361 #### /usr/sbin/inetd -s -t &
18361: poll(0xFFBFF528, 53, -1) (sleeping...)
18361: poll(0xFFBFF528, 53, -1) = 1
18361: accept(63, 0xFFBFF870, 0xFFBFF914, 1) = 3
18361: sigprocmask(SIG_BLOCK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
18361: fork() = 1921
1921: fork() (returning as child ...) = 18361
1921: sigprocmask(0, 0x00000000, 0xFFBFF600) = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600) = 0
1921: lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: close(3) = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600) = 0
1921: lwp_sigtimedwait(0xFFBFF668, 0xFFBFF528, 0x00000020) = 0
1921: sigaction(SIGHUP, 0xFFBFF528, 0xFFBFF500) = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF5F0, 0x00000010) = 0
1921: lwp_sigtimedwait(0xFFBFF508, 0xFFBFF458, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921: lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
1921: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
1921: fcntl(3, F_DUP2FD, 0x00000000) = 0
1921: close(3) = 0
1921: fcntl(0, F_DUP2FD, 0x00000001) = 1
1921: fcntl(0, F_DUP2FD, 0x00000002) = 2
1921: open64("/etc/.name_service_door", O_RDONLY) = 3
1921: fcntl(3, F_SETFD, 0x00000001) = 0
1921: door_info(3, 0xFF0C2748) = 0
1921: door_call(3, 0xFFBFF278) = 0
1921: close(67) Err#9 EBADF
1921: close(66) Err#9 EBADF
1921: close(65) Err#9 EBADF
1921: close(64) Err#9 EBADF
1921: close(63) = 0
1921: close(62) = 0
1921: close(12) = 0
1921: close(11) = 0
1921: close(10) Err#9 EBADF
1921: close(9) Err#9 EBADF
1921: close(8) Err#9 EBADF
1921: close(7) Err#9 EBADF
1921: close(6) Err#9 EBADF
1921: close(5) Err#9 EBADF
1921: close(4) Err#9 EBADF
1921: setrlimit(RLIMIT_NOFILE, 0xFFBFFD20) = 0
1921: xenix(398872, 0xFFBFF5E4, 0x00000040) = 38
1921: execve("/tmp/srv/t_srv", 0x0008B5FC, 0xFFBFFDA0) argc = 0
1921: getuid() = 0 [0]
1921: resolvepath("/usr/lib/ld.so.1", "/usr/lib/ld.so.1", 1023) = 16
1921: open("/var/ld/ld.config", O_RDONLY) = 3
1921: fstat(3, 0xFFBFF5E8) = 0
1921: mmap(0x00000000, 148, PROT_READ, MAP_SHARED, 3, 0) = 0xFF3E0000
1921: close(3) = 0
1921: stat("/usr/lib/libc.so.1", 0xFFBFF648) = 0
1921: resolvepath("/usr/lib/libc.so.1", "/usr/lib/libc.so.1", 1023) = 18
1921: open("/usr/lib/libc.so.1", O_RDONLY) = 3
1921: mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xFF340000
1921: mmap(0x00000000, 802816, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF200000
1921: mmap(0xFF200000, 703520, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF200000
1921: mmap(0xFF2BC000, 24772, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 704512) = 0xFF2BC000
1921: munmap(0xFF2AC000, 65536) = 0
1921: memcntl(0xFF200000, 113528, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
1921: close(3) = 0
1921: stat("/usr/lib/libdl.so.1", 0xFFBFF648) = 0
1921: resolvepath("/usr/lib/libdl.so.1", "/usr/lib/libdl.so.1", 1023) = 19
1921: open("/usr/lib/libdl.so.1", O_RDONLY) = 3
1921: mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921: mmap(0x00000000, 8192, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF330000
1921: mmap(0xFF330000, 2638, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF330000
1921: close(3) = 0
1921: stat("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", 0xFFBFF368) = 0
1921: resolvepath("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", "/usr/platform/sun4u-us3/lib/libc_psr.so.1", 1023) = 41
1921: open("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", O_RDONLY) = 3
1921: mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921: close(3) = 0
1921: mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFF320000
1921: dup(0) = 3
1921: llseek(0, 0, SEEK_CUR) Err#29 ESPIPE
1921: close(0) = 0
1921: fcntl(3, F_DUP2FD, 0x00000000) = 0
1921: close(3) = 0
1921: dup(1) = 3
1921: close(1) = 0
1921: fcntl(3, F_DUP2FD, 0x00000001) = 1
1921: close(3) = 0
1921: dup(2) = 3
1921: close(2) = 0
1921: fcntl(3, F_DUP2FD, 0x00000002) = 2
1921: close(3) = 0
1921: sys#177(0x00000080, 0xFFBFFB7C, 0xFF3F0518, 0x00000000, 0xFF3C2EF8, 0xFF2C0284) = 0x00000000 [0xFFBFFB7C]
1921: sys#227(0x00000006, 0x00000000, 0x0001ADF0, 0xFF3F0518, 0xFF3C3C18, 0xFF3C2670) = 0x0000000C [0x00000000]
1921: sys#227(0x00000002, 0x0000000C, 0x0000000E, 0xFFBFFCAE, 0x00000002, 0xFF3C2670) = 0x00000002 [0x00000000]
1921: Incurred fault #6, FLTBOUNDS %pc = 0xFF232E2C
1921: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921: Received signal #11, SIGSEGV [default]
1921: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921: *** process killed ***
18361: Received signal #18, SIGCLD, in poll() [caught]
18361: siginfo: SIGCLD CLD_DUMPED pid=1921 status=0x000B
18361: poll(0xFFBFF528, 53, -1) Err#4 EINTR
18361: lwp_sigtimedwait(0xFFBFF218, 0xFFBFF140, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF130, 0xFFBFF218, 0x00000010) = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFEF28) = 0
18361: poll(0xFFBFF528, 53, -1) (sleeping...)Thank you in advance -
Multithreading issue on Solaris 8 branded zone
Hi,
We are facing a multithreading problem in Solaris 8 container (branded zone) on Solaris 10.
The core file shows 2 LWPs for a single thread.
First LWP
(dbx) lwp
current LWP ($lwp) is l@1403
(dbx) print this->m_ThreadId->m_IdImpl.m_PosixId
this->m_ThreadId.m_IdImpl.m_PosixId = 1404U
Second LWP
(dbx) lwp
current LWP ($lwp) is l@1404
(dbx) print this->m_ThreadId->m_IdImpl.m_PosixId
this->m_ThreadId.m_IdImpl.m_PosixId = 1404U
Another point to note is that dbx returns 'MT support is disabled' for this program even though it has been built using the -mt option. The dbx version is Sun Dbx Debugger 7.5 2005/10/13.
As far as I have read, the Solaris 8 branded zone uses the alternate T2 thread library. Note also that this program is linked with the alternate thread library @ /usr/lib/lwp.
This alternate thread library is supposed to use the 1:1 thread model.
Can someone explain why are we then seeing 2 LWPs for a single thread ?
Thanks,
Best regards,
Raj IyerThis error messages are output by
cssd which is a input method of Japanese.
If you don't use Japanese input method cs00, you can stop it by following method.
# /etc/init.d/loc.ja.cssd stop
# mv /etc/rc2.d/S90loc.ja.cssd /etc/rc2.d/_S90loc.ja.cssd -
Add zfs volume to Solaris 8 branded zone
Hi,
I need to add a zfs volume to a Solaris 8 branded zone.
Basically ive created the zvol and added the following to the zone configuration.
# zonecfg -z test
zonecfg:test> add device
zonecfg:test:device> set match=/dev/zvol/dsk/sol8/vol
zonecfg:test:device> end
When I boot the zone it comes up ok but I am unable to see the device, nothing in format, /dev/dsk etc etc
Ive also tried to setmatch to the raw device as well to no avail.
Basically I have numerous zvols to add and dont really want a load of mount points from the global zone then lofs back to the local zone
Any ideas please??
Thanks...Thanks but that's why I created zfs volumes and newfs'ed them to create UFS and presented those to the zone.
In the end I just create a script in /etc/rc2.d and mounted the filesystems in there. -
Inetd services (telnet, rlogin ,rsh) in Solaris 9 Branded Zone
Hi,
I've got two Solaris 9 Branded Zones running on an M3000. They both use exclusive IP.
When I try and telnet, rlogin or rsh to either of my Solaris 9 zones from the other I get an error. With the r* commands I get a "Protocol error" message, and telnet just reports a terminated connection. I've tried Mr. Google, the results I get make sense for a physical host - i.e Protocol Error would occur if the server executable (in.rlogind, etc) was somehow messed up.
Just to complicate things slightly the exclusive IP NICs are on a physically separate switch from the other NICs.
I'd forgotten that with the Branded Zones some native features are actually handled by the underlying global zone (i.e. Solaris 10).
Anyway, has anybody else had this same problem and how did you resolve it?
Thanks
Tim Shaw.I found out that the services in the Global Zone had been disabled. Simply enabling them fixed the problem :)
-
How do I get from Branded Zones to "real" Solaris 10 Zones?
My head is beginning to spin! I am beginning to think I have been led down a blind alley.
We have vast numbers of old Solaris 8 systems that we want to consolidate on new hardware in Solaris 10 Zones. We have been bombarded with advice that the way to go is to move it first to Branded Zones, as a stepping stone, and then migrate/upgrade it from there to Solaris 10. So we have started on our journey.
We now have our first bunch of Solaris 8 containers happily installed and running. And yes, it was relatively easy and painless, and the tool support was good. But now what? What are the steps and tools that will make the second step, from Solaris 8 to Solaris 10?
Everything out there hints that it is supposed to be easy. But every time I try and spec out the steps for our teams to follow I come unstuck. Does Live Upgrade feature in this anywhere? (And if so, at what point does my zone lose its Brand identity?) Is there some way to use archives? (And if so, how do I only include the bits I need to move?) Is there something magic under the covers of the Zone administration commands? (And if so, what pulls in my Solaris 8 stuff?) Is there at least some tool somewhere that will capture the configuration I need and build me a new one?
If the answer is that I just define the new Zone by hand and re-install all my applications from scratch, then can somebody explain just what I have achieved so far, and in what way it can be construed as a "stepping stone"?Correct. But we have now invested in the time taken to learn about Branded Zones, do the migrations, teach the support teams how to manage them... Plus we are paying the subscription for the Branded Zone software. And we still have pure Solaris 8 applications staring end-of-support in the face. We could have made the same investment to re-install the applications in a real Solaris 10 Zone and make them work "properly". All the publicity tells me I've made my migration to Solaris 10 much easier, but I still can't see how I'm any nearer my end point.Here's where your losing it. There is no real distinction between what you call a normal Solaris 10 zone and a Solaris Branded 8 zone. They could have called it something else and you would still insist that somehow one is normal and one is not. There are a variety of Branded Zones. There's a Solaris 8, Solaris 9, and Linux Branded Zones. They differ from what you call "normal" zones in that you basically are adding an OS to the Base OS and are not just copying files from the Base OS. That's the only difference. In all other respects they are the same. The only differentiators is for a Branded Zone you are adding the files from some other OS, even if it's just an earlier version of Solaris.
How do you migrate from a Solaris 8 zone to a Solaris 10 zone. The same way that you moved from the Solaris 8 physical box to the Solaris 8 branded zone. The steps should be the same. Implicite_Order pretty much said the same thing.
You seem to have a hang up on the words "normal zone." Yea I know, you've spent time and money and educated everyone and now your looking for the payoff. As I already stated and has been echoed by I_O, contact the vendor to see if they have Solaris 10 support, if they do, create a zone on a dev box, do some testing, and then create the zone on the real box, do the install, migrate the data. Just as you already did from the Solaris 8 box. If they don't have a Solaris 10 specific version you can still setup a test box, create a "normal" zone, install the app and some test data, make sure it works, and then create the "normal" zone, install the app, migrate the data, and relax.
alan -
Created zone with defaults won't boot completely (Solaris 10, Update 1)
If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME STATUS PATH
0 global running /
7 foo running /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006
Maybe you are looking for
-
How can I change the name of devices associated with my Apple ID in iTunes?
We have 3 iPads and 4 iPhones in our family. All of the iPads show up on the list of devices associated with my Apple ID as simply "iPad". All of the iPhones show up simply as "iPhone", even though each device has a distinct name on the device itse
-
Error message in middle of sync
I keep getting error messages"ipod cannot be synced. The disk could not read from or written to" and "attempting to cop to the disk ipod failed. The device is not connected. I have a new touch 16G, using windows xp. Need help!
-
Hello. I'm posting in these forums because I really don't know where else to go. I have been trying for the past several days to figure out how to go about writing my program but to no avail. The project requires reading many lines each containing se
-
Getting a evdre error when trying to refresh data. When tried to process the application or optimize the application, getting the error Error message:: CreateOLAPCubeForApplication:CreateCube:Internal error: The operation terminated unsuccessfully. E
-
Send mail to external address using send mail step.
Hi all, I have one question. In a send mail step of workflow, when the recipient type is a Organizational Object and Org Unit, the mail is only sent to workplace? I would need to send the mail to external address from all users of Org Unit. Is possib