ArgusWriteOutSocket(0xd40bb1e0) max queue exceeded 500001

[John Gerth]

It's been my experience that the max queue exceeded message is indicative of
a problem that won't be fixed by upping the limit (can't remember if it's possible
but so much of argus is configurable that it may well be).

What the message is saying is that there are a  half-million queued messages.
Not surprising if radium actually died.

The "dead but subsys locked" message is just a result of the abnormal termination
since radium couldn't or didn't remove the lock file on its way down.

John Gerth      gerth at graphics.stanford.edu  Gates 378   (650) 725-3273 fax 725-6949

On 8/12/2013 12:06 PM, Craig Merchant wrote:
> Hey, Carter…
> 
>  
> 
> I’m still having some issues with radium crashing.  I get that “max queue exceeded” message and then if I check radium’s status, it says:  “radium
> dead but subsys locked”.
> 
>  
> 
> Is the max queue size something that can be adjusted?
> 
>  
> 
> Thx.
> 
>  
> 
> Craig
>