[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

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

1241.0. "Old events shown in the ENS Multi-line window" by 42441::JUDD (Geoff Judd. UK TSC. Viables, Basingstoke) Thu Mar 14 1996 09:40

Hi,
  Has anyone seen the following problem before. The system is a VAX running
OpenVMS V6.1 and PCM V1.6-201 (ECO 2). This morning at 00:02:08.41 a level 4
event HSJINSTCODE was reported in an eventlist window against 2 HSJ40 systems.
However when the context of the events were displayed it showed that the
events had been generated on 24-FEB-1996. At the time these events were
displayed a console archive command of all systems keeping the last 480 hours of
data was in progress. However for these 2 HSJ40 nodes there was nothing to
archive. I have extracted the events for the nodes but the events show as being
generated on the 24-FEB-1996 and the last event generated was on the 8-MAR-1996.
The ENS logfile shows nothing of significance but I have asked the customer to
define console$debug to ENS so hopefully more information will be given should
the problem occur again.

Thanks in advance,

Geoff Judd.

T.R	Title	User	Personal Name	Date	Lines
1241.1	System also stopped logging data	42441::JUDD	Geoff Judd. UK TSC. Viables, Basingstoke	`Wed Mar 27 1996 12:43`	14
	The problem has been reproduced again with CONSOLE$DEBUG set to ENS. This shows that an event was definitely triggered at the time that the event is shown in the multi-line window. However there is no corresponding data shown at the time event is generated when a console extract is done. In fact no data is being logged at all. The system can be connected OK and all appears normal but none of the data is logged (a Monitor, Extract and a dump of the log file show none of the data). The customer is now running V1.6-205 although the problem was originally seen on ECO2. Any ideas ? Geoff Judd.
1241.2	Could archiving have left a flag set preventing data being logged ?	42441::JUDD	Geoff Judd. UK TSC. Viables, Basingstoke	`Wed Mar 27 1996 12:55`	7
	I see from note 1252 that archiving will stop data being logged for node when it is being archived. The problem normally first noticed during the early hours of the morning and an archive is run at midnight. Archiving definitly no longer running and I dod not bvelive there were any errors but is it possible that a flag is being left set which is preventing data being logged. Geoff Judd.