Page tree
Skip to end of metadata
Go to start of metadata

The FusionReactor (FR) Linux Archive bundle comes with scripts to automate setting up Fusion Reactor as a daemon (allow it to be run in the background of the system). This gives the ability to configure FusionReactor to begin on server startup, and cleanly exit on server shut down. A daemon is the equivalent of a Windows Service.

There are three scripts included in the Archive :

NameOptions
framd.installNone
framd.uninstallNone
framd
start | stop | status | restart 
  • start - Starts the daemon.
  • stop - Stops the daemon.
  • status - Returns whether or not the daemon is running
  • restart - Stops the daemon and attempts to start it again.

 

You may run the framd script without running framd.install. However, this will then not include the benefits of running as a daemon and also force FusionReactor to be run as root user. It is recommended to use the installer.

Step-By-Step Guide


1) Run framd.install. This will generally need to be run by the root user. However, you can run this as a non-root user by using:

sudo ./framd.install

in which you will be prompted for your password.
 

2) You will be asked to specify the user and group that you want to run the daemon as. The user chosen may affect the performance of FusionReactor if the they do not have sufficient Read/Write permissions to the areas the FusionReactor accesses. These include:

  • Any application servers that FusionReactor is installed into through Fusion Reactor Administration Manager (FRAM).
  • The FusionReactor directory (e.g. /opt/fusionreactor/)

If you are having any issues regarding permissions, it is advised to look at : 

3) The script will begin creating the relevant symbolic links in place in your /etc/init.d and /etc/rcX.d directories or your /etc/systemd/system/ directory to allow FusionReactor to be run as a daemon on boot. The directory that the links are placed into depends on what daemon process your system uses. A file called .runuser will also be created in the FusionReactor root directory, containing the name of the user in which the system will run FusionReactor as.
 

4) FusionReactor can now be successfully run as a daemon on your system. In order to control the daemon, you need to use the command for which your Linux Distribution supports. For example, if FusionReactor installed into the init.d and rcX.d directories of your system, you should use the command

service framd start|stop|status|restart

If FusionReactor installed into the systemd directory of your system, you should use the command

systemctl start|stop framd

To find out whether you are running 'init' or 'systemd' , run the command in terminal

ps -p1 -o command

On booting your system, FusionReactor will immediately attempt to start if installation was successful.

Uninstalling

Note: Uninstalling FusionReactor

If you installed FusionReactor as a daemon, you should always use the uninstaller to cleanly remove Fusion Reactor as this gets rid of the various system files created by Fusion Reactor such as symbolic links in your system for boot-loading.

If you wish to remove FusionReactor as a daemon, you should run framd.uninstall .

Troubleshooting

If you have any issues starting FusionReactor as a service after installation, make sure that the runtime users' file permissions are sufficient. The runtime user requires full access in the FusionReactor directory and the execute access to java in your Java bin directory to work correctly.

There is also a log file called framd.log which can be found in the root directory of FusionReactor. This contains logs of the FusionReactor once it has started running to help indicate if there is any issues.

  • No labels