topic Re: Alpha crashing in Operating System - OpenVMS

Alpha crashing

Mulder_1 — Tue, 16 Jun 2009 07:26:47 GMT

Hi,

The server gets crashed due to NET$ACP.EXE
----------------------------------------------
CPU 00 Processor crash information
----------------------------------

CPU 00 reason for Bugcheck: INVEXCEPTN, Exception while above ASTDEL

Process currently executing on this CPU: NET$ACP

Current image file: $255$DKA100:[SYS19.SYSCOMMON.][SYSEXE]NET$ACP.EXE;1

Current IPL: 8 (decimal)

CPU database address: 8143A000
---------------------------------------------
Can anyone please provide any suggestions ?

Thanks

Re: Alpha crashing

Duncan Morris — Tue, 16 Jun 2009 07:54:03 GMT

Mulder,

what is your hardware, and what software versions are you using (especially DECnet and OpenVMS)?

Try;

$ show sys/full/noproc

$ prod show prod/full DECNET*

$ prod show prod/full VMS

Please post the output in a text attachment.

Many thanks,

Duncan

Re: Alpha crashing

Ian Miller. — Tue, 16 Jun 2009 08:18:49 GMT

Also look in the SYS$ERRORLOG directory for a file with a name starting with CLUE and dated for the crash. Post that if found.

Re: Alpha crashing

Mulder_1 — Tue, 16 Jun 2009 08:53:42 GMT

Please find the details as requested :

SA$:> prod show prod/full DECNET*
----------------------------------- ----------- ------------ ----------------------------------- ----------------------------
-------
PRODUCT KIT TYPE STATE MAINTENANCE REFERENCED BY
----------------------------------- ----------- ------------ ----------------------------------- ----------------------------
-------
DEC AXPVMS DECNET_OSI V7.3-1 Full LP Installed DEC AXPVMS DNVOSIECO01 V7.3-1 DEC AXPVMS OPENVMS V7.3-1
DEC AXPVMS WANDD V1.6
DEC AXPVMS X25 V1.6
----------------------------------- ----------- ------------ ----------------------------------- ----------------------------
-------

1 item found

Thanks

Re: Alpha crashing

marsh_1 — Tue, 16 Jun 2009 09:19:41 GMT

hi,

there is certainly ecos for v7.3-1 x25 that addressed a number of bugcheck issues :-

http://www11.itrc.hp.com/service/patch/patchDetail.do?patchid=AXP_X25ECO03-V73X&sel={openvms:alpha:7.3-1,}&BC=main|search|

as well as further ecos for decnet-osi that you should be looking to put on first

http://www11.itrc.hp.com/service/patch/patchDetail.do?patchid=AXP_DNVOSIECO03-V731&sel={openvms:alpha:7.3-1,}&BC=main|search|

if you've a support contract with hp and place a call ,as you probably know the first thing they'll ask you to do is get current with patches !

fwiw

Re: Alpha crashing

Volker Halle — Tue, 16 Jun 2009 10:07:16 GMT

Hi,

please attach the CLUE file from this crash to your next reply. You'll find that file on CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS on OpenVMS Alpha V6.2 or higher.

Volker.

Re: Alpha crashing

Volker Halle — Tue, 16 Jun 2009 10:22:25 GMT

Sorry, couldn't download the .ZIP file with IE, but it worked with Mozilla on OpenVMS.

This crash in GAP_DISCONNECT_SESSION_C+C8 is a 'popular' problem footprint. You're running X.25 V1.6 without patches. This problem is supposed to be fixed with V1.6 ECO 1 or higher.

Volker.

Re: Alpha crashing

Mulder_1 — Tue, 16 Jun 2009 10:32:07 GMT

Thanks to all for responding quickly...

patching is not an option at least for now...any work around ?

Also, what does this means :

GAP_DISCONNECT_SESSION_C+000C8

Thanks

Re: Alpha crashing

Volker Halle — Tue, 16 Jun 2009 10:38:24 GMT

The crash is an invalid exception and happens at the instruction LDL R16,#X0060(R16), because the contentsw of R16 is 0 (ZERO), leading to an invalid access to virtual address 00000060.

This insturction is inside the module X25$ACCESS.EXE and the routine name and offset inside this module is symbolized by SDA as GAP_DISCONNECT_SESSION_C+000C8.

There is NO workaround - except NOT using X.25 - other than installing the current X.25 V1.6 ECO.

Volker.

Re: Alpha crashing

Wim Van den Wyngaert — Tue, 16 Jun 2009 11:31:14 GMT

If you can't upgrade, find out what changed and do a roll back of that.

Wim

Re: Alpha crashing

Steve Reece — Wed, 17 Jun 2009 01:50:51 GMT

You don't say whether you've upgraded to get to this point, rebooted the system or if the system suddenly crashed for no (apparent) reason.

As others have suggested, patching up to the latest level is likely to be your fix on this.

If the system has started to misbehave following a system change, the change may need to be backed out. This could be a patch, a product installation or something else entirely.

PRODUCT SHOW HISTORY can also be useful for products installed on the system as this shows the patching that's happened as well as the products installed.

Steve