Increase /var filesystem Solaris nine.

I was having an issue with my 5.9 solaris not booting up , this was due to /var being full. I was able to decrease /var and login. I notice I took the defaults when installing solaris 9 on a 40gb drive and only allowed 56mb of space for /var and 36gb for /export/home.
I'm not using LVM nor Veritas
The output of my /etc/vfstab is :
SunOS 5.9
login: root
Password:
Login incorrect
login: veverett
Password:
Last login: Wed Jan 18 14:41:45 from 10.0.0.5
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
$ more /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s3 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no -
/dev/dsk/c0t0d0s1 /dev/rdsk/c0t0d0s1 /var ufs 1 no -
/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /export/home ufs 2 yes -
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /opt ufs 2 yes -
swap - /tmp tmpfs - yes -
$
What would be the best course of action to decrease /export/home and increase /var by 6gb. This is a test box so I'm not concern about the amout of space for /export/home.
I would prob increase swap as well.
Thanks

Your system disk has already been organized. Increasing /var space is not done easily.
Is /var and /export/home created by SVM?
Show your df -h and disk partition information.
If the slices are organized without any free space, you may need to do a re-install with custom layour option.

Similar Messages

/var filesystem 100% full

I need some help here please, I cleared /var filesystem from all the big files but it's still showing me 100% full, I only manage to get rid of this problem when I reboot the server then /var becomes 3% full, any idea what's causing this to happen.
I want to avoid rebooting the server in future, should /var/ become full again
Many thanks

Some process still has the deleted file open, so the kernel cannot
free the space occupied by the file(s) you've delete.
The space is deleted as soon as the process closes the file handle
(e.g. by stopping / restarting the process).
The following command lists the process ids / file handles that
do not have filesystem links but are still referenced by a process
(you must run it as user root):
# find /proc/*/fd -type f -links 0 -ls

Unable to install gcc, says /var filesystem full

Hi,
when i am trying to intall gcc on solaris9, it says
NOTICE: alloc: /var: file system full
cpio: Cannot write "reloc/lib/libstdc++.a", errno 28, No space left on device
cpio: Cannot write "reloc/lib/libstdc++.so.5.0.5", errno 28, No space left on device
cpio: Cannot write "reloc/lib/libsupc++.a", errno 28, No space left on device
cpio: Cannot write "reloc/man/man1/cpp.1", errno 28, No space left on device
cpio: Cannot write "reloc/man/man1/gcc.1", errno 28, No space left on device
cpio: Cannot write "reloc/man/man1/gcov.1", errno 28, No space left on device
cpio: Cannot write "reloc/man/man7/fsf-funding.7", errno 28, No space left on device
cpio: Cannot write "reloc/man/man7/gfdl.7", errno 28, No space left on device
cpio: Cannot write "reloc/man/man7/gpl.7", errno 28, No space left on device
124787 blocks
when i try to check the disk free using df -h, i get output as
Filesystem size used avail capacity Mounted on
/dev/dsk/c0d0s0 149M 32M 103M 24% /
/dev/dsk/c0d0s6 1.3G 451M 784M 37% /usr
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
/dev/dsk/c0d0s1 52M 3.6M 43M 8% /var
swap 585M 12K 585M 1% /var/run
swap 585M 0K 585M 0% /tmp
i can see clearly tht my first slice which i have used for /var filesystem is not full. what might be the problem?
thanx in advance
regards
bushan.

hi,
I am having a similar problem while trying to install gcc...This is the error messg I get-
cpio: Cannot write "reloc/man/man7/gfdl.7", errno 28, No space left on device
cpio: Cannot write "reloc/man/man7/gpl.7", errno 28, No space left on device
210439 blocks
2 error(s)
pkgadd: ERROR: attempt to process datastream failed
    - process </usr/bin/cpio -icdumD -C 512> failed, exit code 2
