Error unpacking rpm package

[mared02]

:confused:
Taking a LUX5 appliance and Branch Class, Resized volumes, added a placeholder volume, made usr volume wr, connected net terminal to net applicance, created a volume and use as placeholder and saved it. Start application logged in and attempted to install httpd and received the following errors

Installing : apr 1/5
Error unpacking rpm package apr-1.2.7-11.el5_6.5.i386
error: unpacking of archive failed on file /usr/lib/libapr-1.so.0;4e8d4828: cpio: symlink
Installing : postgresql-libs 2/5
Error unpacking rpm package postgresql-libs-8.1.23-1.el5_6.1.i386
error: unpacking of archive failed on file /usr/lib/libecpg.so.5;4e8d4828: cpio: mkdir
Installing : mailcap 3/5
Error unpacking rpm package mailcap-2.1.23-1.fc6.noarch
error: unpacking of archive failed on file /usr/share/man/man4/mailcap.4.gz;4e8d4828: cpio: mkdir
Installing : apr-util 4/5
Error unpacking rpm package apr-util-1.2.7-11.el5_5.2.i386
error: unpacking of archive failed on file /usr/lib/apr-util-1: cpio: mkdir
Installing : httpd 5/5
Error unpacking rpm package httpd-2.2.3-53.el5.centos.1.i386
error: unpacking of archive failed on file /usr/bin/ab;4e8d4828: cpio: mkdir

Failed:
apr.i386 0:1.2.7-11.el5_6.5 apr-util.i386 0:1.2.7-11.el5_5.2
httpd.i386 0:2.2.3-53.el5.centos.1 mailcap.noarch 0:2.1.23-1.fc6
postgresql-libs.i386 0:8.1.23-1.el5_6.1

Complete!
Any help would be greatly appreciated.

Ed

[mared02]

I check the status of my usr volume and it is mounted - rw-excl
Ewing1 TEST4> volume info Edsnewapp.usr

Name : TEST4:Edsnewapp.usr
Comment :
UUID : 4f79499b-0bc2-4eb2-bcd6-23f45ccd0834
Size : 2.00 GB
State : ok
Filesystem : ext3
Partitions :
Partition Filesystem Size
par1 ext3 2.00 GB
Unused Space : 1.00 MB
Mount State : in_use
Mounted Device : none
Current Users : 1
Mount Attributes : rw-excl
Time Created : Thu 06 Oct 2011 12:41:54 AM EDT
Time Written : Wed 05 Oct 2011 11:43:06 PM EDT
Time Accessed : Thu 06 Oct 2011 03:49:05 AM EDT
Number Mirrors : 2
Mirrors :
Server State
srv1 ok
srv2 ok

But when I attempt to create dir under usr/ I receive a message that is mounted read only.

[PavelGeorgiev]

Ed,

When a volume is being assigned to an appliance, it is 'mounted' and the output of 'vol info' gives you the access that the appliance has on this volume. This has nothing to do with how the OS within the appliance will mount that volume, its just a low-level restriction in AppLogic. If a volume is mounted read-only (as reported by 'vol info'), there is nothing you can do within the appliance to modify it, it effectively appears as a read-only device. When it is mounted rw, then you can write to that volume from within the appliance.

The use of 'mount' in the output of 'vol info' is kind of ambiguos, which I guess is the reason for your confusion.

Once you have a volume passed as rw (which is what you have done when you modified the LUX5 boundary), you can write to it from within the appliance, but that volume is mounted ro by the OS (as this is what the fstab for LUX5 tells it to do).

To fix, either modify /etc/fstab in the appliance or 'mount -o remount,rw /usr'.

Cheers,
Pavel

[mared02]

Thanks Pavel!

Once I made the /usr rw in the OS. I was able to install httpd and php without receiving the " Error unpacking rpm package" messages. My confusion was in intrepretation of the Documentation -

Configure the Appliance Boundary
The boundary includes everything necessary to configure the appliance, bind it to data on external storage volumes and connect it to other appliances.

To set up the appliance to the designed boundary

Select the newly-minted appliance. Right-click on its shape and click Modify Boundary.
Change the class name to your chosen name for the appliance class.
Review other options on the General tab, in particular the size and color.
Make the changes needed on the Interfaces tab to match the set of terminals in the designed boundary.
Note: Verify the default interface is selected and the external interface is not selected.

Add user volumes on the Volumes tab if your appliance needs user volumes. Carefully choose the read-only and shared options -- usually they are either both off (read/write non-shared) or both on (read-only shared).
Add the properties on the Properties tab. Verify you have selected good defaults; mark properties that cannot have defaults as mandatory. Set property constraints, if needed. Review the Config Files and Resources tabs. If nothing sticks out as wrong, leave them alone -- you will return to them later. Specifically, don't add any config files that don't already exist on the volume, because this will prevent the appliance from starting.
Save your changes.
Important! If you plan to install new software on the appliance, in a sub-directory of the /usr directory, verify that the appliance common volume (named usr) is made writeable and non-shared (unclick the read-only and shared buttons in the Volumes tab of the class editor). This will allow you to write to the usr volume. (Before moving the appliance to the catalog, you will need to make the common volume read-only and shared again.)

I just assumed by making the usr volume within the Modify Boundry of the appliance would allow the install to write to the usr/ directory.

Thanks again,

Ed