rastream stopped processing

[Carter Bullard]

Did radium stop collecting or sending ??  We’ve got some
reports on reliable connection failure, so it maybe your
rastream() disconnected and didn’t reconnect ????

check out your system log /var/log/messages /var/log/system.log
to see if radium complained about the client going away, or if
radium stopped reading.  If radium is still running you can just
connect to it, to see if its transmitting anything.

If there is a problem, and you’ve compiled with symbols in (.devel),
then attach to radium with gdb() and look to see if any of the
threads have terminated.

(gdb) attach pid.of.radium
(gdb) info threads
(gdb) thread 1
(gdb) where
(gdb) thread 2
(gdb) where

etc ….. may not be exact syntax, but its something like that.
With all the various end systems using clang and lldb, I’m kind
of schizophrenic on debugging right now.

Carter


On Jul 7, 2014, at 4:28 PM, Jesse Bowling <jessebowling at gmail.com> wrote:

> Hello,
> 
> Over the weekend my rastream process stopped processing records for some reason. The current setup is:
> 
> netflow records -> radium -> rastream -M time 5m
> 
> I noticed that records were no longer being written to disk. I connected a new ra instance to radium, and had no problems receiving records. Attaching strace to the rastream process all I could see were calls:
> 
> <snip>
> nanosleep({0, 50000000}, NULL)          = 0
> nanosleep({0, 50000000}, NULL)          = 0
> nanosleep({0, 50000000}, NULL)          = 0 
> <snip>
> 
> Is there any settings I can tweak or logs to check for or correct the issue? I vaguely recall something about persistent connections where if lost an attempt would be made to reconnect, but my gut says that’s not what’s happening here...
> 
> Cheers,
> 
> Jesse

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20140708/bcff844b/attachment.sig>