Rundeck is cross-platform open source software that helps you automate ad-hoc and routine procedures in data center or cloud environments. Rundeck allows you to run tasks on any number of nodes from a web-based or command-line interface. Rundeck also includes other features that make it easy to scale up your scripting efforts including: access control, workflow building, scheduling, logging, and integration with external sources for node and option data.

Rundeck software is free and completely open source. It’s licensed under the terms of the Apache 2.0. Download it. Try it. Use it. If you find value in it and would like to actively participate in the project, introduce yourself on the mailing list or the IRC channel.

Bugs are tracked on Github Issues.

Post messages to google groups: http://groups.google.com/group/rundeck-discuss

Yes, Rundeck works on Linux flavors and windows. This assumes the commands you execute can run on the targeted host.

Please check docs for latest suppoted Operating Systems: https://docs.rundeck.com/docs/administration/install/system-requirements.html

Yes, Rundeck server can be configured to use SSL. Consult the Security section in the manual. https://docs.rundeck.com/docs/administration/security/ssl.html

Yes, Rundeck can be configured to authenticate to an LDAP directory service. See https://docs.rundeck.com/docs/administration/security/authentication.html#ldap

The open source list of plugins is kept here: https://github.com/rundeck-plugins

You can use multiple JAAS loginmodule configurations within a single named JAAS configuration. See Multiple Authentication Modules

You can add configuration to the Rundeck-config.properties file, using the config settings shown under the Grails Mail Plugin "Configuration" section.

Since the default rundeck config file is Java ".properties" format, you will either have to flatten the config hierarchy shown in that document .e.g "grails.mail.host=hostname", or convert your Rundeck config file to Groovy format, and specify the right config file location at Rundeck startup.

The default for RPM/DEB is /tmp/rundeck, if it doesn’t exist or does not have permissions, you may encounter errors.

If you are using the launcher, you will need to add -Djava.io.tmpdir=/path/to/dir to your Java system properties when you start the server.

If you installed with the RPM package, modify the /etc/sysconfig/rundeckd file, and if you installed with the DEB package, modify the /etc/default/rundeckd file and add:

export RUNDECK_TEMPDIR=/tmp/rundeck

You need to set the grails.serverURL property in your rundeck-config.properties file to specify a fully qualified domain name for your server.

Rundeck uses that URL as the base URL for redirects, so you need to change it from localhost after installation. (Related issue #1049)

For Rundeck 3:

See the System Configuration

Use config property server.session.timeout.

For Rundeck 2:

1. edit /var/lib/rundeck/exp/webapp/WEB-INF/web.xml (change path depending on you Rundeck install)

2. find <session-config>

3. raise the timeout:

   <session-config>
           <session-timeout>43200</session-timeout>
   </session-config>

If you are executing commands to remote nodes that use bash as the login shell, you might not be getting the shell environment you see when logging in interactively. This is because remote commands create a non-interactive shell session.

To illustrate add the following line to your .bash_profile and .bashrc files for a remote user to test.

Next, login as a remote user:

Notice the .bash_profile is read. Now log out.

This time execute a remote command rather than logging in:

This time .bashrc file is read.

So to summarize:

• For interactive ssh, it will read .bash_profile

• For non-interactive ssh, will read .bashrc

Rundeck remote command steps result in a non-interactive shell.

You can check this useful link also, Invocation section: https://linux.die.net/man/1/bash