slow response localhost

[Hr. G. Dirkzwager]

Hello,

i have a hpux server d350 with unix10.20 installed. When i trie to ping to localhost the server gives 5 to 10 seconds later a response. The same happens on the local ip adres. The normal reaction should be an instant response. Does anyone know what can cause this problem? The interface is a Built-in LAN.

[twang]

You may take a look at the content of /etc/nsswitch.conf

[Hr. G. Dirkzwager]

the content of my /etc/nsswitch.conf file is"
hosts: files[NOTFOUND=return UNAVAIL=continue]

Seems oke this way.

[twang]

- you may change
hosts: files[NOTFOUND=return UNAVAIL=continue]

to:

hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return]

and try to test again

- If you have an /etc/resolv.conf file you may wish to remove it.

- do you mean that it is same if you issue "ping 127.0.0.1"?

[Hr. G. Dirkzwager]

I have changed it but no result.

And yes, i meant that if i issue "ping 127.0.0.1" it also take a several seconds before i get a response.

[twang]

Have you tried using "traceroute" to see if you have any network bottlenecks anywhere?

# traceroute localhost

# traceroute

[Massimo Bianchi]

Hi is there any message in the syslog ?
I think of card problems.

Check with: lanadmin or landiag .

Massimo

[Francisco J. Soler]

Hi,

Is the hostname in the /etc/hosts file?

If not, add a line with the hostname and the ip address.

Frank.

[Hr. G. Dirkzwager]

Hi,

- traceroute localhost is giving the same result. a delay and then after a few seconds an answer.

- in the syslog are no errors, i tried also to start inetd with debug mode, but no errors given. lanadmin or landiag are also not refreshing.

- ofcourse the hostname and localhost is in the /etc/hosts file. This problem occurred this morning, so before there was no problem.

Is resetting the interface card with lanadmin an option?

[Massimo Bianchi]

Hi,
in 11.0 there is the option to reset the card, but i don't remember in 10.20.

Remember that, obviously, all network connection will be closed.

Massimo

[Hr. G. Dirkzwager]

Hi,

i found what caused it. There was a process for ypbind, the NIS binder. I killes that process and the problem was over.
Thank you all for help.

[Bill Hassell]

Is the ping delay shown in the ping message? If so, ping is a very low level task and bypasses most of the network stack in HP-UX. This type of delay would indicate a serious network hardware problem. However, if ping reports: time=10 ms or less, then the problem is with name resolution. You will probably see a similar delay with nslookup. Start by renaming /etc/resolv.conf and change /etc/nsswitch.conf to have:

hosts: files

The long delay is a common delay trying to contact a DNS server before failing over to /etc/hosts. Make sure that /etc/nsswitch and /etc/hosts are world-readable.

[Suresh Patoria]

hi,

pls check the /etc/hosts file there is entry for localhost

if it is not there then put the entry then try to ping 127.0.0.1 address
If u trying through ping the name then also check the /etc/nsswitch.conf file for lookup order

set appropriate order

check order through nslookup utility

Thanx.