rufus-scheduler | scheduler for Ruby (at, in, cron and every jobs) | Job Scheduling library

In your project directory, try installing rails gem install rails -v 4.1.6 and removing the version from the failing gems like (liquid_markdown, gon, etc..) then try running bundle update then bundle clean --force

I think this might be an issue because all the version of these gems are locked inside your Gemfile

I am the author of most of what you consider "verbiage". I will add to this mountain of verbiage by answering to your question.

In fact, I double checked by creating a simpler version of your project. It's at

https://github.com/jmettraux/sof63386937

What you are encountering is not a rufus-scheduler issue. It's simply you misunderstanding Rake.

The way to make Rake cooperate:

Their docs make it look like you only need to set the URL for redis and not an instance of redis https://github.com/resque/resque/blob/master/README.markdown#configuration

You could try with

Your problem here is you are using a for loop instead of an Enumerable method such as each.

Short answer, just change for x in 0..s3 to sume2.each_index do |x|

Longer answer, you can compare the following:

Sorry for the late answer.

What you are seeing is the output of Scheduler#on_error. By default it outputs to stderr.

This destination can be overriden as explained in the readme but it's probably better to override #on_error, as detailed in the readme as well.

Your #on_error might thus look like

According to the project README, you can specify the cron job with a timezone as follows:

So, Heroku dynos not sharing the file system

The .rufus-scheduler-a.lock seen on dyno d0 is not the .rufus-scheduler-a.lock seen on dyno d1.

Your Heroku dynos do not share the same filesystem and also they do not share the same Ruby process and thus not the same rufus-scheduler instance. So overlap: false, blocking: true will not have any effect from dyno d0 to dyno d1.

You could implement a custom locking mechanism for rufus-scheduler taking inspiration from https://github.com/jmettraux/rufus-scheduler#advanced-lock-schemes (probably via the database because it's shared by your Ruby processes) but that will not help with overlap: false and blocking: true.

If you still want to have overlap: false and blocking: true, you could look at https://devcenter.heroku.com/articles/scheduled-jobs-custom-clock-processes and have the scheduling happening in a dedicated process/dyno with rufus-scheduler or Clockwork and have no need for a schedule lock.

The rest of my answer is about your code, not about the double scheduling you are experiencing.

scheduler.down?

Is this all the code? I ran it and it worked fine for me.