Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Different VMS V8.3 I64 crashes

 
SOLVED
Go to solution
Dario Karlen
Frequent Advisor

Different VMS V8.3 I64 crashes

Hi
We had some crashes on both of our cluster nodes in the last few weeks.
I found in the clue$history following information:
Date Version System/CPU Node Bugcheck Process
PC Module Offset
----------------- -------- ------------------- ------ ------------ --------
------- -------- ----------------------- --------
11-MAR-2007 03:09 V8.3 HP rx2620 (1.60GHz ALESA1 PROCGONE SYSINIT
80B38EC0 IMAGE_MANAGEMENT 000495C0
11-MAR-2007 05:02 V8.3 HP rx2620 (1.60GHz ALESA1 PROCGONE SYSINIT
80B38EC0 IMAGE_MANAGEMENT 000495C0
11-MAR-2007 04:26 V8.3 HP rx2620 (1.60GHz ALESA2 PROCGONE SYSINIT
80B38EC0 IMAGE_MANAGEMENT 000495C0
21-SEP-2007 02:43 V8.3 HP rx2620 (1.60GHz ALESA1 CLUEXIT NULL
80D24290 SYS$CLUSTER 0003EF90
6-MAR-2008 04:55 V8.3 HP rx2620 (1.60GHz ALESA1 INSF_NONPAGE NULL
811E2470 SYS$SHDRIVER 00173670
9-APR-2008 17:27 V8.3 HP rx2620 (1.60GHz ALESA2 INSF_NONPAGE TCPIP$FT
PC046C3 811FA370 SYS$SHDRIVER 00173670

I wanted to increase the NPAGEDYN, but I didn't get it. I put the lines
"ADD_NPAGEDYN=800000"
"ADD_NPAGEVIR=800000" in the modparams.dat, executed autogen and did a restart. But when I check it in SYSGEN it shows me the same values as before. How can I increse the NPAGEDYN and NPAGEDIR???
Thank you in advance
Dario
21 REPLIES 21
labadie_1
Honored Contributor
Solution

Re: Different VMS V8.3 I64 crashes

Do not use the ADD_ in modparams.dat, better use
MIN_NPAGEDYN
and let autogen calculate NPAGEVIR.

After the autogen, you can check the values that will be used at the next boot, doing
$ mc sysgen
use current
sh npagedyn
sh npagevir

And you reboot only if the values suit you.

Vladimir Fabecic
Honored Contributor

Re: Different VMS V8.3 I64 crashes

You can do it, of course:
$ mc sysgen
SYSGEN > USE CURRECT
SYSGEN > SET NPAGEDYN new_value
SYSGEN > SET NPAGEVIR new_value
SYSGEN > WRITE CURRENT
And reebot after that.
Better way is to specify values in MODPARAMS.DAT to be:
NPAGEDYN=new_value
NPAGEVYR=new_value
and then:
$ @sys$update:autogen getdata reboot
In vino veritas, in VMS cluster
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

We have an old VMS 7.3 Alpha, on which MAX NPAGEDYN and MAX NPAGEVIR is set to -1.
How can we do the same on our I64 that there is no limit for the NPAGE parameters?
labadie_1
Honored Contributor

Re: Different VMS V8.3 I64 crashes

By the way, PROCGONE means something has gone wrong very early in the boot process.

R0 was containing which value ?

labadie_1
Honored Contributor

Re: Different VMS V8.3 I64 crashes

be careful, as Npagedyn is related to your physical memory
Can you post

$ sh mem/phy


If you want, you can fix a high value for npagedyn/Npagevir, and eventually fail to boot your system, with a POOLEXPF or similar message.

Extract from the doc, at
http://h71000.www7.hp.com/doc/82FINAL/aa-pv5nj-tk/aa-pv5nj-tk.PDF


For the benefit of OpenVMS VAX systems with limited physical memory, AUTOGEN logs a warning message
in its report if NPAGEDYN exceeds 10 percent of physical memory or if NPAGEVIR exceeds 33 percent of
physical memory.
AUTOGEN also limits its own calculated value for NPAGEDYN to 20 percent of physical memory, and limits
NPAGEVIR to 50 percent of physical memory. These calculated values are adequate for most workstations
and systems with 16 or fewer megabytes of physical memory. If your system requires a larger value, you can
override the AUTOGEN calculated values by setting higher values in MODPARAMS.DAT
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

ina > sh mem/phy
System Memory Resources on 10-APR-2008 18:38:32.33

Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (1.99GB) 262096 174683 86990 423

Of the physical pages in use, 34834 pages are permanently allocated to OpenVMS.
ina >

We want the full memory available for the system....
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

the system whe have trouble with insufficient nonpaged pool is with one of our customer. I tried to set the NPAGEDYN and NPAGEDIR to -1 in our I64 in the office, no I cannot start the machine, showing following errors:
EFI Boot Manager ver 1.10 [14.62] Firmware ver 4.13 [4634]

Please select a boot option

OpenVMS on DKA0: PKA0.0

EFI Shell [Built-in]

DVD rom device

Boot Option Maintenance Menu

System Configuration



Use ^ and v to change option(s). Use Enter to select an option

Loading.: OpenVMS on DKA0: PKA0.0

Starting: OpenVMS on DKA0: PKA0.0


**************************************************************

* Exception taken before exception handler has been loaded! *

* Unable to take crashdump. *

**************************************************************


* Exception Frame Display: *


Exception taken at IP 00000000.00056230, slot 00 from Kernel mode

Exception Frame at 00000000.2020BB80

Trap Type 00000008 (Access control violation fault)

IVT Offset 00001000 (Alternate Data TLB Fault)


* = Value read directly from the register rather than the frame


Control Registers:

CR0 Default Control Register (DCR) 00000000.00007F00

CR1 Interval Timer Match Register (ITM) * 00000023.D60C3CC9

CR2 Interruption Vector Address (IVA) * 00000000.000C0000

CR8 Page Table Address (PTA) * 00000000.0000003C

CR16 Processor Status Register (IPSR) 00001010.09026010

CR17 Interrupt Status Register (ISR) 00000802.00000000

CR19 Instruction Pointer (IIP) 00000000.00056230

CR20 Faulting Address (IFA) 00000801.FF0003C0

CR21 TLB Insertion Register (ITIR) 00000000.00000034

CR22 Instruction Previous Address (IIPA) 00000000.00056220

CR23 Function State (IFS) 80000000.0000030A

CR24 Instruction immediate (IIM) 00000000.00000000

CR25 VHPT Hash Address (IHA) 00000000.00808EA0

CR64 Local Interrupt ID (LID) * 00000000.00000000

CR66 Task Priority Register (TPR) * 00000000.00010000

CR68 External Interrupt Req Reg 0 (IRR0) * 00000000.00000000

CR69 External Interrupt Req Reg 1 (IRR1) * 00000000.00000000

CR70 External Interrupt Req Reg 2 (IRR2) * 00000000.00000000

CR71 External Interrupt Req Reg 3 (IRR3) * 00000000.00000000

CR72 Interval Time Vector (ITV) * 00000000.00010000

CR73 Performance Monitoring Vector (PMV) * 00000000.00010000

CR74 Corrected Machinecheck Vector (CMCV) * 00000000.00010000

CR80 Local Redirection Register 0 (LRR0) * 00000000.00010000

CR81 Local Redirection Register 1 (LRR1) * 00000000.00010000


Application Registers:

AR0 Kernel Register (KR0) * 00000000.20620000

AR1 Kernel Register (KR1) * 00000000.60000000

AR2 Kernel Register (KR2) * 00000000.00000000

AR3 Kernel Register (KR3) * 00000024.C5A84E1C

AR4 Kernel Register (KR4) * 00000000.00000000

AR5 Kernel Register (KR5) * 00000000.00000000

AR6 Kernel Register (KR6) * 00000000.00000000

AR7 Kernel Register (KR7) * 00000000.10001000

AR16 Register Stack Config Reg (RSC) 00000000.00000000

AR17 Backing Store Pointer (BSP) 00000000.201FC578

AR18 Backing Store for Mem Store (BSPSTORE) 00000000.201FC328

AR19 RSE NaT Collection Register (RNAT) 00000000.00000000

AR32 Compare/Exchange Comp Value Reg (CCV) 00000000.201701D0

AR36 User NaT Collection Register (UNAT) 00000000.00000000

AR40 Floating-point Status Reg (FPSR) 0009804C.8A70433F

AR44 Interval Time Counter (ITC) * 00000025.C1B93AF3

AR64 Previous Function State (PFS) 00000000.00001733

AR65 Loop Count Register (LC) 00000000.00000000

AR66 Epilog Count Register (EC) 00000000.00000000


Processor Status Register (IPSR):

AC = 0 MFL= 1 MFH= 0 IC = 1 I = 1 DT = 1

DFL= 0 DFH= 0 RT = 1 CPL= 0 IT = 1 MC = 0 RI = 0

Interrupt Status Register (ISR):

Code 00000000 X = 0 W = 1 R = 0 NA = 0 SP = 0

RS = 0 IR = 0 NI = 0 SO = 0 EI = 0 ED = 1


Branch Registers: Region Registers:

B0 00000000.000D02F0 RR0 * 00000000.00000034

B1 80000000.FFD293D0 RR1 * 00000000.00000030

B2 00000000.00000000 RR2 * 00000000.00000030

B3 00000000.00000000 RR3 * 00000000.00000030

B4 00000000.00000000 RR4 * 00000000.00000030

B5 00000000.00000000 RR5 * 00000000.00000030

B6 00000000.3FF9F1F0 RR6 * 00000000.00000030

B7 00000000.3FFB2A80 RR7 * 00000000.00000334


Floating Point Registers: FPSR 0009804C.8A70433F

F6 00000000.0001003E.00000000.0000E000

F7 00000000.0001003E.00000000.00000007

F8 00000000.0001003E.00000000.00002000

F9 00000000.0001003E.00000000.00000000

F10 00000000.0001003E.00000000.00002000

F11 00000000.0001003E.00000000.00000000


Miscellaneous Registers:

Processor Identifier (CPUID 0,1) GenuineIntel

(CPUID 3) 00000000.1F020204

Interrupt Priority Level (IPL) 0000001F

Stack Align 000002D0

NaT Mask 0030

PPrev Mode 00

Previous Stack 00

Interrupt Depth 00

Preds 80000000.FF5218A3

Nats 00000000.00000000

Context 00000000.FF519AA3


General Registers:

R0 00000000.00000000 GP 00000000.00480000 R2 000007FF.FF800406

R3 000007FF.FFDF0000 R4 00000000.FFCF64C0 R5 00000000.00000004

R6 00000000.00000000 R7 80000000.FED00000 R8 00000000.00000001

R9 00000000.00000000 R10 00000000.00000000 R11 00000000.00000028

SP 00000000.2020B758 TP 00000000.0000040A R14 000000FF.FFFFFFFF

R15 00000000.000048F8 R16 00000000.00000048 R17 00000000.00000000

R18 00000001.FFFFF7C0 R19 FFFFF800.007FF800 R20 FFFFF800.00000000

R21 00000000.00000018 R22 00000000.000048F8 R23 00000000.00001401

R24 00000000.2020BE70 R25 00000000.00000003 R26 00000000.000000FC

R27 00000000.000048FC R28 00000000.00000100 R29 00000000.000000E0

R30 00000000.01000000 R31 00000000.00000004


Interrupted Frame RSE Backing Store , Size = 10 registers


00000000.201FC578: 00000801.FF0003C0 (R32)

00000000.201FC580: 00000000.000048F8 (R33)

00000000.201FC588: 00000000.00001401 (R34)

00000000.201FC590: 00000000.000D02F0 (R35)

00000000.201FC598: 00000000.00001733 (R36)

00000000.201FC5A0: 00000000.00480000 (R37)

00000000.201FC5A8: 000007FF.FF800403 (R38)

00000000.201FC5B0: 00000000.00000000 (R39)

00000000.201FC5B8: 00000000.00000028 (R40)

00000000.201FC5C0: 00000000.000048F8 (R41)


******************************************

* Using INIBRK to get help from Xdelta! *

******************************************

Brk 0 at 000D22E1

000D22E1! break.i 080003

000D22E2! nop.i 000000

does anybody have a clue? is something broken or could it caused by my manipulation?
Volker Halle
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Dario,

you should not set NPAGEDYN or NPAGVIR to -1. This has most likely caused the exception early during boot.

Please consider to have AUTOGEN make the necessary changes:

$ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS FEEDBACK

Then check SYS$SYSTEM:AGEN$PARAMS.REPORT to check, which changes AUTOGEN would have making. Once satisfied, replace the GENPARAMS parameter with SETPARAMS and reboot your system afterwards.

You check in the running system, whether nonpaged pool is getting expanded with:

$ ANAL/SYS
SDA> CLUE MEM/STAT

or

$ SHOW MEM/POOL/FULL

Check whether Nonpaged Dynamic Memory Current Size exceeds Initial Size. It becomes critical, when Current Size is getting near maximum size.

Volker.
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

Thanks Volker for your answer. The server will be repaired in the next few days. What I do not understand: in VMS with Alphas, this limit was set to -1, why is it not the same with I64's? The server crashes running out of "nonpaged pool". So that means I have to increase this number. Do you think autogen will generate sufficient limits?

thanks a lot for your professional help! I really apreciate it.
Dario
Volker Halle
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Dario,

if you look into SYSGEN, you'll see, that the maxium allowed value for NPAGEDYN (and NPAGEVIR) is 1879048192. On both Alpha and Itanium, try $ MC SYSGEN SHOW NPAG

You should have a readable system dumpfile for both of your Integrity rx2620 servers. Try to have a look at the dumps:

$ ANAL/CRASH SYS$SYSTEM:
SDA> CLUE MEM/STAT

do you see non-zero nonpaged pool expansion counters on the first page ?

SDA> SHOW POOL/NONP/SUMM

which packets consume a large amount of nonpaged pool (more than e.g. 10%) ?

SDA> SHOW MEM/POOL/FULL

what values retured for nonpaged pool in the dump ?

Try to find out, how much nonpaged pool your system are using during 'normal' operations. AUTOGEN with FEEDBACK should be able to do this for you. Please note that there could also be software problems (i.e. some nonpaged pool leak), which could cause your pool to be quickly consumed, when a certain event happens. If this would be the casue for your INSF_NONPAGED crashes, tuning won't help !

Volker.
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

Result of
$ ANAL/CRASH SYS$SYSTEM:
SDA> CLUE MEM/STAT

Memory Management Statistics:
-----------------------------
Pagefaults: Non-Paged Pool:
Total Page Faults 912339467 Successful Expansions 725
Total Page Reads 115969375 Unsuccessful Expansions 3812
I/O's to read Pages 79915087 Failed Pages Accumulator 535703
Modified Pages Written 0 Total Alloc Requests 11071129
I/O's to write Mod Pages 0 Failed Alloc Requests 3537
Demand Zero Faults 365961673
Global Valid Faults 275523740 Paged Pool:
Modified Faults 30812568 Total Failures 0
Read Faults 0 Failed Pages Accumulator 0
Execute Faults 0 Total Alloc Requests 213561776
Failed Alloc Requests 0

Direct I/O 3675816600 Cur Mapped Gbl Sections 1083
Buffered I/O 2587534610 Max Mapped Gbl Sections 1089
Split I/O 2557 Cur Mapped Gbl Pages 17018
Hits 3526914412 Max Mapped Gbl Pages 17097
Logical Name Transl 2690695599 Maximum Processes 210
Dead Page Table Scans 0 Sched Zero Pages Created 0


Result of
SDA> SHOW POOL/NONP/SUMM^
Non-Paged Dynamic Storage Pool
------------------------------

NPOOL address: 8F018480
Pool map address: 8802C650
Number of lookaside lists: 160.
Granularity size: 64.
Ring buffer address: 8FC00000
Most recent ring buffer entry: 8FC01160

LSTHDS(s)
---------

LSTHDS Variable Lookaside
address listhead listheads
----------------- ----------------- -----------------
FFFFFFFF.8F017A28 FFFFFFFF.8F017A34 FFFFFFFF.8F017A60

Segment(s)
----------

Start End Length
-------- -------- --------
8801E000 8941DFFF 01400000
8942A000 8EC21FFF 057F8000

Non-Paged total: 06BF8000

Non-Paged Dynamic Storage Pool
------------------------------

Summary of Non-Paged Pool contents
----------------------------------

Packet type/subtype Packet count Packet bytes Percent
--------------------------- ---------------- ---------------- --------
Unknown 00001447 02E35440 (43.2%)
ADP 0000000D 00000AC0 (0.0%)
ACB 00001EE6 0007B980 (0.5%)
AQB 00000005 00000140 (0.0%)
CEB 00000003 00000180 (0.0%)
CRB 00000037 00003C40 (0.0%)
DDB 00000026 00001300 (0.0%)
FCB 00001177 001A3280 (1.5%)
FRK 00000061 000D8B40 (0.8%)
IDB 00000035 00002040 (0.0%)
IRP 00000085 00012B40 (0.1%)
PCB 000000CD 00073500 (0.4%)
RVT 0000003A 0004A040 (0.3%)
TQE 00000086 00002280 (0.0%)
UCB 0000012B 00048700 (0.3%)
VCB 00000004 00000700 (0.0%)
WCB 00000344 00030A40 (0.2%)
BUFIO 00000056 00001E80 (0.0%)
TYPAHD 00000022 00005000 (0.0%)
MVL 00000018 00004300 (0.0%)
NET 00000035 0001B180 (0.1%)
CXB 000005CE 01B16300 (25.3%)
NDB 00000001 00000280 (0.0%)
PFL 0000001E 00016B40 (0.1%)
PTR 0000000D 00003740 (0.0%)
JIB 00000041 000030C0 (0.0%)
TWP 0000000D 00002240 (0.0%)
VCA 0000037F 00CD1080 (12.0%)
CDRP 00000018 000018C0 (0.0%)
CIDG 00000012 00004DC0 (0.0%)
CIMSG 00000048 00004600 (0.0%)
ACL 00000002 00000100 (0.0%)
PMB 00000003 00000180 (0.0%)
ORB 00000165 0000F9C0 (0.1%)
FKB 00001F6D 00180C80 (1.4%)
DCB 00000001 00000080 (0.0%)
VCRP 00000366 00761B80 (6.9%)
......
Total space used: 06B14480 (112280704.) bytes out of 06BF8000 (113213440.) bytes
in 0000B23D (45629.) packets

Total space utilization: 99.2%

Result of SDA> SHOW MEM/POOL/FULL
System Memory Resources from Crashdump on 6-MAR-2008 04:55:28.61
-----------------------------------------------------------------

Nonpaged Dynamic Memory (Lists + Variable)
Current Size (MB) 107.96 Current Size (Pagelets) 221120
Initial Size (MB) 20.00 Initial Size (Pagelets) 40960
Maximum Size (MB) 108.01 Maximum Size (Pagelets) 221216
Free Space (MB) 0.88 Space in Use (MB) 107.07
Largest Var Block (By) 448.00 Smallest Var Block (By) 64.00
Number of Free Blocks 5569 Free Blocks LEQU 64 bytes 1231
Free Blocks on Lookasides 0 Lookaside Space (By) 0.00

Bus Addressable Memory (Lists + Variable)
Current Size (By) 0.00 Current Size (Pagelets) 0
Initial Size (By) 0.00 Initial Size (Pagelets) 0
Free Space (By) 0.00 Space in Use (By) 0.00
Largest Var Block (By) 0.00 Smallest Var Block (By) 0.00
Number of Free Blocks 0 Free Blocks LEQU 64 bytes 0
Free Blocks on Lookasides 0 Lookaside Space (By) 0.00
(Not all BAP data accessible)

Paged Dynamic Memory
Current Size (MB) 9.82 Current Size (Pagelets) 20112
Free Space (MB) 5.18 Space in Use (MB) 4.63
Largest Var Block (MB) 5.16 Smallest Var Block (By) 16.00
Number of Free Blocks 416 Free Blocks LEQU 64 bytes 349

Lock Manager Dynamic Memory
Current Size (MB) 7.12 Current Size (Pages) 912
Free Space (MB) 1.15 Hits 348613
Space in Use (MB) 5.96 Misses 1083
Number of Empty Pages 0 Expansions 1152
Number of Free Packets 4193

What kind of software could cause this problem? We have a lot of self-written software running on the server. How would it be possible?

Volker Halle
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Dario,

thanks for providing the requested detailled data:

There have been: Unsuccessful Expansions 3812

Nonpaged pool has expanded to it's virtual maximum limit:

Current Size (MB) 107.96 Current Size
Initial Size (MB) 20.00 Initial Size
Maximum Size (MB) 108.01 Maximum Size

And then when SYS$SHDRIVER asked for some pool packet and pool couldn't be expanded anymore, the system crashed with INSF_NONPAGED.

The heaviest consumers of pool are:

Unknown 00001447 02E35440 (43.2%)
CXB 000005CE 01B16300 (25.3%)
VCA 0000037F 00CD1080 (12.0%)
VCRP 00000366 00761B80 (6.9%)

These packets together consume 98 out of 112 million bytes of nonpaged pool.

These types of packets seem to all be related to some network protocol and LAN operations. Let me guess: you're using TCPIP ? Do you have the most recent patches installed ?

I'm assuming, that your 'selfwritten software' is not privileged (kernel mode) code. Has something changed before the first INSF_NONPAGED crashes ? Were there some unusual system load conditions immediately preceeding the crashes ?

To find out, which software/driver etc. has allocated all those packets, one would need to analyse the contents of those pool packets.

Volker.
Hakan Zanderau ( Anders
Trusted Contributor

Re: Different VMS V8.3 I64 crashes

I want to make a comment to Vladimirs suggestion about setting parameters directly in SYSGEN ( it was a 10p answer).

It's OK to set parameters directly in SYSGEN, but DON'T FORGET to add the changes to MODPARAMS.DAT ( don't think of it as an option )

If you don't.....next time you run AUTOGEN they will be gone. Autogen is executing the command "USE DEFAULT" ( reset all values ).....and then use the parameters in MODPARAMS.DAT

I have been bitten by this more than once, because its faster to use SYSGEN instead of AUTOGEN.

regards,

Hakan Zanderau
HA-solutions
Don't make it worse by guessing.........
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

Thanks Volker for your answer.
YES, you're right we are using TCPIP. How can I check if the latest patches are installed? I can only see
ina > tcpip sh ver

HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.6
on an HP rx2620 (1.60GHz/6.0MB) running OpenVMS V8.3

do you have a hint how to find out which software/driver allocates those packets?

@Hakan.
thanks for your comment. I made some changes with our I64 in the office, resulted in a crash during startup. The server is repaired now and I will test it with autogen feedback.
labadie_1
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Tcpip sh version, shows, for me
V5.4 - ECO 5

So you do not have any Tcpip patch it appears.

Take it on ftp.itrc.hp.com, and apply it.
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

I installed the latest patch ECO 2 on our testserver. I will do the same with the productive one.

Do you think the "insufficient nonpaged pool" problem will be solved with this action?

at the moment show mem/pool/full is
ina > sh mem/poo/fu
System Memory Resources on 16-APR-2008 14:32:11.96

Nonpaged Dynamic Memory (Lists + Variable)
Current Size (MB) 23.50 Current Size (Pagelets) 48128
Initial Size (MB) 20.00 Initial Size (Pagelets) 40960
Maximum Size (MB) 108.01 Maximum Size (Pagelets) 221216
Free Space (MB) 8.69 Space in Use (MB) 14.80
Largest Var Block (KB) 587.93 Smallest Var Block (bytes) 64
Number of Free Blocks 8281 Free Blocks LEQU 64 bytes 1
Free Blocks on Lookasides 8230 Lookaside Space (MB) 3.00

(Minimum Bus Addressable Memory allocated from Nonpaged Dynamic--run Autogen)

Bus Addressable Memory (Lists + Variable)
Current Size (bytes) 0.00 Current Size (Pagelets) 0
Initial Size (bytes) 0.00 Initial Size (Pagelets) 0
Free Space (bytes) 0.00 Space in Use (bytes) 0.00
Largest Var Block (bytes) 0 Smallest Var Block (bytes) 0
Number of Free Blocks 0 Free Blocks LEQU 64 bytes 0
Free Blocks on Lookasides 0 Lookaside Space (bytes) 0

Paged Dynamic Memory
Current Size (MB) 9.82 Current Size (Pagelets) 20112
Free Space (MB) 5.20 Space in Use (MB) 4.61
Largest Var Block (MB) 5.18 Smallest Var Block (bytes) 16
Number of Free Blocks 425 Free Blocks LEQU 64 bytes 356

Lock Manager Dynamic Memory
Current Size (MB) 4.62 Current Size (Pages) 592
Free Space (MB) 0.81 Hits 36459
Space in Use (MB) 3.81 Misses 533
Number of Empty Pages 0 Expansions 602
Number of Free Packets 3002 Packet Size (bytes) 0
labadie_1
Honored Contributor

Re: Different VMS V8.3 I64 crashes

>>>Do you think the "insufficient nonpaged pool" problem will be solved with this action?

No

What specific software do you start on this node ?
Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

ina > ss
OpenVMS V8.3 on node ALESA1 16-APR-2008 15:01:58.40 Uptime 6 03:22:13
Pid Process Name State Pri I/O CPU Page flts Pages
20200401 SWAPPER HIB 16 0 0 00:01:12.74 0 0
20200407 CLUSTER_SERVER HIB 14 11 0 00:00:00.05 127 164
20200408 SHADOW_SERVER HIB 5 1120008 0 00:00:29.15 111 151
20200409 CONFIGURE HIB 9 36 0 00:00:00.01 101 105
2020040A USB$UCM_SERVER HIB 5 155 0 00:00:00.09 205 434
2020040B LANACP HIB 14 78 0 00:00:03.12 157 207
2020040D FASTPATH_SERVER HIB 10 8 0 00:00:00.00 108 134
2020040E IPCACP HIB 10 8 0 00:00:00.09 78 109
2020040F ERRFMT HIB 8 33789 0 00:00:02.56 159 196
20200410 CACHE_SERVER HIB 16 5 0 00:00:00.00 66 87
20200411 OPCOM HIB 7 6708 0 00:00:00.59 211 101
20200412 AUDIT_SERVER HIB 10 867 0 00:00:00.09 169 213
20200413 JOB_CONTROL HIB 9 1991450 0 00:00:57.24 120 186
20200417 SECURITY_SERVER HIB 10 1100562 0 00:01:06.58 449 594
20200418 ACME_SERVER HIB 10 79 0 00:00:02.95 381 522 M
20200419 QUEUE_MANAGER HIB 10 2714 0 00:00:00.74 197 271
2020041B SMISERVER HIB 9 43 0 00:00:00.05 238 272
2020041C TP_SERVER HIB 9 35471 0 00:00:05.88 426136 112
2020041D NETACP HIB 10 4858 0 00:00:00.16 132 231
2020041E EVL HIB 6 9697 0 00:00:00.65 229 206 N
2020041F REMACP HIB 8 8 0 00:00:00.00 70 72
20200426 TCPIP$INETACP HIB 10 8600 0 00:02:06.78 395 362
2028A027 RS4 LEF 4 3083 0 00:00:00.38 539 447
2020142B A_bb_Restart HIB 6 57251 0 00:00:00.64 532 332
2020142C A_bb_b_r LEF 4 27593494 0 00:06:19.21 291 304 S
20284C38 RO1 LEF 6 799639 0 00:00:44.82 580 529
2020043D INAL02 LEF 9 1298 0 00:00:00.19 3390 147
20276449 RS1 LEF 4 498477 0 00:00:24.99 593 557
20201453 A_bb_sup HIB 4583944070 0 00:58:49.99 403 411 S
20201454 A_bb_dl01 LEF 6 102 0 00:00:00.04 219 219 S
20201455 A_bb_dl02 LEF 6 102 0 00:00:00.07 219 219 S
20201456 A_bb_dl03 LEF 6 102 0 00:00:00.04 219 219 S
20201457 A_bb_dl04 LEF 5 102 0 00:00:00.01 219 219 S
20201458 A_bb_dl05 LEF 6 102 0 00:00:00.07 219 219 S
20201459 A_bb_dl06 LEF 6 102 0 00:00:00.04 219 219 S
2020145A A_bb_dl07 LEF 6 102 0 00:00:00.02 219 219 S
2020145B A_bb_dl08 LEF 6 102 0 00:00:00.08 219 219 S
2020145C A_bb_dl09 LEF 6 102 0 00:00:00.02 219 219 S
2020145D A_bb_dl10 LEF 6 102 0 00:00:00.05 219 219 S
2020145E A_bb_dl11 LEF 6 102 0 00:00:00.04 219 219 S
2020145F A_bb_dl12 LEF 6 102 0 00:00:00.04 219 219 S
20201460 A_bb_dl13 LEF 6 102 0 00:00:00.05 219 219 S
20201461 A_bb_dl14 LEF 6 102 0 00:00:00.07 219 219 S
2028A475 RS5 LEF 4 163310 0 00:00:10.78 585 541
2028AC9D RS2 LEF 4 613259 0 00:00:32.09 620 577
2028B4DD TCPIP$FTPC1C730 LEF 8 220 0 00:00:00.06 477 427 N
2028FCDF TCPIP$FTPC1C732 LEF 9 3335 0 00:00:00.28 477 427 N
202904E0 TCPIP$FTPC1C733 LEF 8 221 0 00:00:00.05 477 427 N
202904E1 TCPIP$FTPC1C734 HIB 8 111 0 00:00:00.01 414 372 N
2026B8E2 TCPIP$FTPC1C735 HIB 9 97 0 00:00:00.01 415 373 N
202610E3 TCPIP$FTPC1C736 LEF 10 98 0 00:00:00.04 414 372 N
2028E0E4 TCPIP$FTPC1C737 LEF 8 104 0 00:00:00.00 375 333 N
2028FCE8 _TNA717: LEF 4 21567 0 00:00:01.80 547 468
2028F0FE RS3 LEF 8 186546 0 00:00:09.92 568 498
2026CD11 _TNA532: LEF 4 1729346 0 00:02:30.14 597 568
2027AD17 _TNA627: LEF 4 3422286 0 00:02:35.45 605 571
2028BD52 _TNA718: LEF 4 18135 0 00:00:01.88 547 468
2028D96A _TNA711: LEF 4 141926 0 00:00:06.29 577 519
2027AD92 _TNA628: LEF 4 790455 0 00:01:07.73 537 451
202721B5 _TNA565: LEF 4 3244064 0 00:03:18.07 643 639
202879BE _TNA681: LEF 6 538629 0 00:00:32.95 603 570
2028EDD5 INA CUR 0 4 166693 0 00:00:11.45 2191 216
2028C610 RO2 LEF 9 1464392 0 00:00:51.18 558 481
20204A11 CPU LEF 4 2265191 0 00:03:29.44 537 451
2027C657 Ina_Process_Log HIB 5 28652479 0 00:11:51.26 1031 854
2027C658 Ina_Restart HIB 6 228102 0 00:00:11.27 518 326
20279E59 Ina_Params HIB 5 652854 0 00:00:09.92 150 190 S
2027525A Ina_Nets HIB 4 85977 0 00:00:06.19 221 248 S
2027D25B Ina_Meas HIB 4 478363 0 00:00:52.06 159 199 S
20275A5C Alarms_html_log HIB 5 38 0 00:00:00.01 148 185 S
2027C65D Wago_Log HIB 6 38 0 00:00:00.02 141 178 S
2027C65E Ina_Monitor LEF 4 3386115 0 00:04:01.82 157 197 S
2027C65F WAGO01 HIB 4 2038 0 00:00:00.15 219 241 S
2027C660 WAGO02 HIB 5 353013 0 00:00:05.87 211 233 S
2027C661 WAGO03 HIB 5 631687 0 00:00:12.55 211 233 S
2027C662 WAGO04 HIB 4 352338 0 00:00:05.59 218 240 S
2027C663 WAGO05 HIB 4 2041 0 00:00:00.14 219 241 S
2027C664 WAGO06 HIB 4 2051 0 00:00:00.14 219 241 S
2027C665 ALARMS_HTML_01 HIB 5 2594835 0 00:07:42.03 178 218 S
2027C666 ALARMS_HTML_02 HIB 4 2587009 0 00:09:06.60 178 232 S
2027C667 ALARMS_HTML_03 HIB 4 2559123 0 00:11:53.76 178 218 S
2027C668 ALARMS_HTML_04 HIB 4 2550258 0 00:13:20.80 185 239 S
2027C269 ALARMS_HTML_05 HIB 4 2543430 0 00:16:39.42 178 232 S
20276E6A ALARMS_HTML_06 HIB 4 2544772 0 00:17:18.26 178 232 S
2028C286 _TNA690: LEF 5 79657 0 00:00:07.20 555 483
2028FA92 INFO LEF 4 84204 0 00:00:04.75 593 560
202612AE TCPIP$FTP_1 LEF 8 14199212 0 00:06:26.11 1536 1358 N
202826B0 _TNA663: LEF 5 272821 0 00:00:20.07 578 527
20283AB8 _TNA649: LEF 4 1640098 0 00:01:30.83 596 555

TCPIP with a some FTP connections, TELNET for the userlogin, some WAGO TCPIP connections, some TCPIP BITBUS connections, and some processes which generate HTML files (Alarms_html).

How can I monitor the nonpaged pool? Which are the critical limits?
Thanks for you help and time.
Volker Halle
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Dario,

these are the 3 numbers to watch for nonpaged pool:

Current Size (MB) 23.50
Initial Size (MB) 20.00
Maximum Size (MB) 108.01

In this case, the initial value of NPAGEDYN was a little bit too small, as nonpaged pool has already been extended, go for 25 MB, if this data was obtained after typical usage of the system.

It is becoming critical, if the current value is about to reach maximum size (NPAGEVIR), then you're are likely to see crashes.

Volker.
labadie_1
Honored Contributor

Re: Different VMS V8.3 I64 crashes

Hello

You have an unusual number of subprocesses...
That can be normal.

Monitor the non-paged-pool ?

As Volker said, do regularly a
SDA> set log mytempfile
SDA> SHOW POOL/NONP/SUMM

to see how it changes, and how much "unknown" do you have ?

And look for the failed pool expansion , with something as simple as, for example every hour
$ mc agen$feedback
$ sea sys$system:agen$feedback.dat npagedyn_allocfail

Dario Karlen
Frequent Advisor

Re: Different VMS V8.3 I64 crashes

Thanks a lot guys.
I will install the latest TCPIP patch and keep an eye on the system. I hope it will run stable now. I will post the result here if any problem occur.