Welcome, Guest Login

Rundeck Enterprise Support Center

Installing a Single Instance of Rundeck Pro Cluster On Linux

Last Updated: Feb 21, 2018 05:33AM PST

Note: these instructions are for installing a single instance "cluster" (one cluster member only) for evaluation or standalone usage. 

1.   Install Rundeck Pro



  • Rundeck PRO 2.x needs Java 8 installed on the server


RedHat or Centos distributions (rpm)

  • Install RPM with yum

wget https://bintray.com/rundeckpro/rpm/rpm -O bintray-rundeckpro-rpm.repo
sudo mv bintray-rundeckpro-rpm.repo /etc/yum.repos.d/
sudo yum install rundeckpro-cluster

  • Install RPM package

Download rpm package: http://download.rundeck.com/eval/ and run:

sudo rpm -i rundeckpro-cluster-X.X.X-GA.noarch.rpm


Debian distributions (deb)

  • Install with apt-get
Using the command line, add the following to your /etc/apt/sources.list system config file:

echo "deb https://rundeckpro.bintray.com/deb stable main" | sudo tee -a /etc/apt/sources.list

Or, add the repository URLs using the "Software Sources" admin UI:

deb https://rundeckpro.bintray.com/deb stable main

Download bintray public key:

wget -qO - https://bintray.com/user/downloadSubjectPublicKey?username=bintray | sudo apt-key add -

Finally, install rundeck;

sudo apt-get update
sudo apt-get install rundeckpro-cluster

  • Install deb package directly

Download deb package: http://download.rundeck.com/eval/ and run:

sudo dpkg -i rundeckpro-EDITION_X.X.X-GA_all.deb

2. Login to the GUI

By default, rundeck will be installed in port 4440. To access rundeck, go to the following URL: http://servername:4440.

Normally, it is necessary to modify the [servername] parameter on /etc/rundeck/rundeck-config.properties to access the GUI, for example:
Screenshot 2017-10-04 14.15.29.png
Change grails.serverURL=http://localhost:4440 with the server name or IP.
(this change needs the rundeck service to be restarted)
Screenshot 2017-10-04 14.21.44.png
The default username and password is “admin”

3. Start-Stop instances


To start or stop the instance you can use the following command:
 sudo service rundeckd {start|stop|restart|status}

4. Install License File

  • Go to the GUI and click on the “No License Key File is installed” button
Screenshot 2017-10-04 14.22.53.png
  • Then click on “Upload License File”

Screenshot 2017-10-03 14.29.11.png
  • Then select the license file (.key file)  and press “Update License File”
Screenshot 2017-10-03 14.31.33.png
  • Finally, it is necessary to change the “Passive Mode”  to “Active”
Screenshot 2017-10-03 14.31.44.png

5. Folder Structure

Rundeck folder will be owned by rundeck user. Any file that you add/edit needs to be owned by that user (for example in case that you add acls files)
  • /etc/rundeck/ => Configuration file layout
├── admin.aclpolicy => Administrator access control policy defined with a [aclpolicy] document
├── apitoken.aclpolicy => Default API ACL policies
├── cli-log4j.properties => This file defines the logging configuration for the Commandline tools.
├── framework.properties => Configuration file used by shell tools and core Rundeck services
├── jaas-loginmodule.conf => Default authentication module.
├── log4j.properties => Rundeck uses log4j as its application logging facility,
├── profile => Shell environment variables used by the shell tools
├── project.properties =>Rundeck project configuration file when using Filsystem based project defintions:
├── realm.properties => Property file user directory when PropertyFileLoginModule is used
├── rundeck-config.properties => This is the primary Rundeck webapp configuration file. Defines default loglevel, datasource configuration, and GUI customization.
└── ssl => To enable SSL access to rundeck
    └── ssl.properties
├── rundeck.access.log => access to rundeck
├── rundeck.api.log => Api calls
├── rundeck.audit.log => Authorization messages pertaining to aclpolicy
├── rundeck.executions.log => Logs of all executions
├── rundeck.jobs.log => Log of all job definition changes
├── rundeck.log => General Rundeck application messages
├── rundeck.options.log => Logs remote HTTP requests for Options JSON data
├── rundeck.storage.log
└── service.log => Standard input and output generated during runtime
  • /var/rundeck/projects => Projects data (eg: resource files, project properties, etc)
  • /var/lib/rundeck => Rundeck install directory
├── work
├── var
├── logs => Executions Logs folder
├── libext => Plugin folder
├── exp
├── data
├── cli => rd-acl client (to manage ACL validation)
├── bootstrap
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found