pkgadd: ERROR: unable to unpack datastream
Installation of <SMCgcc342s> failed (internal error).
No changes were made to the system.But when I do a df - h it looks like I have enough space...then why am I getting this error?
bash-2.05$ df -h
Filesystem             size   used avail capacity Mounted on
/dev/dsk/c0t0d0s0      2.5G   2.3G   138M    95%    /
/proc                    0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
fd                       0K     0K     0K     0%    /dev/fd
swap                   3.6G   176K   3.6G     1%    /var/run
swap                   3.6G   456K   3.6G     1%    /tmp
/dev/dsk/c0t0d0s7       14G   2.5G    11G    19%    /export/home
/vol/dev/dsk/c1t6d0/networker_vol_1
                       464M   464M     0K   100%    /cdrom/networker_vol_1
/export/home/dupont     14G   2.5G    11G    19%    /home/dupontthanks,
R

Increase root filesystem size with VxVM

Hi All,
Can i increase the root fileystem size in solaris 10 after encapsulating the root disk into VxVM.
Thanks
---MGP---

I wouldn't try it.
If you have a mirror, I'd drop the mirror, copy everything over to the mirror disk (in normal, contiguous slices), then redo the VxVM encapsulation.
Root filesystem cannot be discontiguous, no concats, stripes, raid5s, only mirror. So growing is difficult unless the space is already past the end.
Easier to copy to another disk, reset the bits (/etc/system, /etc/vfstab), then boot from it.
Darren

Increase root filesystem in ldom

Hi
I have a ldom having a flat file /ldoms/ldom1-data in the backend used as a virtual disk c0d2s0 for data In the ldom .Now this virtual disk is running out of space in the ldom How can I increase the size of this filesystem in the ldom or my only option is to create another file of bigger size in the primary domian ,export it to the ldom as a new Virtual disk ,parttion it in the ldom and copy the data from the old disk to the new
Appreciate any inputs
TIA

Hello
I don't think you can do with sol10u6 without any patch, assuming that you don't have SVM just and slice
Solaris Does Not Automatically Handle an Increase in LUN Size (Doc ID 1382180.1)
How to expand a UFS Lun in Solaris 10 (Doc ID 1451858.1)
And the previous doc I gave you has the example for ufs too but with sol11, so mixing a bit all this docs I think you will be able to do, but first don't forget to do a backup just in case something goes wrong.
How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain (Doc ID 1549604.1)
—snip —
Procedure to increase size of a UFS filesystem based on SMI label in a guest domain running Solaris 11
Another way, is add a new LUN and do a mirror to a bigger LUN then remove the small LUN. (for this you need SVM or ZFS in the guest)
Regards
Eze

/var filesystem full according to df but not du command? How do you resolve this?

Environment is a 2 node cluster, one node is running Oracle DB and the other running Oracle AS. Node running Oracle AS has /var of about 9.9G. /var is an independent filesystem and not part of /. After rebooting or when there are no users accessing the application, /var is about 2.4G and this is reflected on both df and du commands. But afew minutes into application usage and that shoots up to 100% capacity utilization reflected in df -h command output but du still hovers around 2.4G. I know to resolve this scenario you look for open but deleted files i.e. files with a link count of 0 using
find /proc/*/fd -type f -links 0 | xargs du -k | sort -n
They are binary files, application related I suppose but when I view them with cat command I get to make out a few details in plain text. I decided to delete one as a test case and see if it affected any real data, surprisingly it did. How is this possible if link count is zero? Has anyone experienced such a scenario before? I can't apply the resolution to this problem without affecting data so am in quite a fix
Note: I know nothing about Oracle AS

user10980710 wrote:
Environment is a 2 node cluster, one node is running Oracle DB and the other running Oracle AS.
That's not a cluster. That's simply two different servers, each with its own distinct function.
Node running Oracle AS has /var of about 9.9G. /var is an independent filesystem and not part of /. After rebooting or when there are no users accessing the application, /var is about 2.4G and this is reflected on both df and du commands. But afew minutes into application usage and that shoots up to 100% capacity utilization reflected in df -h command output but du still hovers around 2.4G. I know to resolve this scenario you look for open but deleted files i.e. files with a link count of 0 using
find /proc/*/fd -type f -links 0 | xargs du -k | sort -n
They are binary files, application related I suppose but when I view them with cat command I get to make out a few details in plain text. I decided to delete one as a test case and see if it affected any real data, surprisingly it did. How is this possible if link count is zero? Has anyone experienced such a scenario before? I can't apply the resolution to this problem without affecting data so am in quite a fix
Note: I know nothing about Oracle AS
So where is the ASM question here? (This is the ASM forum). Looks to me like this would be better addressed in a Linux forum, of which there are several on the Web, both within OTN and outside.

