Ping local host fails

[Matsul]

I have a problem that a certain process does not work due to it not finding the license server.

I know it uses localhost to locate the license server. I have local host in my host file as 127.0.0.1 yet ping local hosts shows that it is attempting to ping 212.15.3.7 which isn't even an address in our network.

netstat -rn shows

212.15.3.7 192.168.18.254 UHW

where 192.168.18.254 is the default gateway.

I used route delete to delete the above entry but it learnt it again.

Any ideas ?

 

[bi]

Can you post the line from you /etc/hosts file that has the localhost entry?

 

[Matsul]

Yep, here is the first part of my hostfile . thanks


# @(#)47 1.1 src/bos/usr/sbin/netstart/hosts, cmdnet, bos420, 9613T 7/24/91 10:00:46
# IBM_PROLOG_BEGIN_TAG
# This is an automatically generated prolog.
#
# bos420 src/bos/usr/sbin/netstart/hosts
#
# Licensed Materials - Property of IBM
#
# (C) COPYRIGHT International Business Machines Corp. 1985,1989
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# IBM_PROLOG_END_TAG
#
# COMPONENT_NAME: TCPIP hosts
#
# FUNCTIONS: loopback
#
# ORIGINS: 26 27
#
# (C) COPYRIGHT International Business Machines Corp. 1985, 1989
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# /etc/hosts
#
# This file contains the hostnames and their address for hosts in the
# network. This file is used to resolve a hostname into an Internet
# address.
#
# At minimum, this file must contain the name and address for each
# device defined for TCP in your /etc/net file. It may also contain
# entries for well-known (reserved) names such as timeserver
# and printserver as well as any other host name and address.
#
# The format of this file is:
# Internet Address Hostname # Comments
# Items are separated by any number of blanks and/or tabs. A '#'
# indicates the beginning of a comment; characters up to the end of the
# line are not interpreted by routines which search this file. Blank
# lines are allowed.

# Internet Address Hostname # Comments
# 192.9.200.1 net0sample # ethernet name/address
# 128.100.0.1 token0sample # token ring name/address
# 10.2.0.2 x25sample # x.25 name/address
127.0.0.1 localhost
127.0.0.1 loopback localhost # loopback (lo0) name/address
127.0.0.1 test

 

[dlpar]

This line is enough for the local host:
127.0.0.1 loopback localhost
At least another one is necessary for your machine:
x.x.x.x hostname-machine

what about the result of netstat -rn?

 

[bi]

Try commenting out the line 127.0.0.1 test. Then refresh or restart inetd. If that doesn't solve it, take out the 127.0.0.1 localhost line and refresh or restart inetd. I just have:

127.0.0.1 loopback localhost # loopback (lo0) name/address

and I've never had this problem.

 

[Matsul]

thanks, any idea how to restart inetd + will users loose their connection

 

[bi]

stopsrc -p <inetd PID>
startsrc -s inetd

I do this remotely and don't lose connection. Anyone trying to get in in the split second before you do the startsrc -s command won't be able to get in for that brief time.

You can also do this in smit: Processes & Subsystems/Subsystems/Stop Subsystem then Start a Subsystem.

 

[bi]

One other thing:

What is the name of this system? Is that in your /etc/hosts file? As dmaris said:
At least another one is necessary for your machine:
x.x.x.x hostname-machine

 

[dlpar]

To refresh the inetd use:
refresh -s inetd
You can use it remotely.
You are not going to loose the connection

 

[Matsul]

OK thanks

Yes for my host name there are two entries

191.167.2.7 athena
191.167.2.6 athena

as its dual ip.

As such I think its more some routing protocol learning an incorrect route mainly because of the netstat output I mentioned initially.

Strangly the problem is on two of the 4 IBM machines I have. Now I flushing the roputing table on one of them and it went. On the other I renamed the host file back and forth and the prob went also . Quite strange.