I am not certain what the nature of your problem is and my suggestion, of
course, is that you call Support the next time it happens and get some help
in pinning it down. But there are a few things I can offer, based upon
what you have said.
First, ovspmd is single-threaded. That means that if you have done an
ovstart, for example, and it has not completed, then you cannot do an
ovstatus or an ovstop. They will just hang waiting for the previous
command to complete. So the next time your ovstatus hangs, do a ps -ef |
grep ov and see if there are other such command still running. You can
then kill the previous one. It may even put an error message to the window
in which it was running if you do.
If snmpCollect (or any other daemon for that matter) has exited for reasons
unknown, always look for a core file, either in /usr/OV/PD/cores (many
daemons put cores there) or else look in the root (/) directory. If you
find a core in / and it is current, then you can try to figure out who
produced it. One way is to use the strings command. Another is the od
command (for AIX Version 4.1 and 4.2 -- I haven't tried this on 4.3 yet):
od -c <core_filename> 0x6b0 | head . The name of the coring process
should be spelled out in the array, one letter at a time. Armed with this
information, you should be in a good position to call Support.
Tivoli (NetView for UNIX) L3 Support
Cornelis Jacobi <C.A.Jacobi AT NL.DAP.PHILIPS DOT COM> on 09/25/98 02:40:36 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks)
Subject: Netview 4.1 Problem
I would like to know if anyone has suggestions to check thing in the
Netview is not functioning well during more than a day.
There's one gui open and events are still coming. I'm not working with
rules. Normally there are only a few events coming every hour, I'v
never seen daemons swallowing in work.
snmpCollect didn't function any more. I tried to do some research by
starting a gui with more authority. I didn't even reach the login
I started to give some commands on the prompt: ovstatus gives no
output and hangs, the same for ovstop for every daemon. I had to kill
all processes before I could start with ovstart.
All logfiles in /usr/OV/log contain no messages regarding anything is
Everything is working fine now, but I want to know what's the cause.
Hope anyone can help,
Philips DAP Holland