SEO

Hi all,

I'm running a NIM master on AIX5.3 and try to build a SPOT for AIX52-01
from a lpp source same level. It works fine during the whole building
process (I'm using smitty). But after - when I look at the new spot
with lsnim -l spot - I get a warning:
0042-157 c_ckspot: unable to access the
"...usr/./lpp/bosinst/image.template" file
and several "missing" lines with
missing = "network boot image"

I do not find any solution and have no idea whats wrong? This file
mentioned in the warning isn't really there. I can copy it from the
server, but that isn't so fine, I think, and afterwards doing a nim -o
check spot reveals the next missing file/directory.
I can do any other spots from other OS levels and Maint.levels. So I
don't think its the nim master.
Could it be the lpp source is somehow corrupted? Or incomplete? But the
Builing process itself finishes sucessfully.

Anybody any idea?
Thanx in advance,
Sandy.

I don't have a solution for you but I have some related info about a
similar problem that might help you find what's wrong.

When you build the spot, smitty might say it finishes OK but you *HAVE*
to look at the whole output because you probably had an lpp that failed
to install, which probably "cancelled" the installation of other
important lpps for which that lpp was a dependency. For example, I had
this problem creating a 5.1 spot and when I looked at the output I
found this:

===================Begin Excerpt=====================
....
installp: The installation of the following filesets will be
CANCELLED because filesets upon which they depend are not
installed
(or not completely installed):

Fileset bos.sysmgt.nim.client 5.1.0.50 requires:
* bos.net.tcp.client 5.1.0.50

Fileset bos.sysmgt.nim.spot 5.1.0.50 requires:
* bos.sysmgt.nim.client 5.1.0.50
* bos.net.tcp.client 5.1.0.50
=============================End================== =====

I then searched a bit more and found that bos.net.tcp.client failed to
install:

=====================Begin Excerpt===========================
....
0513-065 The netstat Subserver has been added.
0513-065 The klogin Subserver has been added.
0513-065 The kshell Subserver has been added.
bos.net.tcp.client.config[559]: 36224 Signal 0
Cannot copy /etc/security/login.cfg to /tmp/inutmpfp3JEa/cfgcpy.32312.
Exiting with failure.

instal: Failed while executing the bos.net.tcp.client.config script.

../bos.net.nfs.client.post_i[26]: 36228 Signal 0
../bos.net.nfs.client.post_i[47]: 36232 Signal 0
../bos.net.nfs.client.post_i[62]: 36236 Signal 0
../bos.net.nfs.client.post_i[106]: 36242 Signal 0
0513-071 The biod Subsystem has been added.
0513-071 The nfsd Subsystem has been added.
0513-071 The rpc.statd Subsystem has been added.
0513-071 The rpc.lockd Subsystem has been added.
0513-071 The rpc.mountd Subsystem has been added.
0513-071 The automountd Subsystem has been added.
/usr/lib/instl/instal[1276]: 32334 Signal 0

installp: The installation has FAILED for the "root" part
of the following filesets:
bos.net.tcp.client 5.1.0.50

installp: Cleaning up software for:
bos.net.tcp.client 5.1.0.50

0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
0513-083 Subsystem has been Deleted.
../bos.net.tcp.client.unconfig[151]: 35168 Signal 0
Cannot copy /etc/security/login.cfg. /etc/security/login.cfg will
remain unchanged.

cleanup: Failed while executing the ./bos.net.tcp.client.unconfig
script.


installp: The installation has FAILED for the "root" part
of the following filesets:
bos.net.tcp.client 5.1.0.50

=============================End================== =====

As a result of all this, there was no way to create a boot image
because we're missing important things like bos.sysmgt.nim.spot and
bos.sysmgt.nim.client in the spot. Even though smitty said "OK", it
really is not OK. You can't blame it though because it shows a
disclaimer/warning in the beginning saying that we still have to look
at the ouput. Still, the whole spot is unusable and thus OK is
definitely not the correct status of the operation. Whatever.

The solution I found at the time was to create a spot from the /usr
filesystem of the master because for some reason I was not able to
build a good 5.1 spot from the bffcreate'd source I got from the 5.1
CDs even though the master was installed from the same CDs.

Hope that points you in the right direction.

--
lpc

Hi,

thanx for the answer. I had a look and there were almost exactly the
same errors while building the spot!
Our NIM master is unfortunetly already AIX 5.3, so I couldn't use its
/usr filesystem. But we find the cause!

In the lpp source of 5.2.base was a fileset kinda double. There was a
bos.sysmgt.5.2.0.0.I and a newer bos.sysmgt.5.2.0.0.I.1 - filesizes
different. No idea where the second came from, but after we deleted it
from the source the spot building went fine!
Maybe there was something similar in your case too?

Sandy.

Simply copy /etc/inetd.conf to your $SPOT_ROOT/usr/lpp/bos.net/inst_root/etc, then, you can successfully to create the SPOT.

as described in /usr/lpp/bos.net/inst_root/bos.net.tcp.client.config

#----------------------------------------------------------------
#CAREFUL : the blank pattern inside [] is a tab followed by a space
#----------------------------------------------------------------
# Defect 428588
# If this is a new install, the kshell and klogin will be added
# to /etc/inetd.conf, and be commented out.
# If this a migration, then if :
# entries existed, they remain in the same state
# entries did not exist, now they will and be commented out
#----------------------------------------------------------------

as I understood, because the inetd.conf under SPOT is created from refresh CD images (or equivalent media), it is neither created from new install, nor migration.

I am still testing my nim server, and see if this workaround really fix the problem or not.

Fei