Kbase P149322: The (5644) message is showing an address of 0.0.0.0 when starting a database instead of the real IP
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/12/2010 |
|
Status: Verified
SYMPTOM(s):
The (5644) message is showing an address of 0.0.0.0 when starting a database instead of the real IP address.
Started for <service-name> using <network-type>, pid <pid>. (5644)
Started for 8898 using TCP IPV4 address 0.0.0.0, pid 26195. (5644)
FACT(s) (Environment):
If database was started with -H localhost the address in the message (5644) is set to 127.0.0.1
All Supported Operating Systems
OpenEdge 10.1C
OpenEdge 10.2x
OpenEdge Category: Configuration
OpenEdge Category: Database
CAUSE:
This is expected behavior.
FIX:
This answer applies to 10.1C and higher.
When a broker is started for IPV4, the hostname specified is ignored (unless its localhost), which forces the broker to monitor the default TCP/IP address 0.0.0.0 or 127.0.0.1 for localhost. This changed with the introduction of IPV6. When a broker is started for IPV6, the hostname, which can be a hostname or an IP address, is NOT ignored. The broker will monitor the IP address supplied via -H and all servers started by the broker will monitor the same exact IP address.
Sample 5644 messages based on how the broker is started:
IP
Version -H 5644 message
=== ======== =====================
IPv4 thishost Started for #### using TCP IPV4 address 0.0.0.0, pid ####
IPv4 localhost Started for #### using TCP IPV4 address 127.0.0.1, pid ####
IPv4 not specified Started for #### using TCP IPV4 address 0.0.0.0, pid ####
IPv6 thishostIPV4 Started for #### using TCP IPV6 address 192.168.1.23, pid ####
IPv6 not specified Started for #### using TCP IPV6 address ::, pid ####
IPv6 thishostIPV6 Started for #### using TCP IPV6 address fd00:19d:8012:12::54, pid ####
IPv6 localhost Started for #### using TCP IPV6 address ::1, pid ####