larry@nstar.uucp (Larry Snyder) (10/07/90)
I noticed the error: Problem with ptr packet: OVERFLOW
when running X release 1.2 this afternoon - what does this mean?
--
Larry Snyder, Northern Star Communications, Notre Dame, IN USA
{larry@nstar, uunet!sco!romed!nstar!larry, nstar!larry@ndmath.math.nd.edu}
backbone usenet newsfeeds available
Public Access Unix Site (219) 289-0282 (5 high speed lines)support@ism780c.isc.com (Support account) (10/10/90)
In article <1990Oct06.221058.251@nstar.uucp> larry@nstar.uucp (Larry Snyder) writes: >I noticed the error: Problem with ptr packet: OVERFLOW >when running X release 1.2 this afternoon - what does this mean? > This generally indicates that the system is running out of the streams resources NSTREAM, NQUEUE, or NBLKxxx. Try running "netstat -m" to observe system usage statistics, and increase these tunables accordingly. ...
cpcahil@virtech.uucp (Conor P. Cahill) (10/10/90)
In article <49335@ism780c.isc.com> support@ism780c.UUCP (Support account) writes: >In article <1990Oct06.221058.251@nstar.uucp> larry@nstar.uucp (Larry Snyder) writes: >>I noticed the error: Problem with ptr packet: OVERFLOW >>when running X release 1.2 this afternoon - what does this mean? >> >This generally indicates that the system is running out of >the streams resources NSTREAM, NQUEUE, or NBLKxxx. Try running >"netstat -m" to observe system usage statistics, and increase >these tunables accordingly. The crash command provides a much better mechanism for viewing the streams statistics. Just log in as root, run crash (with no arguments) and then enter "strstat" which will get you something like the following: ITEM CONFIG ALLOC FREE TOTAL MAX FAIL streams 512 25 487 478 61 0 queues 2048 130 1918 1341 324 0 message blocks 4230 79 4151 6617556 283 0 data block totals 3384 79 3305 4911153 282 0 data block size 4 512 0 512 85157 6 0 data block size 16 512 18 494 679478 60 0 data block size 64 512 3 509 3906377 53 0 data block size 128 1024 58 966 224160 181 0 data block size 256 256 0 256 5410 6 0 data block size 512 256 0 256 6219 3 0 data block size 1024 128 0 128 2443 4 0 data block size 2048 128 0 128 1904 5 0 data block size 4096 56 0 56 5 1 0 (which shows that I am majorly overallocated for just about all of these). -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170
cpcahil@virtech.uucp (Conor P. Cahill) (10/11/90)
In article <1990Oct10.122531.9153@virtech.uucp> I wrote: >In article <49335@ism780c.isc.com> support@ism780c.UUCP (Support account) writes: >>This generally indicates that the system is running out of >>the streams resources NSTREAM, NQUEUE, or NBLKxxx. Try running >>"netstat -m" to observe system usage statistics, and increase >>these tunables accordingly. > >The crash command provides a much better mechanism for viewing the >streams statistics. I should have tested netstat -m before I posted my response. Contrary to the manual the netstat -m does not show the network private buffer statistics, it shows the streams statistics. The output of strstat in crash is almost exactly the same as the output from netstat -m (although netstat -m is *much* faster and may be run by mere mortals). Sorry for the confusion. -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170