I entered an incorrect schedule "@every 1d", because I thought that "d" is also allowed. I would have expected chadburn to report an error, when starting up/reading in the labels, but it doesn't.
Somehow chadburn is "reading/registering" the cron anyway, because once I fixed the problem, the log said this:
chadburn | scheduler.go:94 ▶ NOTICE Job deregistered (will not fire again) "optimize" - "php -dmemory_limit=-1 /web/app/console.php index:optimize" - "@every 1d" - ID: 0
It wasn't showing the registration, but the deregistration of the cron.
An error message would be very helpful in the logs, so those kind of problems can be identified easier.
PS: It would be great, if the log would also add information about the container (e.g. name or ID)
I entered an incorrect schedule "@every 1d", because I thought that "d" is also allowed. I would have expected chadburn to report an error, when starting up/reading in the labels, but it doesn't.
Somehow chadburn is "reading/registering" the cron anyway, because once I fixed the problem, the log said this:
It wasn't showing the registration, but the deregistration of the cron.
An error message would be very helpful in the logs, so those kind of problems can be identified easier.
PS: It would be great, if the log would also add information about the container (e.g. name or ID)