The cluster node has a 'CONNECTED_READY' status even after stopping all the TIBCO Data Virtualization services.
Article ID: KB0072738
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | All Supported Versions |
Description
When the TDV services of a node present in a cluster are stopped, there are oddities noticed at times in that node's status in Web Manager.
The status still displays as 'CONNECTED_READY' instead of being in the 'DISCONNECTED' status.
Another observation made, the services of that node cannot be started/restarted again.
The status still displays as 'CONNECTED_READY' instead of being in the 'DISCONNECTED' status.
Another observation made, the services of that node cannot be started/restarted again.
Issue/Introduction
This article will summarize on the reason for the Web manager displaying a different status for a cluster node even after stopping the services for that particular node.
Environment
Linux Operating System
Resolution
The user faces this issue because the TDV services have not been stopped cleanly and the process is either hung or still active(for unknown reasons).
To resolve this issue the TDV process needs to be killed manually. Identify the process ID specific to TDV and then issue a kill command as follows.
Syntax:
Once this command has been executed, check the particular node's status from the Cluster tab in Web Manager and it should be displaying the correct status(DISCONNECTED).
Also, starting/restarting the TDV services should work as expected now.
To resolve this issue the TDV process needs to be killed manually. Identify the process ID specific to TDV and then issue a kill command as follows.
Syntax:
kill -9 <PID>
Once this command has been executed, check the particular node's status from the Cluster tab in Web Manager and it should be displaying the correct status(DISCONNECTED).
Also, starting/restarting the TDV services should work as expected now.
Feedback
Yes
No
Powered by
