Re: Post-build test fail on BIND 9, old system - DNS

This is a discussion on Re: Post-build test fail on BIND 9, old system - DNS ; Bruce Esquibel napisal(a): > > Reason I'm saying that, not sure why but there is a couple spots in the test > suite for BIND 9.5.0-P1 that has "grep -q" hardcoded which causes several > failures under Solaris. As far ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: Post-build test fail on BIND 9, old system

  1. Re: Post-build test fail on BIND 9, old system

    Bruce Esquibel napisal(a):
    >
    > Reason I'm saying that, not sure why but there is a couple spots in the test
    > suite for BIND 9.5.0-P1 that has "grep -q" hardcoded which causes several
    > failures under Solaris. As far as I can tell, -q (for quiet) is only
    > supported on the gnu grep (ggrep).
    >
    > Besides causing some tests to get bypassed, I think it does eventually fail
    > altogether because of something missing from the grep output (maybe wrong
    > about that).


    I have noticed that at first (grep complains about unknown "-q" option in
    the test output) and fixed that. "/usr/xpg4/bin/grep" should be used instead
    of simply "grep", that version does accept the "-q" parameter.
    The failing tests I have mentioned have nothing to do with this issue.

    However, I am in the process of investigating them in detail, and the first
    test (cacheclean) is probably failing because the "dig" program included
    with BIND is for some reason unable to fetch data from the nameserver (a
    message "/dysk4/soft/bind-9.5.0-P1/bin/dig/dig: isc_socket_bind: socket
    already bound" appears and the file expected to contain output from dig is
    empty). Don't know about the others yet...
    Regards,
    Jaroslaw Rafa
    raj@ap.krakow.pl
    --
    Zapraszam na moja nowa strone: http://www.ap.krakow.pl/~raj/



  2. Re: Post-build test fail on BIND 9, old system

    Jaroslaw Rafa wrote:

    > However, I am in the process of investigating them in detail, and the first
    > test (cacheclean) is probably failing because the "dig" program included
    > with BIND is for some reason unable to fetch data from the nameserver (a
    > message "/dysk4/soft/bind-9.5.0-P1/bin/dig/dig: isc_socket_bind: socket
    > already bound" appears and the file expected to contain output from dig is
    > empty). Don't know about the others yet...



    I think Solaris 2.5.1 didn't support multiple addresses on an interface
    (again could be wrong) so the "already bound" message makes sense.

    I'm pretty sure you are going to have to shut down the named that is
    running, if that is the case. You might even have to go to an extreme and
    get the box into single user mode to run the tests.

    Sorry if this is going to mislead you, I haven't seen a 2.5.1 box in
    probably 10 years, we took posession of them when another isp in the area
    went out of business but only kept them running long enough to migrate
    the users. Pretty sure Solaris 8 was out then and it was a night and day
    difference "getting stuff to work" like this on 8 over the older versions.

    But I'm confident with the way the test suite works and how the 2.5.1
    handles ip addresses on the interfaces, there is an incompatabily there.

    Hope I'm wrong but like I said earlier, you have a pretty good uphill battle
    on your hands.

    -bruce
    bje@ripco.com


+ Reply to Thread