From: Subhash P (SubhashP@Computerpoint.Co.Ke)
Date: Fri Jun 17 2005 - 02:14:32 EDT
Hi managers
I am having ES40 with tru64 5.1A , its getting rebooted, please see below
messages, any clue??
Many thanks in advance.
BR
Subhash
Jun 11 08:31:29 qasys vmunix: ARMTech 134217728 32 32 2 1: Policy Path:
configurability not licensed
Jun 11 08:31:29 qasys vmunix: ARMTech 134217728 64 3 2 1: Policy Path: Tier 1
policy type = 3
Jun 11 08:31:29 qasys vmunix: ARMTech 134217728 64 4 2 1: Policy Path: Tier 2
policy type = 1
Jun 11 08:31:29 qasys vmunix: ARMTech 536870912 32 32 1 255: License
prohibits file persistence
Jun 11 08:31:29 qasys vmunix: ARMTech 536870912 64 32 1 255: Starting
background task
Jun 11 08:31:29 qasys vmunix: ARMTech 1 32 32 2 1: PLFS usage update: 0/1024
secs for 1 Tier 0 entries
Jun 11 08:31:30 qasys vmunix: ARMTech 1 64 32 255 1: PLFS Scheduler: 3 CPUs
on line
Jun 11 08:31:30 qasys vmunix: ARMTech: PLFS Scheduler loaded
Jun 11 08:31:31 qasys vmunix: Environmental Monitoring Subsystem Configured.
Jun 11 08:32:01 qasys vmunix: SuperLAT. Copyright 1994 Meridian Technology
Corp. All rights reserved.
Jun 11 08:32:23 qasys vmunix: aud97open: Can't open. No boards.
Jun 11 08:32:24 qasys vmunix: mmsess sound driver V4.1 configured
Jun 11 08:32:24 qasys vmunix: mmsess: mmsess_num_probed = 0
Jun 11 08:32:24 qasys vmunix: mmsess: No devices to open
Jun 13 08:11:19 qasys vmunix: ee0: Autonegotiated, 100 Mbps full duplex
Jun 14 06:49:39 qasys vmunix: Machine Check SYSTEM Fatal Abort
Jun 14 06:49:39 qasys vmunix: Machine check code = 0x100000202
Jun 14 06:49:39 qasys vmunix: Ibox Status =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Dcache Status =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Cbox Address =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Fill Syndrome 1 =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Fill Syndrome 0 =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Cbox Status =
0000000000000000
Jun 14 06:49:39 qasys vmunix: EV6 captured status of Bcache mode =
0000000000000000
Jun 14 06:49:39 qasys vmunix: EV6 Exception Address =
fffffc00002e8780
Jun 14 06:49:39 qasys vmunix: EV6 Interrupt Enablement and Current
Processor mode = 0000007ee0000000
Jun 14 06:49:39 qasys vmunix: EV6 Interrupt Summary Register =
0000000200000000
Jun 14 06:49:39 qasys vmunix: EV6 TBmiss or Fault status =
0000000000000000
Jun 14 06:49:39 qasys vmunix: EV6 PAL Base Address =
0000000000018000
Jun 14 06:49:39 qasys vmunix: EV6 Ibox control =
fffffe001e304396
Jun 14 06:49:39 qasys vmunix: EV6 Ibox Process_context =
0000000000000000
Jun 14 06:49:39 qasys vmunix: O/S Summary flag =
0000000000000005
Jun 14 06:49:39 qasys vmunix: Cchip Base Address (phys) =
00000f01a0000000
Jun 14 06:49:39 qasys vmunix: Cchip Device Raw Interrupt Request =
4000000000000000
Jun 14 06:49:39 qasys vmunix: DRIR Register Decode:
Jun 14 06:49:39 qasys vmunix: Bit 62: Error from Pchip 0
Jun 14 06:49:39 qasys vmunix: PCI Device Interrupt Mask =
0000000000000000
Jun 14 06:49:39 qasys vmunix: Cchip Miscellaneous Register =
0000000800000440
Jun 14 06:49:40 qasys vmunix: Misc Register Decode:
Jun 14 06:49:40 qasys vmunix: Bit 6: Interval Timer Intr Pending to
CPU 2
Jun 14 06:49:40 qasys vmunix: Bit 10: Interprocessor Intr Pending
to CPU 2
Jun 14 06:49:40 qasys vmunix: Bit 35: CChip Rev (Bit<35>)
Jun 14 06:49:40 qasys vmunix: Cchip Revision: 08
Jun 14 06:49:40 qasys vmunix: ID of CPU performing read: 00
Jun 14 06:49:40 qasys vmunix: Pchip 0 Base Address (phys) =
00000f0180000000
Jun 14 06:49:40 qasys vmunix: Pchip 0 Error Register =
8c01b7ded2800401
Jun 14 06:49:40 qasys vmunix: Pchip Error Register Decode:
Jun 14 06:49:40 qasys vmunix: Bit 0: Lost Error
Jun 14 06:49:40 qasys vmunix: Bit 10: Uncorrectable ECC Error
Jun 14 06:49:40 qasys vmunix: System Address =
00000001b7ded280
Jun 14 06:49:40 qasys vmunix: Command: DMA Read
Jun 14 06:49:40 qasys vmunix: ECC Syndrome: 8c
Jun 14 06:49:40 qasys vmunix: Pchip 1 Base Address (phys) =
00000f0380000000
Jun 14 06:49:40 qasys vmunix: Pchip 1 Error Register =
0000000000000000
Jun 14 06:49:40 qasys vmunix: Pchip Error Register Decode:
Jun 14 06:49:40 qasys vmunix: PCI Xaction Start Address =
0000000000000000
Jun 14 06:49:40 qasys vmunix: PCI Command: Interrupt Acknowledge
Jun 14 06:49:40 qasys vmunix: panic (cpu 0): System Uncorrectable Machine
Check
Jun 14 06:49:40 qasys vmunix: syncing disks... done
Jun 14 06:49:40 qasys vmunix: Alpha boot: available memory from 0xa026000 to
0x1fffe4000
Jun 14 06:49:40 qasys vmunix: Compaq Tru64 UNIX V5.1A (Rev. 1885); Tue Jul 22
10:25:51 EAT 2003
Jun 14 06:49:40 qasys vmunix: physical memory = 8192.00 megabytes.
Jun 14 06:49:40 qasys vmunix: available memory = 8031.11 megabytes.
Jun 14 06:49:40 qasys vmunix: using 31405 buffers containing 245.35 megabytes
of memory
Jun 14 06:49:40 qasys vmunix: Master cpu at slot 0
Jun 14 06:49:40 qasys vmunix: Starting secondary cpu 1
Jun 14 06:49:40 qasys vmunix: Starting secondary cpu 3
Jun 14 06:49:40 qasys vmunix: Firmware revision: 6.1-3
Jun 14 06:49:40 qasys vmunix: PALcode: UNIX version 1.88-101
Jun 14 06:49:40 qasys vmunix: Compaq AlphaServer ES40
Jun 14 06:49:40 qasys vmunix: pci1 (primary bus:1) at nexus
Jun 14 06:49:40 qasys vmunix: itpsa0 at pci1 slot 4
Jun 14 06:49:40 qasys vmunix: IntraServer ROM Version V2.0 (c)1998
Jun 14 06:49:40 qasys vmunix: scsi0 at itpsa0 slot 0 rad 0
Jun 14 06:49:40 qasys vmunix: emx0 at pci1 slot 5
Jun 14 06:49:40 qasys vmunix: KGPSA-CA : Driver Rev 1.32a : F/W Rev
3.81A4(2.01A0) : wwn 1000-0000-c92a-fd23
Jun 14 06:49:40 qasys vmunix: emx0: Using console topology setting of :
Fabric
Jun 14 06:49:41 qasys vmunix: scsi1 at emx0 slot 0 rad 0
Jun 14 06:49:41 qasys vmunix: pci0 (primary bus:0) at nexus
Jun 14 06:49:41 qasys vmunix: p3g0: Card type '3Dlabs Oxygen VX1' with 32MB
framebuffer memory.
Jun 14 06:49:41 qasys vmunix: p3g0 at pci0 slot 1
Jun 14 06:49:41 qasys vmunix: ee0 at pci0 slot 2
Jun 14 06:49:41 qasys vmunix: ee0: COMPAQ Intel 82559 (10/100 Mbps) Ethernet
Interface
Jun 14 06:49:41 qasys vmunix: ee0: Driver Rev = V1.0.12, Chip Rev = 8,
hardware address: 00-02-A5-40-9F-08
Jun 14 06:49:41 qasys vmunix: itpsa1 at pci0 slot 3
Jun 14 06:49:41 qasys vmunix: ee0: Autonegotiated, 100 Mbps full duplex
Jun 14 06:49:41 qasys vmunix: IntraServer ROM Version V2.0 (c)1998
Jun 14 06:49:41 qasys vmunix: scsi2 at itpsa1 slot 0 rad 0
Jun 14 06:49:41 qasys vmunix: isa0 at pci0
Jun 14 06:49:41 qasys vmunix: gpc0 at isa0
Jun 14 06:49:41 qasys vmunix: gpc1 not probed
Jun 14 06:49:41 qasys vmunix: ace0 at isa0
Jun 14 06:49:41 qasys vmunix: ace1 at isa0
Jun 14 06:49:41 qasys vmunix: lp0 at isa0
Jun 14 06:49:41 qasys vmunix: fdi0 at isa0
Jun 14 06:49:41 qasys vmunix: fd0 at fdi0 unit 0
Jun 14 06:49:41 qasys vmunix: ata0 at pci0 slot 15
Jun 14 06:49:41 qasys vmunix: ata0: ACER M1543C
Jun 14 06:49:41 qasys vmunix: scsi3 at ata0 slot 0 rad 0
Jun 14 06:49:41 qasys vmunix: scsi4 at ata0 slot 1 rad 0
Jun 14 06:49:42 qasys vmunix: usb0 at pci0 slot 19
Jun 14 06:49:42 qasys vmunix: Created FRU table binary error log packet
Jun 14 06:49:42 qasys vmunix: kernel console: p3g0
Jun 14 06:49:42 qasys vmunix: dli: configured
Jun 14 06:49:42 qasys vmunix: NetRAIN configured.
Jun 14 06:49:42 qasys vmunix: ATM Subsystem configured with 3 restart threads
Jun 14 06:49:42 qasys vmunix: ATMUNI: configured
Jun 14 06:49:42 qasys vmunix: ATMSIG: 3.x (module=uni3x) configured
Jun 14 06:49:42 qasys vmunix: ILMI: 3.x (module=ilmi) configured
Jun 14 06:49:42 qasys vmunix: ATM IP: configured
Jun 14 06:49:42 qasys vmunix: ATM LANE: configured.
Jun 14 06:49:42 qasys vmunix: ATM IFMP: configured
Jun 14 06:49:42 qasys vmunix: vm_swap_init: swap is set to eager allocation
mode
Jun 14 06:49:42 qasys vmunix: ARMTech 268435456 64 32 255 1: ARMTech Lic.Ctrl
successfully initialised (3 CPUs)
Jun 14 06:49:42 qasys vmunix: ARMTech 268435456 64 32 255 1: ARMTech Lic.Ctrl
- license being processed
Jun 14 06:49:42 qasys vmunix: ARMTech 268435456 64 32 255 1: ARMTech Lic.Ctrl
- license accepted
Jun 14 06:49:42 qasys vmunix: ARMTech 134217728 32 32 2 1: Policy Path:
configurability not licensed
Jun 14 06:49:42 qasys vmunix: ARMTech 134217728 64 3 2 1: Policy Path: Tier 1
policy type = 3
Jun 14 06:49:42 qasys vmunix: ARMTech 134217728 64 4 2 1: Policy Path: Tier 2
policy type = 1
Jun 14 06:49:42 qasys vmunix: ARMTech 536870912 32 32 1 255: License
prohibits file persistence
Jun 14 06:49:42 qasys vmunix: ARMTech 536870912 64 32 1 255: Starting
background task
Jun 14 06:49:42 qasys vmunix: ARMTech 1 32 32 2 1: PLFS usage update: 0/1024
secs for 1 Tier 0 entries
Jun 14 06:49:42 qasys vmunix: ARMTech 1 64 32 255 1: PLFS Scheduler: 3 CPUs
on line
Jun 14 06:49:42 qasys vmunix: ARMTech: PLFS Scheduler loaded
Jun 14 06:49:43 qasys vmunix: Environmental Monitoring Subsystem Configured.
Jun 14 06:50:13 qasys vmunix: SuperLAT. Copyright 1994 Meridian Technology
Corp. All rights reserved.
Jun 14 06:50:38 qasys vmunix: aud97open: Can't open. No boards.
Jun 14 06:50:39 qasys vmunix: mmsess sound driver V4.1 configured
Jun 14 06:50:39 qasys vmunix: mmsess: mmsess_num_probed = 0
Jun 14 06:50:39 qasys vmunix: mmsess: No devices to open
Jun 15 10:43:42 qasys vmunix: ee0: Autonegotiated, 100 Mbps full duplex
BR.
Subhash Pakhare.
CSA (HP-UX), CSE (Tru64 UNIX), SCSA, CDP.
Sr. Support Engineer- Enterprise System Group
Computerpoint Kenya Group
Tel: (+254-20) 4446644
Cell: (+254-721) 214343.
www.computerpoint-me.com
"Have you ever noticed? Anybody going slower than
you is an idiot, and anyone going faster than you
is a maniac."- George Carlin
-----Original Message-----
From: tru64-unix-managers-owner@ornl.gov
[mailto:tru64-unix-managers-owner@ornl.gov] On Behalf Of A. Mahendra Rajah
Sent: Friday, June 17, 2005 1:05 AM
To: tru64-unix-managers@ornl.gov
Subject: DOP error: application not available on this system
We are running Tru64 v5.1B-3 (= v5.1B-2 + pkit#5) on an ES40.
Before pkit#5 was applied, we had an application 'prtcontrol'
added to the DOP database that worked fine for authorized
usernames before _and_ _after_ pkit#5.
I made some modifications to the ksh script used by
'prtcontrol' and noticed that DOP was still using the original
version of it. Question #1: Why was it still looking at the
original version? It no longer exists in its original directory!
OK, so I thought I would do a 'dop -d', 'dop -a' and 'dop -W'
to get it reinstalled in the dop database.
But now, for the 'root' user 'dop prtcontrol' works using the
modified ksh script. For the usernames that have been already
authorized to run 'prtcontrol', the dop command returns this
error:
A system error occurred, preventing prtcontrol from
being launched. The application you wish to access is
not available on this system. It may be contained in a
subset that is not currently installed.
Funny thing is that the same error is returned if this user
tries 'dop somegarbage' where 'somegarbage' is not even in the
dop database.
So, I thought that there may be an access violation problem?
/etc/doprc.bin had '-rw-------' for protection and I modified
that to '-rw-r--r--', but the error message persists!
Any insight into what is going on here and how can I convince
'dop' to do its job for my users?
Thanks in advance,
-- mahendra
.................................................................
A. Mahendra Rajah Email: Mahendra.Rajah@URegina.CA
Tru64 UNIX Systems Manager Phone: (306) 585-4496
Dept. of Computing Services FAX: (306) 337-2324
University of Regina,
Regina, Sask., S4S 0A2
Canada.
.................................................................
ComputerPoint K Ltd Disclaimer:
This E-Mail may contain confidential information and may be legally privileged and is intended only for the person to whom it addressed. If you are not the intended recipient, you are notified that you may not use, distribute or copy this document in any manner whatsoever.
Kindly also notify the sender immediately by telephone, and delete the E-Mail. When addressed to clients of the company from where this e-mail originates ("the sending company) any opinion or advice contained in this e-mail is subject to the terms and conditions expressed in any applicable terms of business or client engagement letter.
The sending company does not accept liability for any damage, loss or expense arising from this email and /or from accessing of any files attached to this e-mail.
Tel. +254 20 4446644, E-Mail: postmaster@computerpoint.co.ke
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:19 EDT