Omnicomm bad hosts list

If a device (the Terminal (Term.) Server/Host Name field on the Physical Connection Edit tab of the connection Row Edit dialog box) fails a getHostByName() call, Omnicomm may blocklist the device (that is, place it on its bad host list). A configuration error (for example, a spelling error) or a network failure can cause a device to fail a getHostByName() call.

The first failed attempt to access a device prevents any other connections from attempting to access it (that is, the failed attempt affects all connections configured for that device). The oasErrLog.log file will contain a log message such as, for example, "hostLookupByName(): adding "ls1pdcdev1" to the bad hosts list; error in getaddrinfo: 10050 - The network subsystem has failed."

Omnicomm does not attempt any socket connections to blocklisted hosts, as potentially blocking socket calls would adversely affect all communications.