When trying to configure an OpenSpirit satellite installation there must be a communication path between the machine the OpenSpirit master installation is running on, and the machine you are installing the satellite installation on. If a communication path between these two machines does not exist, you may get the error below which often is the result of having a firewall between the two machines.
Warning: Unable to connect to an OpenSpirit installation using <port@hostID>Keep in mind that the firewall is not always on the PC you are installing the satellite installation on, it could also be on the machine the master installation is running on (especially if it is a PC), or it could also be a corporate firewall. In all cases, chances are you will need to consult with your System/Network administrator in order to confirm.
If you are required to have a firewall turned on the PC, then you should launch a Windows command prompt with Administrator’s privilege and execute the
%OSP_HOME%\bin\etc\OSPExemptions.bat script to add the OpenSpirit executables to the Windows firewall exemption list. You will need to consult with other application vendors to find out how to exempt their application from the firewall.
Another reason for these errors could be that the OpenSpirit shared services is in fact not runningBelow is how you could start troubleshooting these types of issues:
- The first thing to do, and easiest is to verify that the shared services IS in fact running. To do this, just go to $OSP_HOME/bin directory then issue the command ./runOSServices.sh status. If your master installation is on a Windows machine, then the command would be ./runOSServices.bat status from a command prompt. The message you get back should indicate if both the Shared Services, and Notifications Services are running:
-bash-4.1$ pwd
/prod/spirit/v430_GAcjl_rh6-r5000/v4.3/bin
-bash-4.1$ ./runOSServices.sh status
Running on: Linux RH6-R5000.openspirit.com 2.6.32-573.3.1.el6.x86_64 #1 SMP Mon Aug 10 09:44:54 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
Checking local host against RH6-R5000.openspirit.com at: Mon Oct 28 11:49:28 CDT 2019
Checking status of OpenSpirit v4.3.0.158 HF02 (OSP port=15437) services...
The Notification Service does not appear to be running
Shared Server is unreachable.
- In the example above, neither the shared services or notifications services are running, so to resolve this particular issue, all you may have to do is start the shared services with the command below:
-bash-4.1$ ./runOSServices.sh start
Running on: Linux RH6-R5000.openspirit.com 2.6.32-573.3.1.el6.x86_64 #1 SMP Mon Aug 10 09:44:54 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
Checking local host against RH6-R5000.openspirit.com at: Mon Oct 28 11:53:46 CDT 2019
Starting OpenSpirit v4.3.0.158 HF02 (OSP port=15437) services...
Starting Notification service...
### - Waiting for Notification Service (pid 9120) to come up.
Notification Service running as pid 9120
Starting Shared Services...
### - Waiting for SharedServices server to come up...
SharedServices running as pid 9153
OpenSpirit services are now running... - After starting the shared services, try configuring your satellite again, chances are you will now be able to configure your satellite.
- One thing to note, make sure that you are using the host and port you get back from the command above to configure your satellite installation: example above host=RH6-R5000.openspirit.com, and port = 15437
Still have problems?If after starting the shared services, you are still unable to configure your satellite installation, and you are getting the same error message, then chances are that the issue is firewall or DNS related. Do the following:
- Launch a Windows command prompt then issue the command below to see if the PC can resolve the name of the machine the shared services are running on (in the example, the machine the shared services is running on is RH6-R5000.openspirit.com):
nslookup RH6-R5000.openspirit.com
nslookup RH6-R5000
(2) Your PC should be able to resolve both long and short name of the machine the shared services is running on. If your PC cannot resolve the host name to its IP address, then a short term fix your System Administrator could implement would be to edit your
C:\Windows\System32\drivers\etc\hosts and add the name of the machine the shared services is running on and its IP address.
It is very important that you consult with your System Administrator before modifying this file.