Kbase P49926: NameServer reports different hostnames with a nsman -query versus information listed in NS log files
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/09/2004 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1x
WebSpeed 3.1x
SYMPTOM(s):
nsman -query reports the NameServer has started on primary IP/hostname (Host Progress-Primary)
NS log file reports the NameServer has started on the secondary IP/hostname (Host Progress-Secondary)
Example of Problem:
nsman -query reports:
NameServer NS1 running on Host Progress-Primary Port 5162 Timeout 30 seconds.
NS log file reports:
Starting NameServer NS1 rmi://progress-secondary:20931/NS1 Port = 5162 TimeOut = 30. (8196)
Working with dual NIC environment
NameServer, AdminServer and WS broker are all started on the intended secondary IP/hostname (Host Progress-Secondary)
WS broker and NameServer are correctly registered to correct IP/hostname (Host Progress-Secondary)
All logs report that all components have been started on the correct IP/hostname (Host Progress-Secondary)
CAUSE:
The NameServer listens on many interfaces. When working within a multi NIC environment, Progress gets the IP address from InetAddress.getLocalHost(). This function retrieves only the first defined interface. Thus, even though the NameServer listens on all interfaces, the first interface is reported when performing an nsman -query.
FIX:
The information that is reported through the nsman -query is only reporting the first interface. This does not mean that the NameServer was started on the wrong IP/hostname address.
No action is needed, all components have started successfully on the correct IP/hostname address.