A Plesk node is up and running, but it is shown with the status "Not Available" in the Odin Business Automation Standard (OBAS) Panel (
Top > Service Director > Plesk Manager > Nodes).
Various issues can cause the above problem, including:
- Network connectivity issues
- An expired Plesk license
- The Plesk admin’s password was changed directly from the Plesk Control Panel
- The IP Address of the OBAS node has been changed
- A broken API-RPC package on Plesk
- Firewall rules that prevent OBAS from connecting to the Plesk node
Log into the Plesk Control Panel and check that a valid license is installed.
Make sure that the IP address of the Plesk server is reachable from the OBAS server and that the connection to port 8443 is not blocked on either the Plesk server or the OBAS server.
To check the OBAS connection, log in on the OBAS server via SSH. Check the connection of the Plesk server (IP 126.96.36.199 ) on port 8443 with the telnet command:
# telnet 188.8.131.52 8443 Trying 184.108.40.206... Connected to 220.127.116.11. Escape character is '^]'.
Top > Service Director > Plesk Manager > Nodes > %Plesk node% > Edit > Plesk administrator password
This will re-initiate secure keys for further communication. NOTE: The connection may fail because of the Plesk Security Policy.
Run the periodic task "
Update Plesk nodes stats info" from the OBAS Provider Control Panel to update the Plesk node's status:
Top > Configuration Director > Logging and Errors > Action Log > Task Queue tab > Update Plesk nodes stats info > Run now
Verify DEBUG OBAS log for update records. NOTE: The task may fail because of error "PleskAPIInvalidSecretKeyException : Invalid secret key usage. Please check logs for details."
By design, OBAS communicates with Plesk using the Plesk API. Check the consistency of the API-RPC-related packages on the Plesk server:
Validate the package psa-api-rpc:
# rpm -V psa-api-rpc
The above command will give you a list of missing or modified files, if there are any. If the output is not empty, it most likely means that the package needs to be reinstalled.
The valid package can be obtained from http://autoinstall.plesk.com (according to your Plesk version, OS, and architecture) and reinstalled. The example given below illustrates the installation of the psa-api-rpc package of Plesk 11.5.30 installed on a server with CentOS 6 x64.
# wget http://autoinstall.plesk.com/PSA_11.5.30/dist-rpm-CentOS-6-x86_64/contrib/psa-api-rpc-10.0.0-1.noarch.rpm # rpm -Uvh --force psa-api-rpc-10.0.0-1.noarch.rpm
Once the package is reinstalled, run the task "
Update Plesk nodes stats info" in OBAS again, following Step 4 (above).
There is no simple way to reinstall a single package on Windows. The files in question are located in the
Check that the files in this directory, specifically Agent.php, were not changed after the installation/upgrade, and that they have the correct permissions:
psaadm: Read, Read&execute
- Temporarily disable the firewall on the Plesk node and recheck the node's availability. Make sure that the firewall rules do not disappear after restarting iptables. If it turns out that firewall is the key, please review the firewall rules and modify them so that all the required ports are open.