Rundeck Community

Hi,This is a WAR installation on FreeBSD, I added :# Allow donwload of public keysrundeck.gui.keystorage.downloadenabled=truerundeck.feature.publicKeysDownload.enabled=trueto both framework.properties and rundeck-config.properties, which I has to create (it doesn’t exist in FreeBSD) with no success.I also added this to preferences.properties Still doesn’t workRegards,Xavier

Hello,I introduced some times ago a workflow plugin, allowing to create dependency links between jobs that can subsist over the 24h duration of the workflow, which is defined with a daily basis.This can lead, for example, with a job failing for any reason, and the jobs linked to it waiting patiently until the error is fixed, and relaunched. If needed, waiting for the whole night.Since, I’ve worked on tackling the main problem due to linking dozen of jobs together : a visual representation of the jobs and the links between them, through a new UI plugin.Preferably, with an interactive output and able to be updated at will.I’ve reached a satisfactory level with it, where while the desired goal is reached, the UI plugin became more than useful even for people not using the other dependencies modules.To the point it is becoming a companion of the main UI.The

We recently upgraded to Rundeck 5.20 and set “rundeck.feature.nextUiMode.enabled = true”.  While the projects’ job lists load quicker (especially those with numerous cascading folders for job organization), the top of the screen shows duplicate search bars now.

Hello,Some of our users noticed a minor issue with "Job reference" step. There step label value is ignored. When a step label is added to a  "Job reference" step, the job can edition can be normally validated without any message error but the label value just disappears suddenly. It doesn't even appear after saving the stop (before saving the workflow)This happens in both Rundeck Pro/Enterprise and Rundeck Community…Is this a known bug?

Hello,When you add a "Job reference" step to a job, and choose “By name” to manually enter referenced the job’s group/name (rather then using “Choose a job” button and selecting a job interactively), is there supposed to be an autocomplete in jobs names/groups/names ? In both Rundeck Community and Pager Duty

We have enabled the execution history cleanup in Rundeck; however, the executions are not getting deleted as expected.As per the Rundeck documentation, it is mentioned that the cleanup feature needs to be enabled and properly configured. Could you please confirm:Is enabling and configuring the execution cleanup sufficient for automatic deletion? Or do we need to create a separate job to handle execution cleanup?We would like your guidance on the correct approach to ensure execution history is cleaned up as expected.And rundeck version is 3.3.11

Hello,Is there a way to reference a job from another WITHOUT the referenced job’s project name ?Some of our users use the SCM plugin to push job definition to a GitLab instance and share the referenced same jobs between two Rundeck instances used for two different purposes. Lets call them Instance A and Instance B.Instance A has project_X containing a referenced job_1, from job_2. Both jobs definitions are pushed to GitLab instance and cloned to project_Y on Instance BThe problem is, while the UUID and jobs name are the same on both Instance A and Instance B because both jobs do the same EXACT thing as you would except (no modification on actual jobs, they different only in terms of which nodes they’re scheduled/executed on), projects names on tho other hand reflect the purpose/environment (testing, production, level-

Hi,The table ‘stored_events’ grow exponentially, which each login of an user. Is it safe to purge this table ?Regards,Xavier

Hello,Our users reported many of their jobs fail to run when scheduled with the following error… com.dtolabs.rundeck.core.NodesetEmptyException: No matched nodes: NodeSet{includes={hostname=node_fqdn.tld, dominant=false, }} at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.validateNodeSet(BaseWorkflowExecutor.java:880) at com.dtolabs.rundeck.core.execution.workflow.NodeFirstWorkflowExecutor.executeWorkflowImpl(NodeFirstWorkflowExecutor.java:92) at com.dtolabs.rundeck.core.execution.workflow.BaseWorkflowExecutor.executeWorkflow(BaseWorkflowExecutor.java:220) at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.runWorkflow(WorkflowExecutionServiceThread.java:95) at com.dtolabs.rundeck.core.logging.LoggingManagerImpl$MyPluginLoggingManager.runWith(LoggingManagerImpl.java:146) at com.dtolabs.rundeck.core.execution.WorkflowExecutionServiceThread.run(WorkflowExecuti

Hi all,On the previous forum, I posted:Hi All, Is there an upgrade available yet for the following vulnerability in the rundeck log4j library? Plugin Name: Apache Log4j 2.0-beta9 < 2.25.3 MitMPlugin ID: 282519Plugin Output:  Path              : /var/lib/rundeck/bootstrap/rundeck-5.12.0-20250512.war  Installed version : 2.17.2  Fixed version     : 2.25.3 I'm running rundeck 5.12.0. Thanks,Eric Racuna responded: Hi Eric, The engineering team is aware of that CVE, thanks for your feedback! Stay tuned to next releases. Regards! I checked in both 5.19.0 and 5.20.0 but it’s still not there.  Does anyone know when this is coming? jar tvf rundeck-5.20.0-20260402.war | grep log4j 24248 Mon May 12 16:40:32 CDT 2025 WEB-INF/lib/log4j-s

Hi,Has the database structure changed between 5.19 and 5.20 ? We experience a regressions issue and want to try to rollback to 5.19Xavier

Hello.I noticed there is a weird difference between the two timestamps shown in Rundeck 5.19 web interface.I’m referring tot he HH.mm:ss timestamp shown in the left sidebar, which I assume to be the server’s timestamp in local timezone and the ISO8601 timestamp shown in tooltip/.rdlog file. The problem is they look inconsistent so I was wondering how each of these timestamps is determined The timestamp form tooltip/.rdlog file has a Zulu suffix which suggest UTC but there is a huge inconsistencyThe server is located in France (UTC + 2), locale timezone is set correctly in the OS, so is the UTC clock. NTP synchronization is active. Therefore on Rundeck server, both local timezone and UTC are set correctly.Rundeck JVM is executed with the correct timezone parameter “-Duser.timezone=Europe/Paris”. But the problem is there is much more than 2 hours differences between the left sidebar timestamp and the ISO8601 tooltip timestamps.

Hello.While looking at one of our users jobs, I noticed Rundeck Community 5.19.0 interface doesn’t show all the logs in node view. Here’s an example in screenshot Ansible playbook executed by a Rundeck job’s step from a distant node.Rundeck “Nodes” view is broken, with empty space instead of logsSometimes more logs is displayed (a few seconds more) but never the whole logs. The job actually ends a while after that.Note that the same issue as the missing “whale of a log” link for huge log files. This happens with very small log execution files. The corresponding .rdlog file is only 337 kB and both the .rdlog file and “Log output” view show all the logs but “Log output” view doesn’t lose the nodes  context (what step has been executed in which notes) and users don’t h

Hello, is there a way to "Kill tracked processes after execution" the PID child when i kill a job that running for a specific command(Not a job)? 

Calling out all Rundeck by PagerDuty open-source experts out there!We’re gearing up for next Rundeck by PagerDuty meetups (in-person & virtual), and we want YOU to be one of our rockstar speakers! If you’ve got some cool insights, epic stories, or game-changing tips about your experience with Rundeck by PagerDuty open-source, we’d love to hear from you. This is your chance to shine, share your knowledge, and inspire your fellow community members. Plus, it’s a great way to network and connect with like-minded folks in the industry!If you’re interested (and we hope you are!), visit https://github.com/rundeck/rundeck-meetups, reach out to us at community-team@pagerduty.com, or leave a comment below and let us know your region, topic idea and avai