Scheduled job executions broken after restart #2271

Open
shoelzle opened this Issue Jan 10, 2017 · 6 comments

Projects

None yet

3 participants

@shoelzle
shoelzle commented Jan 10, 2017 edited

Bug report

My Rundeck detail

  • Rundeck version: 2.7.0-1
  • install type: launcer
  • OS Name/version: Debian Wheezy

Expected Behavior

One-time scheduled job executions continue after rundeck server restart.

Actual Behavior

One-time scheduled job executions are still present after a rundeck server restart, however they don't continue and thus are not executed

How to reproduce Behavior

  1. Schedule job for a one-time run (button: run job later)
  2. Restart rundeck server

...

@jamieps
Contributor
jamieps commented Jan 12, 2017

@shoelzle Can you check if there are any errors in your service.log?

@willemdh
willemdh commented Jan 13, 2017 edited

Fyi, I have the same problem. It started on the update to 2.6.10.

@jamieps
Contributor
jamieps commented Jan 13, 2017

Is this scheduled jobs, as in using a fixed crontab schedule, or a one-off ad hoc scheduled job (using 'Run Job Later')?

@shoelzle

@jamieps , this only happens with one-off ad-hoc scheduled jobs. I'll clarify this in the issue description.

@shoelzle

@jamieps , I'll check the logs in a few days.

@jamieps
Contributor
jamieps commented Jan 13, 2017

Does your job have secure input options? Those cannot be rescheduled automatically at startup (currently), if so it should log a warning to that effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment