Install Rundeck
Run the following commands as root:
· rpm -Uvh http://repo.rundeck.org/latest.rpm
· yum install rundeck java
· service rundeckd start
· service rundeckd status (make sure it’s started)
· vi /etc/rundeck/framework.properties
Modify the following properties to have the IP Address of this server:
framework.server.name
framework.server.hostname
framework.server.url
· vi /etc/rundeck/rundeck-config.properties
Modify the following property to have the IP Address of this server:
grails.serverURL
· vi /etc/rundeck/realm.properties
Modify the following property to change the default admin password:
admin: <new password>…
Hi Eric,
Check the service log: tail -f /var/log/rundeck/service.log
at the moment of starting the Rundeck service. In that way you can obtain more clues.
Take a look at this guide (Community tab).
After installation, change the grails.serverURL=http://localhost:4440
to grails.serverURL=http://server_ip_or_hostname:4440
in the rundeck-config.properties
file (at /etc/rundeck
path).
And of course, make sure to install Java 11 to run the Rundeck service properly.
Greetings.
--
You received this message because you are subscribed to a topic in the Google Groups "rundeck-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rundeck-discuss/smX-t3cV66w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/77779ce8-a43f-4d6f-9fe0-ad57bb9af650n%40googlegroups.com.
#!/bin/bash
#Backup rundeck
#Set variables
DAY_OF_MONTH=$(date +"%d")
BACKUP_JOBS=${DAY_OF_MONTH}_JOBS.xml
BACKUP_DATA=${DAY_OF_MONTH}_DATA.tar.gz
BACKUP_LOG=${DAY_OF_MONTH}_LOG.tar.gz
#Set env vars that are needed by rd
export RD_URL=http://1.2.3.4:4440
export RD_USER=admin
export RD_PASSWORD=<GetPasswordFromPasswordSafe>
# First get into the proper directory
cd /backup/rundeck
# If this day of month's backup already exists, delete it
if [ -f "${DAY_OF_MONTH}*" ]
then
rm -f ${DAY_OF_MONTH}*
fi
#First backup jobs
rd jobs list -f /backup/rundeck/$BACKUP_JOBS -p RossNapOISOperations
#Stop rundeck server
service rundeckd stop
#Wait for it to get fully stopped before backing up data
sleep 30
#Backup the data
tar cvfz /backup/rundeck/$BACKUP_DATA /var/lib/rundeck/data
#Backup the logs
tar cvfz /backup/rundeck/$BACKUP_LOG /var/lib/rundeck/logs
#Start rundeck back up
service rundeckd start
exit 0
Hi,
Great! You can simplify that process by exporting the whole project in your script (instead of creating individual jobs backups):
rd projects archives export help
for more info. This includes the stored (All ACLs saved in the database) ACLs, if your old instance contains filesystem ACL you can back up the .aclpolicy
files located in the /etc/rundeck
path.rd projects create help
for more info.rd projects archives import help
.Regarding the AD Config. That configuration needs a file in the /etc/rundeck
path (jaas-ad.conf
or similar), the same for the file that calls that conf. If your Instance is well configured you also need the /etc/sysconfig/rundeckd
file, take a look at this.
Of course, the main advice is to test that process before in a non-prod environment to test all steps.
Hope it helps!
No worries Eric :-)
If you open the rundeck-config.properties
file with any text editor, you will see a similar config block as follow:
# Encryption for key storage
rundeck.storage.provider.1.type=db
rundeck.storage.provider.1.path=keys
rundeck.storage.converter.1.type=jasypt-encryption
rundeck.storage.converter.1.path=keys
rundeck.storage.converter.1.config.encryptorType=custom
rundeck.storage.converter.1.config.password=my_password
rundeck.storage.converter.1.config.algorithm=PBEWITHSHA256AND128BITAES-CBC-BC
rundeck.storage.converter.1.config.provider=BC
That means that the keys (private keys and passwords stored on the Rundeck’s Key Storage) are crypted in the backend using my_password
as password.
If the “old” instance was installed by default, probably the password line is configured with a “random” string, and that is the default out of the box Rundeck behavior.
So, probably you’re in the second scenario of this. If you’re using a fresh database, you need to recreate them manually.
Hope it helps!
Hi,
Which java version are you using? you can see it with the following command: java -version
.
Also, check the requeriments here.
Regards.
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/ed0945bd-7352-47ca-a475-e1edbde83d9bn%40googlegroups.com.