Hi,
you can also start NV with ' nv6000 -nl '. Have a look at the man
pages of NV6000.
Best regards,
Herbert Kinzler
BCS/NET
debuigny@DALLAS.NET on 21.06.98 15:43:37
Please respond to NV-L@UCSBVM.UCSB.EDU
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Herbert Kinzler/BCS/BASF)
Subject: Re: nv6000.log
Moise;
How fast is that file growing? It is normmaly going to grow no matter
what. It adds entries each time you start up the GUI, or in your case
each time an error message is generated to your shell.
I would create a small shell script that archives the days log and
creates a new, empty one. Then you'll need to decide how long to keep
the old ones.
Plus, you're getting alot of error messages in there. You need to get
in touch with support for that.
Good luck!
Art DeBuigny
debuigny@dallas.net
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
>
> **********
|