Installation InstallerDocumentation LinStartStop - getrailo/railo GitHub Wiki

Documentation Home

Table of Contents Starting and Stopping Railo in Linux Permisions On RHEL, CentOS, Fedora, etc On Ubuntu, Debian, etc Using the "service" command

In a Linux environment, Railo can be controlled by using the provided "railo_ctl" script. During a standard install, it is possible for two (2) copies of this file to be created.

One copy of the control script will always be created right in the root wherever you installed Railo (usually /opt/railo/ - so the control script would be in /opt/railo/railo_ctl by default), and if you opt to have Railo start at boot time, another will be created in your /etc/init.d/ directory, and used as an init script. Even though there are two copies of the file, there are no difference between the two. You can use whichever copy you prefer to use.

In all installations, root-level privileges are required to use the railo_ctl script. This means you have to either be logged in directly as root, su to root, or sudo to root. This is important because it usually effects how to run the railo_ctl script.

To start Railo (and Tomcat) in a RHEL-based distribution, you can run the following command (logged in as "root"):

 # /opt/railo/railo_ctl start

To Stop Railo:

 # /opt/railo/railo_ctl stop

And to Restart Railo:

 # /opt/railo/railo_ctl restart

You can also use the script to check the server's running status:

 # /opt/railo/railo_ctl status

Lastly, if for some reason Tomcat/Railo hangs, get stuck, etc, you can insta-kill it with:

 # /opt/railo/railo_ctl forcequit

Debian-based distros, like Ubuntu, you'll typically need to SUDO:

 $ sudo /opt/railo/railo_ctl restart

If you opted to have Railo start at boot time, that would have configured the init script to be added to /etc/init.d/. When a script is present there, some distributions, like CentOS, offer the "service" command:

 $ service railo_ctl restart

Documentation Home