Replies: 8 comments
-
The 6-part cron schedules don't work like they do in ofelia, try using 5 parts |
Beta Was this translation helpful? Give feedback.
-
yeah, that only fixed half of the problem, the exec jobs now work fine, but run jobs are still not seen upon update. I have containers that need to be started up every so often. |
Beta Was this translation helpful? Give feedback.
-
It would be a good idea to fix the README - this same error just cost me a bunch of time as well. I even checked the syntax against that given on the front page of this project, which explicitly states "Go syntax", with 6 entries! I'm pretty sure I changed it to 6 at some point to make it work, and now I have to change it back... not sure when this change happened. |
Beta Was this translation helpful? Give feedback.
-
I found out when I made the change - end of december. My own commit message was "Update Cron definitions to fit Go version used in Chadburn". The day before I switched from Ofelia to Chadburn. -> At the time, Go syntax for cron was required. Since then, it has apparently changed and my schedules stopped working. I wasn't paying attention, so I didn't notice it happening. |
Beta Was this translation helpful? Give feedback.
-
Hi @miggland. Thanks for letting me know, although, I don't seem to be getting alerts for every issue raised here. I do plan to fully rewrite Chadburn or at minimum refactor the project to address a large number of issues people are having. When I decided to hard fork this project, I didn't realize just how many issues people were having. I plan to get started fairly soon, after I can get some of my paid projects out of the way. |
Beta Was this translation helpful? Give feedback.
-
Hi @maietta Until then, maybe just remove the wrong info in the Readme? ` Note: the format starts with seconds, instead of minutes. |
Beta Was this translation helpful? Give feedback.
-
same problem here: only job with schedule " $ docker run \
-l "chadburn.enabled=true" \
-l "chadburn.job-exec.o.command=date +%Y-%m-%dT%H:%M:%S.%N-" \
-l "chadburn.job-exec.o.schedule=5-59/10 * * * * *" \
-d --name test_o nginx
$ docker run \
-l "chadburn.enabled=true" \
-l "chadburn.job-exec.oo.command=date +%Y-%m-%dT%H:%M:%S.%N--" \
-l "chadburn.job-exec.oo.schedule=5-59/1 * * * *" \
-d --name test_oo nginx
$ docker run \
-l "chadburn.enabled=true" \
-l "chadburn.job-exec.ooo.command=date +%Y-%m-%dT%H:%M:%S.%N---" \
-l "chadburn.job-exec.ooo.schedule=10 */1 * * * *" \
-d --name test_ooo nginx
|
Beta Was this translation helpful? Give feedback.
-
Hi @maietta , thanks for your work on this. |
Beta Was this translation helpful? Give feedback.
-
Hello! I saw your project and looked into migrating over due to support of dynamically adding in cron jobs. However I noticed that upon migrating over, all run jobs and certain exec jobs are not being seen. I largely use container labels to create and run tasks and have taken into account the change in the label prefix (ofelia to chadburn).
These examples tasks are taken from a docker-compose project I maintain on github that currently uses ofelia:
What does work with chadburn:
What does not work with chadburn:
I am not too sure if there are any additional configuration needed. but any assistance would be appreciated!
Also as a sidenote, would it be possible to omit the container option in run jobs?
Beta Was this translation helpful? Give feedback.
All reactions