Memory increase problem on Solaris

We need your help in understanding and solving a memory problem in one of our products running on Soalris. The server memory keeps growing and there is a fear of a server crash.
We've run our product with Purify and libumem to identify memory leaks. Both of these products didn't report any leak. So, we are very much confident that there are no memory leaks in the product. Still the memory increase is seen on Unix systems. We've done extensive analysis on this subject and absorbed some key points regarding memory management in Unix.
1) Memory doesn't shrink on Unix systems. This is for the libc to retain the released memory and reuse it for further memory requirements.
2) Based on the memory requirements to our application there can be a stabilization point where in the application can serve all memory requests.
After reaching this point the Server memory doesn't increase.But the fear is that it may exceed the hardware resources constraint.
3) Rapid increase in memory can be because of Memory Fragmentation problem. There are environmental variables like Small Block Allocator (_M_SBA_OPTS) and Arena (_M_ARENA_OPTS) on HP-Unix machines which can be used to address Fragmentation issues. We've performed some tests using these variables and found significant improvement in the usage of memory. This confirms that there are no memory leaks. These variables are specific to HP-Unix machines and we are unaware of similar variables/mechanism on Sun Solaris Platform. Please recommend some environmental variables/mechanism on Sun Solaris platform to solve fragmentation problem.
We are performing some tests to observe memory stabilization over a period of time .
The memory bloat is following a pattern. Memory is increasing in chunks of (MB) 2,4,8,16,32,64,128,256,512,1024 MB pattern.
For example if Memory increase is 64 MB, then it stabilizes for some time and the next increase would be 128 MB at a time.
Then it stabilizes for double the time consumed earlier for 64 MB and after that only increases by 256 MB.
So the memory increase and stabilization time are getting doubled each time. Please validate our analysis and kindly suggest what can be done on Unix platforms for solving this memory increase problem.

Thanks MaximKartashev for your inputs.
Ours is a Multithreading application. We are testing it with Hoard for the last three days. The observation so far has been that the performance of Hoard is high but the bloat pattern is not avoided.
Even with Hoard, memory bloat is following a pattern. Memory is increasing in chunks of (MB) 2,4,8,16,32,64,128,256,512,1024 MB pattern.
We are searching for other ways to control this pattern and stabilize the application by making it to reuse the fragmented memory completely.
We have also tried Solaris libgc memory allocator (http://developers.sun.com/solaris/articles/libgc.html). It worked well initially and memory drop was seen. But on heavy load, it crashed the application with 'Can't allocate header' error. So this can't be used for heavy load.
We are trying to use Boehm-Demers-Weiser Garbage Collector (http://www.hpl.hp.com/personal/Hans_Boehm/gc/). Do any one have idea, if it controls memory fragmentation ?

Merge /opt and /var filesystem.

We have Solaris 2.6 running on one of our production Servers(Sun E450).
For some reasons we need to merge /opt and /var partitions, so that we can free one slice for our use. What are the suggested methods in which this can be done with minimum downtime ? Also I would like to know the repercussions if any ?

Hi Ernesto,
Please check the timestamp for the crash files under /var. Delete the older ones as even the OS support group may not analyze any older crash dump files.
Or
Move these crash dump files to new location where you have enough space.
Regards,
Deepak Kori

Increasing kernel parameters Solaris

Hi,
actually i have these parameters and i need to increase them. Which will be the next values to be entered for those ones. Im using solaris 10 , oracle 10gR2.04.
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=2500
set semsys:seminfo_semmsl=1000
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=2500
Thx

Hi here i have answer for your query
if you want to set kernel parameters on solaris means
open the system file as vi /etc/system
and type the following at the end of file
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=2500
set semsys:seminfo_semmsl=1000
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=2500
save and exit
reboot your system
now your kernel parameters changed
okkkkkk

How to increase screen resolution Solaris 10

Hi,
Just installed S10..The monitor that I am using runs pretty high resolution but the highest option that I can choose is 1024x768...What is the easiest way to increase the selections?
Also where would I look to find audio drivers for this box? The speaker has a red line going through it...Speaker works fine with latest dev build of opensolaris, though...Thanks.

If you are mirroring the displays they will have the same resolution, if you are extending the displays you can have different resolutions for each display.

Solaris 9 - INIT: Cannot create /var/adm/utmpx (System Hangs)

Hello,
I am unable to boot into solaris 9 after I did a init 0. I did init 0 because shutdown -y -g0 -i0 did not work.
This is the error message I get
Hardware watchdog enabled
INIT: Cannot create /var/adm/utmpx
INIT: failed write of utmpx entry:" "
INIT: failed write of utmpx entry:" "
INIT: SINGLE USER MODE
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
After it asks for the password it HANGS.
I entered the password, but NOTHING HAPPENS.
I can go into sc console though.
I also rebooted using Solaris 9 cdrom in single user mode. Checked the filesystem using fsck, and no faults were found. I also tried creating a new /var/adm/utmpx file but that did not work too.
Any help would be appreciated,
Thank you,
Jacob.

Hello,
Check for /var filesystem usage,if it is not mouted as seperate filesystem then check for "/" FS usage.
There may be chances you get to have this problem if your FS is full.
If everything normal then follow the below steps, which solved similar kind of issues in the past for me.
Logon to the system and when you get prompt just run fsck on your root filesystem.
Check /etc/vfstab file to ensure that you are running fsck on correct fs name.
After completing fsck just say "reboot". The machine will boot normally.
In b/w is this machine disks are mirrored?? if so then you may need to choose the disks carefully before you run fsck.
thanks.

Increase root partition on ufs filesystem

Hello
we have a virtual solaris vm with ufs the disk has become to small..
we have increased the vmfs but we are having problems increasing the filesystem as format only sees the old size.. fdisk does not seem to offer the possibility to expand the partition to its maximum size.. is it possible to change the label of a solaris partition so that it takes into account all the space that is available for it?
why fdisk does not see there is unallocated space.. i could create a second partition and mount it to other directory perhaps.
thank you.

Hi.
Solaris on X86 system placed on special general dos partittion.
fdisk - used for first level. On this level you can create one ( and only one) partition with type Solaris
and can create some additional partitions for other OS.
format - used for second level. It create additional partittions on solaris's partitions on first level. This label also store original size of disk.
So you need:
1. Increase Solaris partition on first level, using fdisk
2. Check that format detect new size of disk and increase/create new.
In case mistake on any steps - you lost data.
This problem correspond only for root fs and UFS.
On my choice - create addtional virtual disk and just add it to system.
For new disk use gpt (efi) type of label.
Regards.

/var filesytem

Help!
My /var file keeps filling up and going higher and higher. It made it
up to 100%.
It seems to be increasing(as shown in df -k) 1 mb ever 10 minutes. I
restored the /var filesystem from last weeks backup and it still grows
until it reaches %100 capacity. I checked the /var/tmp and /var/dt
which both had today's dates but couldnt find what is filling up?
None of my other files are increasing.
Please advise asap how I can correct this problem?
I am on a Sun Sparc 20 with Solaris 2.6

Could it be that this machine is really often used?
because /var/adm/wtmpx is the file wich contains:
History of user access and administrative information...
the /var/adm/utmpx contains:
user access and administrative Information..
so if these files geting larger and larger there must be a problem.
I'm afraid i can't help you much more... because i never heard of that kind of problem so far..
Do you know which files exacly grew every 10 mins or is it a whole directory?

Issues w/ LiveUpgrade from Solaris 10 x86 06/06 to 08/07 w/ SVMmetadevices

Hello all...
I am trying to upgrade a system from Sol 10 x86 6/06 to 8/07. For this example, we'll assume the following:
* The system has only 2 disks mirrored with SVM
* There are 0 free slices/partitions
* /, /usr, /var are separate slices/filesystems/mirrors
* There are 6 metadbs on 50MB slices, three on each disk
I run the following lucreate command (after having made sure that the appropriate packages and patches exist on the system):
lucreate -c s10u2 -n s10u4 -m /:/dev/md/dsk/d110:ufs,mirror -m /:/dev/dsk/c0d1s0:detach,attach,preserve \
-m /usr:/dev/md/dsk/d120:ufs,mirror -m /usr:/dev/dsk/c0d1s3:detach,attach,preserve \
-m /var:/dev/md/dsk/d130:ufs,mirror -m /var:/dev/dsk/c0d1s4:detach,attach,preserveI can then run luupgrade and every indication leads me to believe that it worked. So, I activate the new BE and init 6 and attempt to boot to the new BE. The boot ends up failing citing that it cannot mount /usr. So, I can either reboot and lumount the filesystems or boot into failsafe mode and take a look at the vfstab. The /etc/vfstab looks fine with the new metadevices identified as the /, /usr, and /var filesystems. However, those metadevices are never initialized. When I look at /etc/lvm/md.cf on the source BE, those metadevices are initialized there. However, they are not initialized in the secondary BE.
Am I missing something somewhere? Wondering why SVM does not appear to be updated on the secondary BE to add/initialize the new metadevices in the secondary BE.
TIA,
Rick

Ok...update...
I have found that there are bugs with LU where it relates to SVM mirrored /'s and what not. So, I modified my approach to the upgrade and "deconfigured" the /, /usr, and /var mirrors. I then executed the the procedure as described in the docs to create a new boot environment on the secondary disk. It worked!
Great! With that done, I can then remove the old boot environment and remirror the /, /usr, and /var filesystems as it was prior to the LU procedure. Wrong answer! There were two problems, the first was fairly simple to overcome....
Problem 1) When attempting to delete the old BE, I would get the following error:
The boot environment <s10u2> contains the GRUB menu.
Attempting to relocate the GRUB menu.
/usr/sbin/ludelete: lulib_relocate_grub_slice: not found
ERROR: Cannot relocate the GRUB menu in the boot environment <s10u2>.
ERROR: Cannot delete the boot environment <s10u2>.
Unable to delete boot environment.Through some Googling, I found that apparently, the Solaris 10 LiveUpgrade is attempting to use a function in /usr/lib/lu/lulib that only exists in OpenSolaris (whatever happened to backporting functionality?). Ok...easy enough. Backup the library and copy it over from an OpenSolaris box. Done...and it worked, but only led to problem #2...
Problem 2) Now when I run ludelete on the old BE, I get the following error:
The boot environment <s10u2> contains the GTRUB menu.
Attempting to relocte the GRUB menu.
ERROR: No suitable candidate slice for GRUB menu on boot disk: </dev/rdsk/c0d0p0>
INFORMATION: You will need to create a new Live Upgrade boot environment on the boot disk to find a new candidate for the grub menu.
ERROR: Cannot relocate the GRUB menu in boot environment <s10u2>.
Unable to delete boot environment.I have attempted to manually move/install GRUB on the secondary disk and make it the active boot disk, all to no avail. ludelete returns the same error every time.
Thoughts? Ideas?
TIA,
Rick

