[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [hobbit] Hobbit bbtest-net crashing

Hi Henrik

Does 4.2.2 RC? use C-ARES 1.2.1, 1.4.0 or 1.5.3?
Or have you not made any changes that drastic? 

We got a test server up and running 4.2 with patches and C-ARES 1.4.0, and we will see if it also crashes.

Cheers
    V


-----Original Message-----
From: Henrik Størner [mailto:henrik (at) hswn.dk] 
Sent: Tuesday, 18 November 2008 11:06 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Hobbit bbtest-net crashing

In <A3D12FAD74FC8B46991703F40C182BABA20D5B4F (at) permls102.wde.woodside.com.au> "Everett, Vernon" <Vernon.Everett (at) woodside.com.au> writes:

>--_000_A3D12FAD74FC8B46991703F40C182BABA20D5B4Fpermls102wdewoo_
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: quoted-printable

>Below are our 5 most recent cores.
>And the corresponding entry in the bb-network.log file where available. 
>(No= t all generate the entry in the log file)

It seems the problems occur in the C-ARES library which is used for hostname lookups (via DNS).

Hobbit 4.2.0 uses version 1.2.1 of C-ARES; the current version is 1.5.3.
Unfortunately there's been a small change of the C-ARES API, so we cannot just drop version 1.5.3 of the library into Hobbit 4.2.0. But it would be nice to know if the problem is still there in the latest version.

If you want to try that, you can grab version 1.4.0 from http://c-ares.haxx.se/c-ares-1.4.0.tar.gz and then change Hobbit's
build/Makefile.rules: The "ARESVER" setting should be "1.4.0".
Then "make clean; rm -rf bbnet/c-ares/* bbnet/libcares.*; make"
and copy bbnet/bbtest-net to ~hobbit/server/bin/

If you want to try out the 1.5.3 version, drop me a mail and I'll send you the patches needed for this to compile with Hobbit 4.2.0.



NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.