rastream fails

James Grace jgrac002 at fiu.edu
Wed Jun 18 11:29:01 EDT 2014


Hi Carter,

I didn't see anything in any of my logs.  The rastream command I'm running
is:

rastream -S localhost -M time 5m -w /home/flows/South/%Y/%m/%d/argus.%H.%M
-D 8 2>/home/flows/rastream.err &


Will this capture the exceptions thrown to stderr appropriately? Or is
there a more 'argus-y' way of doing this?


Thanks,

-james




On Wed, Jun 11, 2014 at 11:24 AM, Carter Bullard <carter at qosient.com> wrote:

> Hey James,
> rastream doesn’t write out these types of messages, so its a little weird.
> Seems like this maybe coming from the script that you’ve got rastream
> running ???
>
> rastream will exit for all the standard reasons that a ra* program
> exits for, such as the argus data source hanging up, internal
> failure, or in rastream’s case, if there is a major problem forking
> the script that it is suppose to run. It should generate syslog messages
> to indicate any errors.  Anything in your system log ???
>
>
> Carter
>
> On Jun 11, 2014, at 10:07 AM, James Grace <jgrac002 at fiu.edu> wrote:
>
> Good morning all,
>
> I've been using rastream to connect to my argus client to split up traces
> into 5 minute interval and store them neatly.
>
> I've been running into a problem after about 48 hours of operation where
> the rastream process closes. I finally ran it with -D 3 and piped the
> output to a file so here's the error message I'm receiving:
>
> Write failed: Broken pipe
>
> Time spent in user mode   (CPU seconds) : 8.348s
>
> Time spent in kernel mode (CPU seconds) : 5.514s
>
> Total time                              : 47:31:15.22s
>
> CPU utilisation (percentage)            : 0.0%
>
> Times the process was swapped           : 0
>
> Times of major page faults              : 74
>
> Times of minor page faults              : 1583
>
> Exit 255
>
> Any clues on this?
>
>
> thanks much,
>
> -james
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20140618/02b6ce80/attachment.html>


More information about the argus mailing list