Installing Solaris 11 on SunFIre T1000 With Automated Installer Server Fail

h4. Hi
h4. A few days i am try to intall solaris 11 11/11 on our server Sunfire T1000
h4. we first upgrade the firmware of the server to
sc> showhost
Sun-Fire-T1000 System Firmware 6.7.12 2011/07/06 20:03
Host flash versions:
OBP 4.30.4.d 2011/07/06 14:27
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:25
h4. And after we install Solaris 11 x86 on a laptop, in that we configure an AIS (Automated installer Server)
installadm list
Service Name Alias Of Status Arch Image Path
default-sparc s11-sparc on Sparc /install/images/s11-sparc
s11-sparc - on Sparc /install/images/s11-sparc
h4. We are using the default installations with a DHCP server in the Laptop
installadm list -m -p
Service Name Manifest Status
default-sparc orig_default Default
s11-sparc orig_default Default
h4. By the other side, in the sparc server (T1000) we use OBP for a WAN Boot Installation
boot net:dhcp - installl
2012-08-08 20:33:44,911 InstallationLogger DEBUG Starting Automated Installation
2012-08-08 20:33:44,913 InstallationLogger INFO Using XML Manifest: /system/volatile/ai.xml
2012-08-08 20:33:44,965 InstallationLogger INFO Using profile specification: /system/volatile/profile
2012-08-08 20:33:45,018 InstallationLogger INFO Using service list file: /var/run/service_list
2012-08-08 20:33:45,070 InstallationLogger INFO Starting installation.
2012-08-08 20:33:45,122 InstallationLogger DEBUG Registering Manifest Parser Checkpoint
2012-08-08 20:33:45,124 InstallationLogger DEBUG Engine registering:
2012-08-08 20:33:45,126 InstallationLogger DEBUG name: manifest-parser
2012-08-08 20:33:45,128 InstallationLogger DEBUG module_path: solaris_install.manifest.parser
2012-08-08 20:33:45,129 InstallationLogger DEBUG checkpoint_class_name: ManifestParser
2012-08-08 20:33:45,131 InstallationLogger DEBUG args: None
2012-08-08 20:33:45,133 InstallationLogger DEBUG kwargs: {'call_xinclude': True, 'manifest': '/system/volatile/ai.xml', 'validate_from_docinfo': True}
2012-08-08 20:33:45,135 InstallationLogger DEBUG insert_before: None
2012-08-08 20:33:45,136 InstallationLogger DEBUG log_level: None
2012-08-08 20:33:45,138 InstallationLogger DEBUG =============================
2012-08-08 20:33:45,142 InstallationLogger DEBUG Current checkpoint list:
2012-08-08 20:33:45,144 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,146 InstallationLogger DEBUG Executing Manifest Parser Checkpoint
2012-08-08 20:33:45,148 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,150 InstallationLogger DEBUG Executing Engine Checkpoints...+
2012-08-08 20:33:45,152 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,154 InstallationLogger DEBUG Engine will be executing following checkpoints:+
2012-08-08 20:33:45,155 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,157 InstallationLogger DEBUG Spawning InstallEngine execution thread
2012-08-08 20:33:45,160 InstallationLogger DEBUG Loading manifest-parser checkpoint
2012-08-08 20:33:45,213 InstallationLogger.manifest-parser DEBUG Initializing ManifestParser (manifest=/system/volatile/ai.xml, Validate_from_docinfo=True, dtd_file=None, load_defaults=True, call_xinclude=True)
2012-08-08 20:33:45,273 InstallationLogger DEBUG manifest-parser: prog est-1, prog ratio-0.95, total_ratio-1.00
2012-08-08 20:33:45,275 InstallationLogger DEBUG Last checkpoint, manifest-parser: prog ratio 0.95
2012-08-08 20:33:45,279 InstallationLogger DEBUG Snapshotting DOC to /var/run/install_engine/engine.MYk67H/.data_cache.manifest-parser
2012-08-08 20:33:45,286 InstallationLogger DEBUG Executing manifest-parser checkpoint
2012-08-08 20:33:45,288 InstallationLogger.manifest-parser DEBUG ManifestParser.execute(dry_run=False) called
2012-08-08 20:33:45,290 InstallationLogger.manifest-parser DEBUG ManifestParser.parse(doc=-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)
     -> [persistent] (DataObjectCacheChild: persistent)
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)
     -> [volatile] (DataObjectCacheChild: volatile)
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)) called
2012-08-08 20:33:45,292 InstallationLogger.manifest-parser DEBUG loading manifest (dtd_validation=True)
2012-08-08 20:33:45,872 InstallationLogger.manifest-parser DEBUG Parsed XML document:
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="orig_default" auto_reboot="false">
<target>
<logical noswap="false" nodump="false">
<zpool name="rpool" is_root="true" action="create">
<filesystem name="export" mountpoint="/export" action="create" in_be="false"/>
<filesystem name="export/home" action="create" in_be="false"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
<software type="IPS">
<destination>
<image action="create" index="false">

