Clues I have, but solutions I don't, since NetView V4 is out of support.
When you close the NetView GUI, ovw sends shutdown requests via a call back
mechanism to each of its registered applications. It waits up to two minutes
for them to go away, and then just closes itself. So what is happening here is
that something xxmap is doing on shutdown is hanging or looping and he does not
go away. When his parent, ovw does go away, then xxmap gets re-parented by the
next higher process (This is standard UNIX behavior).
So what is wrong with xxmap that is won't close down? I don't know. You could
format the nettl logs and look to see if there are error messages for it in the
output (netfmt -f /usr/OV/log/nettl.LOG00 > formatted.LOG01 and then browse
that file). If you were working with Level 2 they would advise you to run a
tool they have called dbxprof, which attaches to a running process several times
in a short time interval and gets a stack trace so you can see what that
process is doing. dbxprof is just a script to run dbx -a <pid> multiple times,
so if you are familiar with that then you could do it yourself. But as NetView
V4 is already out of support, I don't know what good the information would do
you exactly. And your V4 system si not even at the latest code level, but in
fact two levels back:
Server V4 Client V4
U451880 (12/22/97) U451881 (12/22/97)
U453385 (09/01/98) U453386 (09/01/98)
U459387 (12/11/98) U459388 (12/11/98)
I thought we recommended that you apply the latest level of V4 to your system
before migrating, but as that is not my specialty, I suggest you call Support
and ask them about that (migration that is).
Good luck
James Shanks
Tivoli (NetView for UNIX) L3 Support
"David E. Dimond" <dimond@allina.com> on 07/28/99 02:19:27 PM
Please respond to dimond@allina.com
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: xxmap process incorrectly parented
Platform:
Server = 7025-F50 w/AIX 4.2.1 - nv6000.base.obj 4.1.2.0.U451880
Client = an old 390 w/AIX 4.2.1 - nv6000.client.obj 4.1.2.0.U451881
I have four clients that installed with out a hitch. Prior to
installing v5.1.1 (which currently resides in a box under my desk),
I decided to install one more client. This one also went well with
one exception:
Exiting the GUI strands the xxmap process, and subsequent startups
(using the command 'nv6000') produce the following error message:
WARNING: One or more processes are incorrectly parented.
PID PPID COMMAND
xxxx 1 xxmap
Run the following as root user to try to correct the problem.
/usr/OV/bin/nv6000_smit OVWAPPINITSTOP
Execution of this command issues a 'kill -9 xxxx,' and the stranded
process goes away. But the next time you startup and then exit
the GUI the process gets stranded all over again.
I did notice that while the GUI is up the xxmap process parent is
ovw - as expected - but upon exiting the GUI the parent reverts to
PID=1, or /etc/init. I'm also exporting the display back to the
server so I don't have to actually visit the client, which resides
in another city.
Any clues?
TIA
Dave Dimond
dimond@allina.com
Allina Health System, Mpls, MN
|