Error when running Execution History Clean

[nos...@gmail.com]

Rundeck 5.4.0 updated many times over the years.  Running as a container on Ubuntu 20.04.3 LTS.

More frequently running jobs are causing inodes to fill up, so I enabled Execution History Clean for our projects.  Looked like things were working at first since the # of executions decreased, but I noticed they stopped decreasing and the rundeck logs shows:

ERROR quartzjobs.ExecutionsCleanUp - Failed to delete execution 21824204
java.lang.NullPointerException: Cannot get property 'dateCompleted' on null object

I am not sure how many execution id's it is complaining about, the log seams to go on forever.  I queried for a handful of these execution id's in the executions table and they are not in there.  Example: SELECT * FROM execution WHERE id =  21824204;

I am not sure what to do from here, it is getting an old execution list from somewhere, but the entry for an execution is null?  I checked on github issues to no avail.  There are old documents on manually cleaning up old executions, but I would guess they wouldn't work with a newer rundeck.  I appreciate any help on this.

[rac...@rundeck.com]

Hi,

Are execution logs stored on s3 bucket like this? (it seems the same issue).

Regarding this:

There are old documents on manually cleaning up old executions, but I would guess they wouldn’t work with a newer rundeck. I appreciate any help on this.

Which documents have you checked?

Regards.

​

[nos...@gmail.com]

Thank you for responding.  Execution logs are stored on disk, seams like the execution records in the db and logs on disk somehow got out of sync?  It is possible, we store other log types on this VM as well.  We could try making dummy execution logs so that the cleanup routine will run.
I was referencing some solutions in an old thread on purging old logs: https://groups.google.com/g/rundeck-discuss/c/rI9FN9jz_is

[rac...@rundeck.com]

Hi,

Also, consider this approach.  It may be slow if you have a large number of executions (you will most likely need to set certain flags such as this one, more info here), but it is the safer option.

Of course, the main advice is to test it on a non-prod environment first.

Greetings.