[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Network test time-outs
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Network test time-outs
- From: Larry Barber <lebarber (at) gmail.com>
- Date: Wed, 25 Jan 2006 09:18:25 -0600
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VpcxLA1qJkxxUs+6WR4YsncQcOSPTq55L01vql4sttS+4FHZUumZUWkjvKKGe5Cbyw8EFdbR2DNGDS6cWgjCks6oL57XPDmD6nOl8JWINx9sk/pXC4T7ewmTEJ3SFUQC1/+VIiwQ9AtXtBEskdGBZX4vX5EWshTvdsHtHw8AqBs=
- References: <OFF5203716.64E463C0-ON85257101.005190FB-85257101.00530294@glic.com>
You can increase the timeout value on the bbnet-test program by adding a
-timeout=N to its invocation line in hobbitalerts.cfg. I've found just
increasing it to 15 seconds (from the default 10) makes a huge difference in
the number of timeouts I get.
Thanks,
Larry Barber
On 1/25/06, James B Horwath <JamesHorwath (at) glic.com> wrote:
>
>
> I am having an issue with Hobbit network tests. There are times when
> network or (client) system congestion causes a network test such as SSH to
> fail. The service is not down just slow, I receive a clear almost
> immediately after I receive the down. To keep my sanity I need the network
> value upped. In BB I was able to correct this by setting the variables
> BBNETTIMER[1-3] to higher values. I wasn't able to find such a beast in
> Hobbit. I opened the file bbtest-net.c and found the
> int timeout=10; /* The timeout (seconds)
> for all TCP-tests */
> and
> int extcmdtimeout = 30;
>
> I do not use ICMP as a connectivity test, I use ssh for up/down, to me
> that is more realistic. I searched the mail archives and didn't find
> anything. Can I up the values on the time-out to make the test not fail so
> quickly? Or anybody else have any suggestions on how to work around the
> issue.
>
> Please advise,
> Jim
>
> ------------------------------
>
> * This message, and any attachments to it, may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended
> recipient, you are notified that any use, dissemination,
> distribution, copying, or communication of this message is strictly
> prohibited. If you have received this message in error, please
> notify the sender immediately by return e-mail and delete the
> message and any attachments. Thank you. *
>