NS3000/iX Error Messages Reference Manual (36923-90041)

Chapter 19 435
Logging Location Codes
Net Timers Logging Location Codes
Net Timers Logging Location Codes
MESSAGE: Out of resources
1020 CLAS0003 CAUSE: A free-pool entry was needed for a timer-entry element, to hold
information about a new net timer being obtained, but the pool was
empty. A separate timer entry must exist for every net timer on the
system.
ACTION: No new timer was obtained. The system is probably operating
under a heavy load. Other processes on the system have used up all the
free timer entries, or are starting timers with granularities so small as
to use up all the pool entries for timer-intervals. Other processes on the
system will probably start seeing this problem as well, though that
should be a temporary condition. One possible workaround is to
configure a higher value in NMMGR for the maximum number of TCP
connections.
MESSAGE: Out of resources
1040 CLAS0003 CAUSE: A free-pool entry was needed for an interval- head element, to
link a net timer into a new interval, but the pool was empty. A new
interval is required whenever there is no open interval positioned
where a timer entry needs one.
ACTION: If the error occurred when getting a new timer, no new timer
was obtained. If it occurred on a reset, the timer was not reset, and has
been left stopped. The system is probably operating under a heavy load.
Other processes on the system have used up all the free timer entries,
or are starting timers with granularities so small as to use up all the
pool entries for timer-intervals. Other processes on the system will
probably start seeing this problem as well, though that should be a
temporary condition. One possible workaround is to configure a higher
value in NMMGR for the maximum number of TCP connections.
MESSAGE: Cannot free a systimer
1060 CLAS0002 CAUSE: When releasing a system timer following a race-condition
when that timer could not be cached, the system routine
Release_timer reported an error. Timers must be released when the
net timer cache is full or not configured (PARM = status from
Release_timer).
ACTION: Unless there is corruption within system timers, this
probably indicates a Net Timers bug. Another remote possibility is that
the Net Timers port data has been corrupted from outside, so other,
possibly serious problems may soon appear as well. In addition, one
system timer may have been lost; if this continues, the system could
eventually run out of system timers. Submit an SR.