Originally posted by: kristianmilos

Hi All,

I recently upgraded my AIX install from AIX 6100-01 to 6100-06-04 using multibos. The upgrade went fine, and all software packages have been committed. My issue at the moment is with creating WPAR's from the new environment.

(GLOBAL)# mkwpar -A -g testvg -n testwpar1 -r -N address=<ipaddress>

Looking at the log file, I see a bunch of permission issues:

bos.rte.security.post_u98: bos.rte.security.unpost_u: 0403-005 Cannot create the specified file.
chmod: bos.rte.security.unpost_u: The file system has read permission only.
The file system has read permission only.
bos.rte.security.post_u104: bos.rte.security.unpost_u: 0403-005 Cannot create the specified file.
The file system has read permission only.
...
Now, I can still clogin into the wpar, and it displays the correct oslevel. I just wanted to work out if the file permission errors are issues with the Global environment, or something in the creation of the WPAR itself.

Any ideas?

Regards,
Kristian
#AIX-Forum

Originally posted by: nagger

Hi,
I think we have always had these warning messages and similar things, perhaps you never noticed them or there are more or different ones with newer AIX TL levels.

What I think is happening is some install script, that is used to build the WPAR is also used for an AIX install procedure. This tries to chmod a file that, in the WPAR, is now read-only as the WPAR has read-only access to /usr and /opt. So the operation fails - but the file in the Global area is actually OK - it was setup right as part of the Global AIX install.

These are warning and not errors.
I guess the install scripts could check before trying the chmod but the AIX developers don't like meddling with important code that is vital to all AIX installs and WPARs due to the stability and retesting efforts involved (if it ain't broken don't fix it) and its only a warning. Personally, I want them to code exciting new features than spend days fixing and testing a warning message.

So don't worry, I hope this helps you, Nigel Griffiths.
#AIX-Forum

Originally posted by: kristianmilos

Thanks for the follow up Nigel.
#AIX-Forum