nv-l
[Top] [All Lists]

Re: nv6000.log

To: nv-l@lists.tivoli.com
Subject: Re: nv6000.log
From: Stefan Schickling <stefan_schickling@MUS.DE>
Date: Mon, 22 Jun 1998 14:43:51 +0200
Organization: m+s Elektronik AG
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView et alia <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView et alia <NV-L@UCSBVM.UCSB.EDU>
Hello Moise,
the default directory for the nv6000.log is the home-directory. When I install
a system, i change the root's home to /home/root to beware from errors with
overrun filesystem in the root.
At NetView v5 you can change the logfile-directory for nv6000.log in the smitty
menu to start the gui.
At v4 create a link from the log-directory.

best wishes,
Stefan Schickling  /SE
m+s Elektronik AG

Moise Dignard wrote:

> I have a problem with the file "nv6000.log". In my system this file grows
> sometimes up to 50 Meg, and fills up the directory, and the default one is
> root (let me tell you that my box did not like this). Therefore I link the
> nv6000.log file in the  /usr/OV/log directory, that way when the file grew
> my box would not crash, only the file directory /usr/OV/log would fills up.
>      Is it normal for this file to grow like this?
>      Do you know what might be the cause?
>
>  Here are a couple of sample of what I get in nv6000.log :
>
> **********************
> HVDB::createObject cannot create object with keyval:
> 00094NONETNONODNONETNONODNOIPADDRESdefault failed: error 63 Field name is
> not unique
> Thu Jun 18 14:05:38 EDT 1998
> Thu Jun 18 16:35:11 EDT 1998
> HVDB::createObject cannot create object with keyval:
> 00040NONETNONODNONETNONODNOIPADDRESdefault failed: error 63 Field name is
> not unique
> HVDB::createObject cannot create object with keyval:
> 00094NONETNONODNONETNONODNOIPADDRESdefault failed: error 63 Field name is
> not unique
> Error opening ovsnmp.conf database...
> Error is: An error occurred during a system call
> Error opening ovsnmp.conf database...
> Error is: An error occurred during a system call
> Error opening ovsnmp.conf database...
> Error is: An error occurred during a system call
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> ....muchmuch more
>
> then
>
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> ....more and more
>
> then
>
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> .....more and more
>
> then
>
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> Fatal error in Write.: A file descriptor does not refer to an open file.
> ...more and  more
>
> then
>
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file numberdf
>
> Fatal error in Write.: Bad file number
> Fatal error in Write.: Bad file number
> ....more and more
>
> and the pattern continues
>
> *******************
> Fri Jun 19 10:25:53 EDT 1998
> Fri Jun 19 10:27:26 EDT 1998
> Warning: Cannot allocate colormap entry for "Salmon"
> Warning: Cannot allocate colormap entry for "Plum"
> Warning: Cannot allocate colormap entry for "Coral"
> Warning: Cannot allocate colormap entry for "Goldenrod"
> Warning: Cannot allocate colormap entry for "Violet"
> Warning: Cannot allocate colormap entry for "DarkSalmon"
> Warning: Cannot allocate colormap entry for "DarkTurquoise"
> Cannot Create Symbol for the cluster failed: error 91 Map not open
> Could not find object with keyval:00040NONETNONODNONET00002NOIPADDRES
> Cannot change field value for node state failed: error 80 Object not found
> Cannot update Object Status failed: error 91 Map not open
> Cannot update Object Status failed: error 91 Map not open
> Could not find object with keyval:00040NONETNONODNONET00002NOIPADDRES
> Cannot change field value for node state failed: error 80 Object not found
> Cannot update Object Status failed: error 91 Map not open
> Cannot update Object Status failed: error 91 Map not open
> Could not find object with keyval:00040000000000200000NONODNOIPADDRES
> Cannot change field value for connection state failed: error 80 Object not
> found
> Could not find object with keyval:00040000000000200000NONODNOIPADDRES
> Cannot update Object Status failed: error 91 Map not open
> Could not find object with keyval:00040NONETNONODNONET000020024A6A8C0
> Cannot change field value for address state failed: error 80 Object not
> found
> Cannot update Object Status failed: error 91 Map not open
> Could not find object with keyval:00040NONETNONODNONET000020025A6A8C0
> Cannot change field value for address state failed: error 80 Object not
> found
> Cannot update Object Status failed: error 91 Map not open
>
> **********

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web