[frs-293] How to correct a FusionReactor environment on Solaris after upgrading from 4.0.6 or 4.0.7


This will not be an issue for you if you chose for FusionReactor Administration Manager (FRAM) to run as root user during the setup, if you did then you do not have to continue reading this technote.

There was a bug in the FusionReactor 4.0.6 and 4.0.7 installer for Solaris SPARC which resulted in the FusionReactor Administration Manager (FRAM) always running as root user. This bug was fixed in FusionReactor 4.0.8, FusionReactor Administration Manager (FRAM) is now able to be run by the user chosen during the setup.

The problem was that in 4.0.6 and 4.0.7 FusionReactor Administration Manager would place the fusionreactor.jar file in your server's shared lib directory as root which meant no other user except root could access or overwrite it. When trying to update your 4.0.6 or 4.0.7 instances to 4.0.8 (or higher) a lot of the time the update would fail. This is because FusionReactor Administration Manager now runs as the user chosen during the setup, most of the time this user is not root which causes the update to fail as it can't overwrite the fusionreactor.jar file that was placed there by FusionReactor Administration Manager when it was running as root in version 4.0.6 or 4.0.7.


After updating FusionReactor from 4.0.6 or 4.0.7 to a higher version you attempt to update your 4.0.6 or 4.0.7 instances, the following is displayed.

You then follow the advice in the dialog box and view the log by navigating to the table of contents and clicking on FusionReactor and then Log. You will then be presented with the contents of the reactor.log file, scroll down and look for a stack trace that contains something similar to the text below.

2012-05-14 16:15:07.214 WARNING com.intergral.fusionreactor.install.InstanceManagerPermissionsException: 
Could not copy fusionreactor.jar to /opt/coldfusion9/runtime/servers/coldfusion/SERVER-INF/lib/fusionreactor.jar (Permission denied). 

The messages explains that the fusionreactor.jar file can not be copied over to the shared lib folder of the server. This is the symptom.


You will need to apply this procedure to every FusionReactor 4.0.6 or 4.0.7 instance that you want to update.

1) Open a terminal and navigate to the directory that you observed in the Symptoms section of this technote, for this scenario is is /opt/coldfusion9/runtime/servers/coldfusion/SERVER-INF/lib. This directory contains the fusionreactor.jar that is owned by root user.
2) We are going to change the user and group of the fusionreactor.jar to the user and group that was chosen during the FusionReactor setup. If you can not remember the user and group you choose during the setup type the following into the terminal and hit enter, "ls -la fusionreactor_home" where "fusionreactor_home" is the directory in which FusionReactor is installed into. In Solaris the default location is /opt/fusionreactor.
After you type this in and hit enter all the files in the FusionReactor directory along with the user and group that owns them will be output to the console, every file will be owned by the same user and group, this is what you installed FusionReactor as. To change the user and group of the fusionreactor.jar file type in "sudo chown user:group fusionreactor.jar" where user is the user FusionReactor was installed as and group is the group that it was installed as.
3) Now return to the Instance Manager and update the 4.0.6 and 4.0.7 instance in which you applied this technote to.

Issue Details

Type: Technote
Issue Number: FRS-293
Components: Installer
Resolution: Fixed
Last Updated: 22/May/12 11:24 AM
Affects Version:
Fixed Version: 4.5.0
Platform: Solaris
Related Issues:

Comments are closed.