Cron not running in docker, added to supervisord config #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sandywater
added a commit
that referenced
this pull request
Dec 17, 2014
Cron not running in docker, added to supervisord config
|
@ahoying very nice. That would explain why the scheduled backups weren't working 😉 |
|
@ahoying I think we are going to need to run cron in non-daemon mode: http://stackoverflow.com/a/20548563 This might be why you were seeing those errors |
|
I changed the command to /usr/sbin/cron -f and that fixed the issue, and cron still works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this change, alertbot.pl never runs. Cron does work once it is added to the supervisor configuration, but I do get this error in cron.stderr.log: "/usr/sbin/cron: can't lock /var/run/crond.pid, otherpid may be 20: Resource temporarily unavailable" I'm not sure if it is a docker issue, or something with the cron configuration. It doesn't seem to impact anything.