Re: Nonpaged pool expansion due to burst of OPCOM DECnet messages

AEF wrote:
Recently my company's network in its NY office went mostly down. This
caused a major flood of OPCOM messages from DECnet about adjacency
being up and down and such. The result was that nonpaged pool expansion
occurred in varying amounts on many of my VAX systems. On nine of the
systems the expansion went all the way to the max: NPAGEVIR.

I found an old comp.os.vms thread saying that a burst of OPCOM messages
can rapidly exhaust nonpaged pool. OK.

Questions: (I'm running VMS 6.2 VAX)

1.) Is there a patch? I searched through all the release notes for
non-paged and didn't see anything relevant.

2.) Anything to do except to reboot to reclaim locked-up memory? IOW,
is there a way to protect against this, or something?

3.) I thought running out of nonpaged pool was bad and could cause a
system crash. None of my systems crashed from this. What saved me?

Thanks.

AEF

AEF,

Running out of pool can indeed cause a crash, but if the shortfall is
momentary, one can be lucky.

In your case, as described in the posting, it would appear that the
burst of messages caused the pool to expand, and luckily the transient
condition of full pool did not obstruct anything important [this time].

I doubt that there is anything that can be done. On the other hand, are
the systems affected by this pool expansion operating in an abnormal
way? If normal operation is ongoing, without ill effects, there is no
operational problems.

- Bob Gezelter, http://www.rlgsc.com

.

Relevant Pages

  • Re: Nonpaged pool expansion due to burst of OPCOM DECnet messages
    ... The result was that nonpaged pool expansion ... I found an old comp.os.vms thread saying that a burst of OPCOM messages ...
    (comp.os.vms)
  • Re: how to interpret poolmon output, Proc tag.
    ... I indeed also have a leak associated to the 'Toke' tag in the paged pool. ... and reboot my computer regularly. ... the minimum nonpaged pool size is actually 128MB. ...
    (microsoft.public.windowsxp.general)
  • Re: how to interpret poolmon output, Proc tag.
    ... the minimum nonpaged pool size is actually 128MB. ... my previous last reboot this problem did not occur, ... Another weird thing is the process identifier PID in the task manager ...
    (microsoft.public.windowsxp.general)
  • Re: Pagefile use increase when repeatedly executing programs
    ... Using Performance Monitor to Identify a Pool Leak ... as my pagefile use steadily increases, ... scanner, updated my computer bios, defragmented memory and pagefile, ... You could confirm that by doing a perfmon on the Nonpaged Pool objects ...
    (microsoft.public.windowsxp.general)
  • Re: Event ID 2017
    ... Adding a switch should not make any difference to this, I don't think that would be the problem, but maybe when you added the switch you changed another setting by mistake. ... You can also monitor the Server Object Pool Counters to see if anything there looks amiss, specifically the Pool Nonpaged Failures and the Pool Paged Failures, if you get values of 1 or more on these counters you probably don't have enough RAM in the machine. ... "The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations." ...
    (microsoft.public.windowsxp.help_and_support)