radium

[Carter Bullard]

Sorry to be a bit basic, but be sure and run the radii with different radium.conf files,
or with different command line options.

one should connect to argus (ARGUS_SERVER= argus://bivoBox:561),
the other should connect to the radium (ARGUS_SERVER=argus://localhost:562)
with a different RADIUM_ACCESS_PORT.

So, first radium:
   radium -XP 12345 -S bivioBox:561 -D3

second radium:
   radium -XP 23456 -S localhost:12345 -D3

Then the clients should connect to:
   ra -S localhost:23456

Carter


On Jun 8, 2012, at 3:05 PM, CS Lee wrote:

> hi Carter,
> 
> When I just run two radiums, nothing much is happening, it stays okay, the issue is always when argus client connecting to radium then problem will start.
> 
> On Sat, Jun 9, 2012 at 2:56 AM, Carter Bullard <carter at qosient.com> wrote:
> Hey CS Lee,
> So it is very important to debug this, as I think this is one of the keys to the problem.
> And I'm sorry that we have to go through all this effort.  My apologies.
> 
> Not sure that I understand what your presenting below.
> 
> radium is running on the linux box, connecting to argus on the bivio?
> ra connects to radium, runs for 6.5 minutes, and then disconnects?
> 
> Then 2 seconds later, you start another ra connection to radium, ( we get
> the "connect from localhost[127.0.0.1]" ), and that is successful ?
> Are you getting any records?
> 
> This radium is a 3.0.6 radium?  And the clients are 3.0.6 clients?
> 
> what looks like 19 minutes later, radium prints an " idle stream: closing" message
> and closes its connection with argus?
> 
> These two events seem unrelated. radium connecting / disconnecting with the ra* clients,
> and then argus becoming idle.  
> 
> Can you run radium with a " -D3 " option so it will tell us something about what its doing?
> 
> When you get the SIGINT, you should type a few things.
> (gdb) where
> (gdb) info threads
> (gdb) c
> 
> I'm somewhat frustrated, as I do this type of stuff on dozens of different platforms, and none
> of them show this behavior.   Frustrating that its hard to debug.
> 
> I tried to recreate any of this on my machines here, and can't get anything that
> looks similar to your behavior.  It maybe that I will need to access the linux box
> that radium is running on, if we can't make any progress.
> 
> Carter
> 
> 
> On Jun 8, 2012, at 1:40 PM, CS Lee wrote:
> 
>> hi Carter,
>> 
>> This is the radium when runs with gdb 
>> [Thread 0x7ffff4aba700 (LWP 13697) exited]
>> radium[13475]: 23:03:48.178648 connect from localhost[127.0.0.1]
>> radium[13475]: 23:20:11.715904 ArgusCheckClientMessage: client localhost[127.0.0.1] sent DONE
>> radium[13475]: 23:22:53.903480 connect from localhost[127.0.0.1]
>> radium[13475]: 23:41:29.044069 ArgusReadStream 10.0.0.1: idle stream: closing
>> [New Thread 0x7fffcffff700 (LWP 15230)]
>> 
>> Program received signal SIGINT, Interrupt.
>> 0x00007ffff794a8dd in nanosleep () from /lib/x86_64-linux-gnu/libpthread.so.0
>> (gdb) bt
>> #0  0x00007ffff794a8dd in nanosleep ()
>>    from /lib/x86_64-linux-gnu/libpthread.so.0
>> #1  0x000000000046d0e5 in ArgusReadStream (parser=0x7ffff7ea6010,
>>     queue=0xb231e0) at ./argus_client.c:930
>> #2  0x000000000040c1dd in main (argc=3, argv=0x7fffffffe6c8)
>>     at ./argus_main.c:360
>> 
>> I have to control C and exit the radium process, after radium sees the idle stream from argus(10.0.0.1). Then argus client can't connect to both argus and radium to retrieve any data anymore. So I need to restart radium and argus again.
>> 
>> -- 
>> Best Regards,
>> 
>> CS Lee<geek00L[at]gmail.com>
>> 
>> http://geek00l.blogspot.com
>> http://defcraft.net
> 
> 
> 
> 
> -- 
> Best Regards,
> 
> CS Lee<geek00L[at]gmail.com>
> 
> http://geek00l.blogspot.com
> http://defcraft.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20120608/f12f7ad6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4367 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20120608/f12f7ad6/attachment.bin>