Sorry for a late summary. I got replies from
Laurent DENIEL and Hakim Shlomo pointing out problems with kloadsrv.
Restarting kloadsrv makes both netstat and arp work again.
Shlomo wrote:
"We have encountered a very similar problem soon after we upgraded to 4.0D.
After some investigation I found that the cause for all of this is the
kloadsrv daemon. It simply quit. After restarting it both netstat and arp
started working again.
The connection between kloadsrv and netstat command is the knlist() function
that is used by netstat to retrieve the information from the running kernel.
I tried to run the kloadsrv daemon with debug information (-d flag) but
couldn't (it is working on 4.0B) at times it would just quit after printing
a few lines and at other times it would core-dump.
We are currently waiting for a response from DEC on this issue."
-----Original Message-----
On some of my 4.0D-machines I get the following response:
# arp -a
arp: bad namelist
# netstat -r
no namelist
Others work correctly. In the archives I found the following:
>Yes I had the same problem on DU4.0B. After a reboot, it works ok but
>as soon as I start a complex network application, netstat fails. Note
>that there is no other problems (except the failure of the command).
>This is only the communication between netstat and a daemon that fails...
Is this a bug? Rebooting the machines to get some programs to work sounds
no good. Has anyone got a solution, workaround, something???
---------------------------
********************************************************************
Kalle Flodkvist
Uppsala universitet
IT Stöd
Box 887 Email: Kalle.Flodkvist_at_its.uu.se
751 08 UPPSALA Fax: +46 18 471 79 10
Sweden Telephone: +46 18 471 78 63
********************************************************************
Received on Thu Aug 13 1998 - 15:43:43 NZST