RE: buffer lock error

• Previous message: Rafael A. Reta Rodriguez: "Cisco configuration problem"
• Maybe in reply to: Tom Holbrook: "buffer lock error"
• Next in thread: Tom Holbrook: "RE: buffer lock error"
• Reply: Tom Holbrook: "RE: buffer lock error"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Tom,

I experienced the same problem on my busiest collectors. I found that
increasing PKTBUFSIZE (the size of the shared memory space used for packet
buffering) helped. I kept doubling the size until the errors stopped. I'm
presently running with PKTBUFSIZE at 8MB.

Hope this helps.

-Martin

-- 
"Buying a car because it's reliable is like marrying
someone because they are punctual" - Jeremy Clarkson
> -----Original Message-----
> From: Tom Holbrook [mailto:tomhol@mindspring.net]
> Sent: Friday, 22 December 2000 00:30
> To: cflowd@caida.org
> Subject: buffer lock error
> 
> 
> I have cflowd running on a test platform (Linux) listening to
> a very heavily loaded router. It is collecting data, but
> repeatedly gives the following message when traffic is heavy.
> 
> Does this just mean I need a more substantial platform?
> 
> Dec 21 18:19:04 salieri cflowd[757]: [E] 
> semop(0,0xbfe678ec,1) failed to 
> release buffer lock: Resource temporarily unavailable 
> {CflowdPacketQueue.cc:438}
> 
> Thanks
> -Tom
> 
> __________________
> Tom Holbrook
> Network Engineer
> Atlanta
> Earthlink
> 
> --
> cflowd mailing list
> cflowd@caida.org
> 
--
cflowd mailing list
cflowd@caida.org

• Next message: Devin Anderson: "RE: Cisco configuration problem"
• Previous message: Rafael A. Reta Rodriguez: "Cisco configuration problem"
• Maybe in reply to: Tom Holbrook: "buffer lock error"
• Next in thread: Tom Holbrook: "RE: buffer lock error"
• Reply: Tom Holbrook: "RE: buffer lock error"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Dec 27 2000 - 03:20:10 PST