rasplit crash

Carter Bullard carter at qosient.com
Tue Mar 25 13:53:52 EDT 2014


Hey Jesse,
Sorry for the delayed response...EAGAIN is a socket condition, not an error, so we should just keep going.  rasplit() is using the code as the other ra* programs, so shiuld be a quick fix.  Let me check this afternoon ...

Sorry again !!
Carter

> On Mar 25, 2014, at 8:50 AM, Jesse Bowling <jessebowling at gmail.com> wrote:
> 
> I'll bump this, as the issue occurred again last night. It would seem that whatever the problem is, it doesn't occur too often (10 days between runs), but it's certainly troubling. Again the error message was:
> 
> Mar 25 03:38:45 host rasplit[16519]: 03/25/14 03:38:45.687977 main: pthread_create ArgusConnectRemotes: EAGAIN 
> 
> Any help on tracking this down? Do I need to run with debug for a while?
> 
> Cheers,
> 
> Jesse
> 
> 
>> On Sat, Mar 15, 2014 at 7:19 PM, Jesse Bowling <jessebowling at gmail.com> wrote:
>> Hello,
>> 
>> I had an rasplit process crash on me, and the only indication in the logs was:
>> 
>> Mar 15 16:26:10 rasplit[2987]: 03/15/14 16:26:10.939859 main: pthread_create ArgusConnectRemotes: EAGAIN 
>> 
>> Any hints on troubleshooting this?
>> 
>> Thanks,
>> 
>> Jesse
>> 
>> -- 
>> Jesse Bowling
> 
> 
> 
> -- 
> Jesse Bowling
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20140325/5927ec10/attachment.html>


More information about the argus mailing list