I think you are asking for the impossible here. What the messages mean is
pretty straightforward, but that won't tell you who issued them, and that
is more important. And they need not be from NetView itself.
The first one is issued because some process issued a write to file and the
file descriptor which allocates that file is not open, so the write failed.
Who is trying to write and what are they trying to write, it doesn't say.
The second one comes from some process registering for traps with trapd.
It apparently established a session but some one of the session parms has
turned up bad (as might happen if it lost the connection).
I did a quick look at the NetView message catalogs and I could not find
either of these.
Don't assume that just because the messages are in the nv6000.log that they
are produced by NetView itself.
The log contains all error messages which any process started by ovw,
including any user or vendor applications, puts to stderr. The log just
gives us a place to capture them.
I would pursue this by removing or disabling any third-party apps from
starting, getting all the NetView daemons running,
and then start the GUI. Once you have NetView clean you can add back these
other apps. They would have added registration files in
/usr/OV/registration/C. Move them out (don't just rename them as the names
do not matter -- all files in this directory are read as registration
files).
Want more help? Please call Support.
James Shanks
Tivoli (NetView for UNIX) L3 Support
DignardM@STENTOR.CA on 06/23/98 03:39:50 PM
Please respond to NV-L@UCSBVM.UCSB.EDU
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: nv6000.log
Could someone tell me exactly what those 2 specific messages found in
nv6000.log means. I would help me to evaluate my problem.
1) Fatal error in Write.: A file descriptor does not refer to an open file.
2) Request::ProcessTrapRequest - Error in PDU
The session parameter was not created by OVsnmpOpen
Thank you
MOE
|