| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Can anyone help diagnose this problem on an 8200? The following error messages show up in the UNIX error log facility. They seem to show up after almost (but not every) reboot. [ cross posted in TURBOLASER & DIGITAL_UNIX ] Thanks, Mark ********************************* ENTRY 2. ********************************* ----- EVENT INFORMATION ----- EVENT CLASS ERROR EVENT OS EVENT TYPE 110. MACHINE STATE SEQUENCE NUMBER 0. OPERATING SYSTEM DEC OSF/1 OCCURRED/LOGGED ON Tue May 27 10:13:10 1997 OCCURRED ON SYSTEM castor SYSTEM ID x0000000C CPU TYPE: DEC 7000 SYSTYPE x00000000 SYSTEM STATE x0003 CONFIGURATION CORRUPTED ERROR ENTRY - ENTRY DUMP: RECORD HEADER 0000: 00020300 0000000C 00060501 3385F569 *............i..3* 0010: 74736163 0000726F 00000000 00000000 *castor..........* 0020: 00000004 0000000A 16030064 FFFF000A *........d.......* 0030: FFFFFFFF 00000000 *........ * RECORD BODY 0038: 00000002 00000000 00000000 00000000 *................* 0048: 00000000 00000001 00000000 00000000 *................* 0058: 00000000 00000000 00000F00 00000000 *................* 0068: 4550494E 45544F4E 00005453 00000000 *NIPENOTEST......* 0078: 34365941 33343133 00003230 00000000 *AY64314302......* 0088: 0A000000 00000000 00000058 80000000 *........X.......* 0098: 00000018 00000038 00000086 00000001 *....8...........* 00A8: C1FFFFFF FFFFFFF0 0CC3967F FFFFFF00 *................* 00B8: 00000054 00000000 00000000 00000001 *T...............* 00C8: 0015000A 00000000 73008014 00440000 *...........s..D.* 00D8: 00000303 00000303 00A05400 00000303 *.........T......* 00E8: 00000400 00000004 00000214 000001F0 *................* 00F8: 00000000 00000000 89000000 000000FF *................* 0108: 000FFFFF 00000000 73008014 00800000 *...........s....* 0118: 00000240 00000098 00400303 00400C0C *@.........@...@.* 0128: 00406060 00409090 00600000 00E08A84 *``@...@...`.....* 0138: 00000000 00000000 000000FE 00000000 *................* 0148: 00000000 00000000 00000000 00000000 *................* 0158: 00000000 00000000 89400000 000000FF *..........@.....* 0168: 000FFFFF 00000000 73008014 00440000 *...........s..D.* 0178: 00000250 000000BA 00000303 00000303 *P...............* 0188: 00A05400 00000303 00600000 00E08A84 *.T........`.....* 0198: 00000000 00000000 000000FE 00000000 *................* 01A8: 00000000 00000000 00000000 00000000 *................* 01B8: 00000000 00000000 89800000 000000FF *................* 01C8: 0003FFFF 00000000 00005000 00100000 *.........P......* 01D8: 000FC260 00000080 0011D580 07850000 *`...............* 01E8: 00000303 00000C0C 00006060 00009090 *........``......* 01F8: 80000002 00000225 00000001 00000000 *....%...........* 0208: 00000000 00000000 00000000 00000000 *................* 0218: 89C00000 000000FF 0003FFFF 00000000 *................* 0228: 00005000 01440000 000FC270 00000091 *.P....D.p.......* 0238: 0CC39640 07120000 00000303 00000303 *@...............* 0248: 00215400 00000303 80000002 00000225 *.T!.........%...* 0258: 00000000 00000000 00000000 00000000 *................* 0268: 00000000 00000000 8A000000 000000FF *................* 0278: FFFFFFFF 00000001 00002020 00000000 *........ ......* 0288: 00000180 00000000 80000041 80000141 *........A...A...* 0298: 00000000 00000000 00000000 00000000 *................* 02A8: 00000000 00000000 00000000 00000000 *................* 02B8: 00000000 00000000 00000000 00000000 *................* 02C8: 00000100 00000000 80000000 00000000 *................* 02D8: 00000006 00000000 00000000 00000000 *................* 02E8: 00000800 00000000 00000000 00000000 *................* 02F8: 20000000 00000000 *... .... * ********************************* ENTRY 3. ********************************* also, the following looks like an abbreviated verion & seems to repeat: ********************************* ENTRY 4. ********************************* ----- EVENT INFORMATION ----- EVENT CLASS ERROR EVENT OS EVENT TYPE 110. MACHINE STATE SEQUENCE NUMBER 0. OPERATING SYSTEM DEC OSF/1 OCCURRED/LOGGED ON Wed May 21 10:14:03 1997 OCCURRED ON SYSTEM castor SYSTEM ID x0000000C CPU TYPE: DEC 7000 SYSTYPE x00000000 SYSTEM STATE x0003 CONFIGURATION ********************************* ENTRY 5. *********************************
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 9960.2 | system configuration entry | CSC32::I_WALDO | Tue May 27 1997 16:47 | 2 | |
Please get and install DECevent. The error log entry in .0 is the
system configuration. Neat stuff that comes on Turbolasers.
| |||||
| 9960.3 | PAK? | NCMAIL::LEFFLERM | Wed May 28 1997 12:43 | 6 | |
Thanks for the suggestion. I have the dec event kit, but what name does
the PAK go by? Searching VTX PAK for anything containing "*event*
yields nothing...
Thanks,
Mark
| |||||
| 9960.4 | license info | CSC32::I_WALDO | Wed May 28 1997 13:59 | 39 | |
From the release notes:
1.2 License Registration
The License Product Authorization Key (License PAK) must be
registered in the License Database (LDB) in order to use the
analysis and notification features of DECevent on a newly
licensed node. The PAK is not needed to run the translation
feature of DECevent. Registration is performed as a post-
installation procedure.
2.1 Installing DECevent from the Distribution Media
The following sections describe the procedure for installing
DECevent from the distribution media and provides examples of
prompts and displays.
NOTE
A product authorization key (PAK) license is required
in order to utilize the DECevent analysis and notifica-
tion added-value options. The license is obtained by a
DIGITAL Customer Services engineer through the techni-
cal information management architecture (TIMA) and must
be installed on your system prior to kit installation.
To find the DECevent service PAK in TIMA, select the
TIMA tools database and search for "DECEVENT PAK". The
title of the tool you need is "Service Tools Product
Authorization Key (PAK) Distribution Tool". Refer to
TIMA documentation for specifics.
In addition, customers may acquire the PAK information
by requesting the PAK from DSNlink hardware support.
| |||||