<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
h4. When the installation precess is in this part
13% target-selection completed.
17% ai-configuration completed.
19% target-instantiation completed.
19% Beginning IPS transfer
Creating IPS image
Installing packages from:
solaris
origin: http://pkg.example.com/solaris/
h4. in the install_log file show us this errors:
2012-08-08 20:51:39,653 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/doctools ...
2012-08-08 20:51:43,156 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/core-os ...
2012-08-08 20:52:03,704 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/less ...
2012-08-08 20:52:03,788 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/management/rad/module/rad-smf ...
2012-08-08 20:52:03,835 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/library ...
2012-08-08 20:52:30,609 InstallationLogger.generated-transfer-1184-1 DEBUG Cleaning up
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 359, in execute
self._transfer()
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 639, in _transfer
self.api_inst.prepare()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021, in prepare
self._img.imageplan.preexecute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 2827, in preexecute
p.download()
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 406, in download
mfile.wait_files()
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 2857, in wait_files
self._transport._get_files(self)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 432, in wrapper
return f(instance, fargs, *f_kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1736, in getfiles
self._get_files_list(mfile, filelist)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1685, in getfiles_list
raise tfailurex
TransportFailures: 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:30,731 InstallationLogger DEBUG Checkpoints Completed: DOC:+
-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)+
     -> [persistent] (DataObjectCacheChild: persistent)+
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)+
          -> [Engine-DOC-Root-Node] (<solaris_install.engine.EngineData object at 0xecc930>)+
               -> [manifest-parser] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee10d0>)+
               -> [target-discovery] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1230>)+
               -> [target-selection] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee12f0>)+
               -> [ai-configuration] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1410>)+
               -> [var-shared-dataset] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1c30>)+
               -> [target-instantiation] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1750>)+
          -> [discovered] (<solaris_install.target.Target object at 0xee1330>)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=False)+
                    -> [0] (Slice: name=0; action=preserve, force=False, is_swap=False, tag=2, flag=0, in_use={'used_by': ['exported_zpool'], 'used_name': ['rpool']}; size=148.99gb; start_sector=4768)+
                    -> [2] (Slice: name=2; action=preserve, force=False, is_swap=False, tag=5, flag=1; size=148.99gb; start_sector=0)+
               -> [logical] (Logical: noswap=True; nodump=True)+
          -> [desired] (<solaris_install.target.Target object at 0xede3f0>)+
               -> [logical] (Logical: noswap=False; nodump=False)+
                    -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=['c2t0d0s0'])+
                         -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                         -> [export/home] (Filesystem: name=export/home; action=create)+
                         -> [solaris] (BE: name=solaris; mountpoint=/a)+
                         -> [vdev] (Vdev: name=vdev; redundancy=none)+
                         -> [swap] (Zvol: name=swap; action=create; use=swap; size=1024m)+
                         -> [dump] (Zvol: name=dump; action=create; use=dump; size=512m)+
                         -> [var] (Filesystem: name=var; action=create; mountpoint=/var)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=True)+
                    -> [0] (Slice: name=0; action=create, force=True, is_swap=False, tag=2, flag=0; in_zpool=rpool; in_vdev=vdev; size=148.99gb; start_sector=4768)+
     -> [volatile] (DataObjectCacheChild: volatile)+
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)+
          -> [orig_default] (ai_instance: name='orig_default' auto_reboot=False; http_proxy='None')+
               -> [target] (<solaris_install.target.Target object at 0xee1d30>)+
                    -> [logical] (Logical: noswap=False; nodump=False)+
                         -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=[None])+
                              -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                              -> [export/home] (Filesystem: name=export/home; action=create)+
                              -> [solaris] (BE: name=solaris)+
               -> [generated-transfer-1184-1] (<solaris_install.transfer.info.Software object at 0xee1f30>)+
                    -> [transfer] (<solaris_install.transfer.info.IPSSpec object at 0xecc050>)+
                    -> [destination] (<solaris_install.transfer.info.Destination object at 0xecc0b0>)+
                         -> [image] (<solaris_install.transfer.info.Image object at 0xecc130>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc150>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc1b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc210>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc270>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc2d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc330>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc390>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc3f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc450>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc4b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc510>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc570>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc5d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc630>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc690>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc6f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc750>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc7b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc810>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc870>)+
                              -> [img_type] (<solaris_install.transfer.info.ImType object at 0xee1b70>)+
                    -> [source] (<solaris_install.transfer.info.Source object at 0xecc8b0>)+
                         -> [publisher] (<solaris_install.transfer.info.Publisher object at 0xecc8f0>)+
                              -> [origin] (<solaris_install.transfer.info.Origin object at 0xecc910>)+
          -> [transfer-zpool-cache] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee18f0>)+
          -> [transfer-ai-files] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee15b0>)+
