Re: Health check for iperf?
Tanya,
In the usual course of things, just after I wrote the short script to
check to see if iperf was running and restart if necessary, it hasn't
been a problem at all!
I did use the recommendation from Kevin, I think, who told me to comment
out two lines and the logging mechanism works fine. I added a simple
'date' function and the log file looks pretty good now:
Wed Jul 30 15:59:07 2003
[ 6] local 171.66.6.36 port 5001 connected with 171.66.62.107 port 59752
[ ID] Interval Transfer Bandwidth
[ 6] 0.0-10.0 sec 4.26 MBytes 3.56 Mbits/sec
Wed Jul 30 15:59:34 2003
[ 6] local 171.66.6.36 port 5001 connected with 171.66.62.107 port 59753
[ ID] Interval Transfer Bandwidth
[ 6] 0.0-10.1 sec 2.16 MBytes 1.79 Mbits/sec
Wed Jul 30 16:00:06 2003
[ 6] local 171.66.6.36 port 5001 connected with 171.66.62.107 port 59754
[ ID] Interval Transfer Bandwidth
[ 6] 0.0-10.1 sec 4.46 MBytes 3.72 Mbits/sec
Looking forward to the new program when it is complete.
Thanks!
Phil
Tanya Brethour wrote:
>>I've happily deployed iperf. A wide variety of folks on campus are
>>starting to use the service. However, I occasionally find that iperf on
>>the server quits on me.
>>
>>I start the program with the following command:
>>/usr/local/bin/iperf -s -D >> /var/log/iperf.log
>>
>>I used the slightly modified iperf 1.7.0 source which correctly logs the
>>connections.
>>
>>I can imagine iperf wedging for a number of reasons. Is it worth an
>>effort to discover the reasons why it quits or should I just write a
>>script to restart it if it dies and log the restart time and date?
>>
>>
>
>I have not heard many people suffering from the same problems that you
>are. Do the logs record anything useful? (error messages, etc?).
>
>Our main Iperf developer will be returning in August and has been
>rewriting Iperf. I'm not sure if this will solve your problems, but you
>could wait for that new release (sometime in the fall) and use your
>restart script in the meantime. However, I know that DAST would be very
>interested in anymore information you can provide about why you think it
>is quiting, and some basic info about your machine (os, etc.). That
>information could be helpful during the rewrite.
>
>Thanks,
>Tanya Brethour
>DAST
>
>
>
>
>
>
>