-
Notifications
You must be signed in to change notification settings - Fork 57
Description
Hi,
I've been using crono gem for production purposes.
Something oddly strange is happening and I don't have knowlege enough to uderstand. Can someone help me please?
My enviroment is running on a Amazon EC2 with Docker.
My docker compose.yml have a start comand:
command: "bundle exec crono -e production"
it runs but as soon as it starts crono this message happens:
bundler: failed to load command: crono (/usr/local/bundle/bin/crono) SignalException: SIGTERM /usr/local/bundle/gems/crono-1.1.2/lib/crono/job.rb:107:in 'synchronize' /usr/local/bundle/gems/crono-1.1.2/lib/crono/job.rb:107:in 'log' /usr/local/bundle/gems/crono-1.1.2/lib/crono/job.rb:39:in 'perform' /usr/local/bundle/gems/crono-1.1.2/lib/crono/cli.rb:124:in 'each' /usr/local/bundle/gems/crono-1.1.2/lib/crono/cli.rb:124:in 'block in start_working_loop' /usr/local/bundle/gems/crono-1.1.2/lib/crono/cli.rb:121:in 'loop' /usr/local/bundle/gems/crono-1.1.2/lib/crono/cli.rb:121:in 'start_working_loop' /usr/local/bundle/gems/crono-1.1.2/lib/crono/cli.rb:40:in 'run' /usr/local/bundle/gems/crono-1.1.2/exe/crono:8:in '<top (required)>' /usr/local/bundle/bin/crono:17:in 'load' /usr/local/bundle/bin/crono:17:in '<top (required)>'
I am running around trying figure it out. What it can be?