List Info

Thread: netbsd 3.0 and name resolution problems




netbsd 3.0 and name resolution problems
user name
2006-05-18 18:27:50
Hey all!

fist the good news. I reported several disk reliability
problems since 
2.0 on my IIci which prevented me to use NetBDS and the box
at all. 
SIice even tinkering with the termination and the
termination power did 
not help, I thought about strange incompatibilities (note:
the disk 
worked perfectly in a Q610 with 1.6 until the box died).

I decided to use one of my spare external HD's to
install... and this 
time netbsd installed fine! Also,m the system seems quite
fine, I left 
it compiling for hours.
my only problems are a general slowness, which may be just
the factg 
that I didn't use such  box since long, but I doubt: the
multitask is 
fine, I think it is maybe something in process start or in
forking or 
the shell or maybe disk IO, I should run bonnie...(configure
scripts are 
very slow)... and some more serious trouble in networking.

I can't telnet into the box. I can ssh though. Further
investigation 
shows name resolution troubles:

frodo:  host www.netbsd.org
/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/isc/uni
x/socket.c:445: 
fcntl(717056, F_SETFL, -1): Bad file descriptor
/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/isc/uni
x/socket.c:2338: 
fatal error:
RUNTIME_CHECK(make_nonblock(manager->pipe_fds[0]) == 0)
failed
Abort trap (core dumped)
frodo:  nslookup www.netbsd.org
/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/isc/uni
x/socket.c:445: 
fcntl(718952, F_SETFL, -1): Bad file descriptor
/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/isc/uni
x/socket.c:2338: 
fatal error:
RUNTIME_CHECK(make_nonblock(manager->pipe_fds[0]) == 0)
failed
Abort trap (core dumped)

very interesting is also trying to solve the machine name:
frodo:  host frodo
/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/dns/sec
/dst/dst_api.c:120: 
REQUIRE(mctx != (void *)0 && ectx != (void *)0)
failed.
Abort trap (core dumped)

I discovered a typo in my hosts file (the domain was spelled
differently 
than in resolv.conf. Still, it shoudln't core dump). Then I
get

frodo:  host frodo
assertion "contextp != (void *)0 && *contextp
== (void *)0" failed: file 
"/home/builds/ab/netbsd-3-0-RELEASE/src/dist/bind/lib/
lwres/context.c", 
line 85, function "lwres_context_create"


Insteresting is that pinging both of the above hosts works.

I am running 3.0 release

and apparenly I don't have scsi lockups, but with whopping
upgraded 
72MBytes of ram... the machine works pretty smooth.

cheers,
   Riccardo
[1]

about | contact  Other archives ( Real Estate discussion Medical topics )