Tim Peiffer wrote: > I am using a calendar event to summarize multicast traffic on campus and > look for bandwidth anomalies. The output is checked for things like > excessive multicast SDP announcements (Plug and Pray). If run from > command line, the exit status is always 0. If run as part of the > calendar event, the exit status appears to be something like 255, and I > can't seem to influence that exit status. > > I am using SingleWith2Thresholds - I would like to mark when a > Source/Group tuple go above a given bandwidth or packet limit, and then > mark when they go below.. > > What am I doing wrong that would cause problems with shell exit status.. > comments? log and config snippets below. > > Regards, > Tim Peiffer > > Tue Nov 18 09:25:00 2008: Spawning shell command > '/usr/local/nts/bin/multicast-summary -quiet -band 100' > Tue Nov 18 09:25:00 2008: Child 32694 created for command > '/usr/local/nts/bin/multicast-summary -quiet -band 100' > Tue Nov 18 09:25:17 2008: Creating event 'Target: InfoTech-CN-01 Group: > 224.77.2.123 (undefined) Source: 134.84.63.128 Rate: 3542 pps/ 42336 > kbps' (received from child 32694) > Tue Nov 18 09:25:22 2008: Creating event 'Target: KoltH-CN-01 Group: > 224.77.2.123 (undefined) Source: 134.84.7.104 Rate: 1515 pps/ 18108 > kbps' (received from child 32694) > Tue Nov 18 09:25:32 2008: Creating event 'Target: ScottH-CN-01 Group: > 224.77.2.124 (undefined) Source: 134.84.210.101 Rate: 3764 pps/ 44996 > kbps' (received from child 32694) > Tue Nov 18 09:25:39 2008: Child 32694 terminated with non-zero exitcode > 255 ( /usr/local/nts/bin/multicast-summary -quiet -band 100 )
The SEC log indicates that the child process was successfully created (pid 32694). From the log it is also evident that the child process was able to run for 39 seconds and then terminated with exit code 255. There is one guess that I came to my mind -- if you call die() from a Perl program, this should produce exit value 255. So if the /usr/local/nts/bin/multicast-summary program is written in Perl, check for possible die() statements in it. Also, you could try to start this program with its standard error redirected to a file (multicast-summary -quiet -band 100 2>>somefile), then check the file for error messages that 'multicast-summary' might produce. BR, risto > > type=calendar > desc = Look for unusual multicast traffic every 5 minutes > time=0,5,10,15,20,25,30,35,40,45,50,55 * * * * > action= spawn /usr/local/nts/bin/multicast-summary -quiet -band 100 > > type=SingleWith2Thresholds > desc=multicast bandwidth greater than %Bandwidth Kbps > continue=takenext > window=1 > ptype=regexp > pattern=Target: (\S+) Group: (\S+) Source: (\S+) Rate: (\d+)pps/ (\d+) kbps > context = =(($5 > %Bandwidth ) && ($2 eq '239.255.255.250')); > action = event 0 Target: $1 Group: $2 Source: $3 packets %s > thresh=1 > window2=1 > desc2=multicast bandwidth dropped below 10Mbps > pattern2=Target: (\S+) Group: (\S+) Source: (\S+) Rate: (\d+)pps/ (\d+) kbps > action2 = event 0 Target: $1 Group: $2 Source: $3 packets %s > context2= =($5 < %Bandwidth ) > thresh2=0 > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
