Engines log in but never become available
Article ID: KB0085249
Updated On:
| Products | Versions |
|---|---|
| TIBCO DataSynapse GridServer | - |
| Not Applicable | - |
Description
Resolution:
When Engines are listed in the Engine Admin page as "Logged In" but never become available, the issue is often that the Director is reachable from the Engine, but the Broker is not reachable from the Engine. This usually happens when the Director and Broker are on separate systems. Some network configurations that can cause this issue are:
* A Director installed with fully qualified domain names but the Broker has been configured with its short name.
* Firewall software, such as Linux iptables, is installed on the Broker.
* NAT is being used between the Broker and the Engines and either this is LiveCluster 3.1.1 or earlier or the NAT plugin has been incorrecly installed.
When Engines are listed in the Engine Admin page as "Logged In" but never become available, the issue is often that the Director is reachable from the Engine, but the Broker is not reachable from the Engine. This usually happens when the Director and Broker are on separate systems. Some network configurations that can cause this issue are:
* A Director installed with fully qualified domain names but the Broker has been configured with its short name.
* Firewall software, such as Linux iptables, is installed on the Broker.
* NAT is being used between the Broker and the Engines and either this is LiveCluster 3.1.1 or earlier or the NAT plugin has been incorrecly installed.
Issue/Introduction
Engines log in but never become available
Feedback
Yes
No
Powered by
