Closed isuftin closed 7 years ago
Also I should mention that the EC2 instance has an IAM role attached that allows writing to the S3 bucket, so credentials aren't configured at this level.
the stacktrace traces to this line: at rundeck.services.ProjectService.getExecutionXmlFileForExecution(ProjectService.groovy:147)
Which is using Java's File.createTempFile
which will fail if the Temp directory that is defined does not exist or is not writable.
Make sure your JVM properties have a -Djava.io.tmpdir
value pointing at a valid temp dir. For Debian/RPM installs, you can define the RUNDECK_TEMPDIR
in /etc/default/rundeckd
or /etc/sysconfig/rundeckd
respectively.
export RUNDECK_TEMPDIR=/var/tmp/rundeck
If you are using the Launcher, you will have to add -Djava.io.tmpdir=/tmp/dir
to your commandline
@gschueler Adding the -Djava.io.tmpdir
option fixes this issue. I wonder if this is something that should be in the documentation?
@isuftin yes, should be in the docs. Also, perhaps Rundeck should test the value at startup and echo a warning if the temp dir is not valid/writeable.
Plugin version: 1.0.3 Rundeck version: 2.9.3-1 Running on AWS in us-west-2 on CentOS 7
The config:
The trace: