Kbase P90571: Adminserver fails to start with Could not bind name in ADS0.exp file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/10/2005 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
Progress 9.x
SYMPTOM(s):
Adminserver fails to start
Exception in ADS0.exp
Chimera to object com.progress.chimera.adminserver.NonNTAdminServer[RemoteStub [ref: [endpoint:[ipaddress:port](local),objID:[0]]]]
Message (throw): RegistryManager: PrimaryRegistryManager - Could not bind name
Message (excp): Connection refused to host: hostname; nested exception is: java.net.ConnectException: Connection refused
Stack Trace:java.rmi.ConnectException: Connection refused to host: hostname; nested exception is: java.net.ConnectException: Connection refused
Second exception in ADS0.exp file
Message (throw): Failed to register admin server.
Message (excp): Bind of "Chimera" failed
Stack Trace:java.rmi.RemoteException: Bind of "Chimera" failed
Ping of hostname fails
CAUSE:
Valid IP address is not assigned in /etc/hosts
FIX:
Assign valid IP to a hostname by editing "/etc/hosts"
Format of /etc/hosts file:
IP-address official-host-name nicknames
Excerpt from manpage on hosts:
Items are separated by SPACES and/or TAB characters. The first item on a line is the host's IP address. The second entry is the host's official name.
Subsequent entries on the same line are alternative names for the same machine, or "nicknames." Nicknames are optional.