The technote will guide readers through the most common issues related to the Instance Manager and a possible fix for most of them.
By common issues we mean the following;
Usually, the most common reasons are insufficient permissions or a Firewall policy that might be blocking traffic on the listening port. Read the sections below for more information.
You need to make sure that FRAM (FusionReactor Administration Manager) has enough permissions in order to access files. In case FRAM is running as a nobody user, it will not be able to execute root or user commands.
In order to identify if this is the case, the installation of an application server might fail or the installation process might not be successful. Below, there are a couple of error messages that might help you identify this issue.
A possible solution for this issue might be to install FRAM as the same user as the application server or add the user into a group and give that group access to the application server files.
More information about the secured environments can be found in the link below.
Another possible indicator about Instance Manager issues is a Firewall policy or configuration that might be blocking traffic on the listening port the FusionReactor instance has been configured.
A possible solution for this issue is to double check that an inbound policy exists in your Firewall and allows traffic on the configured port.
Additionally, make sure that the configured port is open and ready to accept traffic. For a Linux OS this can be done by typing "netstat -lntu" and for a Windows OS this can be done by typing "netstat -aon"
Another possible explanation why you are having issues with the Instance Manager might be an anti-virus system that is running in your environment.
Please double check that the anti-virus software is not blocking traffic on the configured port.
If you are using a Windows Server and you have already configured FusionReactor with IIS, please make sure that the IIS configuration is not blocking the traffic on the configured port.
If you have configured the FusionReactor Instance to start/stop manually, however, after the configuration you are not able to access the FusionReactor Instance via the browser, please check the following.
If you cannot access the FusionReactor Instance via the browser, is worth checking that the port you have used for the instance is not used by another application in your environment.
For a Linux OS this can be done by typing "netstat -lntu" and for a Windows OS this can be done by typing "netstat -aon"
If you are getting a browser error and similar to the following; "net::ERR_NAME_NOT_RESOLVED", then you need to make sure that a DNS server in your environment is able to resolve the name of a FusionReactor Instance.
If you have further questions or issues, please feel free to contact the FusionReactor Support Team on firstname.lastname@example.org
|Components:||FRAM, Instance Manager|
|Last Updated:||Today 3:57 PM|
Comments are closed.