2012-08-08 20:52:30,747 InstallationLogger DEBUG Checkpoints Completed: DOC (xml_format):
<root>
<target name="discovered">
<disk whole_disk="false">
<disk_name name="c2t0d0" name_type="ctd"/>
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>
<disk_keyword key="boot_disk"/>
<slice name="0" action="preserve" force="false" is_swap="false">
<size val="312456576secs" start_sector="4768"/>
</slice>
<slice name="2" action="preserve" force="false" is_swap="false">
<size val="312461344secs" start_sector="0"/>
</slice>
</disk>
<logical noswap="true" nodump="true"/>+
</target>+
<target name="desired">+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
<vdev name="vdev" redundancy="none"/>+
<zvol name="swap" action="create" use="swap">+
<size val="1024m"/>+
</zvol>+
<zvol name="dump" action="create" use="dump">+
<size val="512m"/>+
</zvol>+
<filesystem name="var" action="create" mountpoint="/var" in_be="true"/>+
</zpool>+
</logical>+
<disk whole_disk="false">+
<disk_name name="c2t0d0" name_type="ctd"/>+
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>+
<disk_keyword key="boot_disk"/>+
<slice name="0" action="create" force="true" is_swap="false" in_zpool="rpool" in_vdev="vdev">+
<size val="312456576secs" start_sector="4768"/>+
</slice>+
</disk>+
</target>+
<ai_instance auto_reboot="false" name="orig_default">+
<target>+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
</zpool>+
</logical>+
</target>+
<software name="generated-transfer-1184-1" type="IPS">+
<software_data>+
<name>pkg:/entire@latest</name>+
<name>pkg:/group/system/solaris-large-server</name>+
</software_data>
<destination>
<image img_root="/a" action="create" index="False">
<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
</software>
</ai_instance>
</root>
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
2012-08-08 20:52:31,012 InstallationLogger ERROR
2012-08-08 20:52:31,064 InstallationLogger ERROR 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2012-08-08 20:52:31,117 InstallationLogger ERROR 2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
2012-08-08 20:52:31,169 InstallationLogger ERROR 3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
2012-08-08 20:52:31,222 InstallationLogger ERROR 4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
2012-08-08 20:52:31,274 InstallationLogger ERROR 5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
2012-08-08 20:52:31,326 InstallationLogger ERROR 6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
2012-08-08 20:52:31,379 InstallationLogger ERROR 7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
2012-08-08 20:52:31,431 InstallationLogger ERROR 8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:31,484 InstallationLogger ERROR
2012-08-08 20:52:31,536 InstallationLogger INFO Automated Installation Failed. See install log at /system/volatile/install_log
2012-08-08 20:52:31,588 InstallationLogger DEBUG Shutting down Progress Handler
h4. Is something about:
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
h4. Somebody knows about this error?

The chash failures indicate that either the repository you're using has corrupt content for those files, or the files are being corrupted on download. The latter is more likely, usually a result of badly-behaved http proxies.

Increase /var filesystem Solaris nine.

Similar Messages

Maybe you are looking for