[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
|
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
780.0. "CONSOLE EXTRACT and CONSOLE VERIFY problem" by BACHUS::WILLEMSG (Geert Willems MCS-Belgium) Fri Jun 02 1995 16:58
Hi,
PCM T1.6-009. OpenVMS V6.1.
I can't use CONSOLE EXTRACT for any system
1)
POLYCENTER Console Manager
Extract facility Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
No log data since specified time
End of requested output - Press RETURN to exit ...
2) This is with /PRIORITY
POLYCENTER Console Manager
Eventlist Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
%DCL-W-CONFLICT, illegal combination of command elements - check documentation
\PRIORITY\
3)I tried the CONSOLE VERIFY command
$ console verify brssws
POLYCENTER Console Manager
Verify facility Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
Test 1 : Passed.
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Passed.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_ fileset
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Test 5 : ** FAILED **.
$ console verify brssws/full
POLYCENTER Console Manager
Verify facility Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Error reporting data will be in the file CONSOLE$VERIFY__BRSSWS.REPORT
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
LOG file
TIMES file
TIMES file
EVENTS file
EVENTS file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : Passed.
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_ fileset
LOG file
TIMES file
TIMES file
EVENTS file
EVENTS file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : ** FAILED **.
$ console verify brssws/repair
POLYCENTER Console Manager
Verify facility Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
Test 1 : Passed.
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Passed.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_ fileset
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Test 5 : ** FAILED **.
$ console verify brssws/full
POLYCENTER Console Manager
Verify facility Version T1.6-009
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Error reporting data will be in the file CONSOLE$VERIFY__BRSSWS.REPORT
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
LOG file
TIMES file
TIMES file
EVENTS file
EVENTS file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : Passed.
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_ fileset
LOG file
TIMES file
TIMES file
EVENTS file
EVENTS file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : ** FAILED **.
$ type CONSOLE$VERIFY__BRSSWS.REPORT;2
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
LOG file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : Passed.
<5005> Timestamps in the TIMES file
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : Passed.
Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_ fileset
LOG file
Test 1, Check to ensure that there are the same number of timestamp
records in the .TIMES file as there are <NL> characters in
the .LOG file, there should be a one-one match.
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2, Check to ensure that the first timestamp record points to
offset 0 in the .LOG file
Test 2 : Passed.
Test 3, Check to ensure that all our timestamp records point
somewhere within the logfile and that they point to
newline characters
Test 3 : Passed.
Test 4, Check to ensure that we dont have log records on the end of
the file for which there are no timestamp records
Test 4 : ** FAILED **, Found extra lines in .LOG file without timestamp
Test 5, Check that the .TIME and .LOG file pointers for each event
record fall within the bounds of the relevant file.
Also check the length values match in the record.
Test 5 : Event record 1 does not point to the start of a time record
Ended Host BRSSWS
Is this a known problem ?
Thanks in advance & Rgds,
Geert
T.R | Title | User | Personal Name | Date | Lines |
---|
780.1 | Can I get access to the system????? | ZEDAR::simon | Simon Jackson 830 x3879 | Fri Jun 02 1995 17:31 | 7 |
| Geert,
you seem to have m,any problems on this system. Is it possible
to log inot the system across Easynet and have a look at it?
Drop me mail about this on elbrig::sdj
Cheers Simon.....
|
780.2 | | BACHUS::WILLEMSG | Geert Willems MCS-Belgium | Tue Jun 13 1995 17:50 | 41 |
|
Hi Simon,
I'm still having this problem. Can it be related to note 754 ?
I don't think so, but ...
I want to delete all the log files and archive files and see what
happens ... Or do you have something else in mind ?
Thanks in advance & Rgds,
Geert
$ console verify brssws
POLYCENTER Console Manager
Verify facility Version T1.6-031
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Starting Host BRSSWS
Loading : CONSOLE$LOGFILES:BRSSWS. fileset
Test 1 : Passed.
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Passed.
Test 5 : Passed.
Loading : CONSOLE$ROOT:[ARCHIVE]BRSSWS.9505221605_TO_9506060205_
fileset
Test 1 : ** FAILED **, Too many lines of data for available timestamps
<66000> Timestamps in the TIMES file
<66204> Records found in the log file
Test 2 : Passed.
Test 3 : Passed.
Test 4 : Test 5 : ** FAILED **.
|
780.3 | | BACHUS::WILLEMSG | Geert Willems MCS-Belgium | Wed Jun 14 1995 11:59 | 7 |
|
I deleted the files in the console$archive directory.
Started an archive and re-did the console verify. It works now.
Rgds,
Geert
|
780.4 | | ZEDAR::simon | Simon Jackson 830 x3879 | Wed Jun 14 1995 12:59 | 6 |
| Geert,
a little while after you had the problem before someone else
had a similar problem after archiving and I had to change part of the
archive algorithm. I guess you saw a hangover from that problem.
Cheers Simon....
|