sidekiq-cron | Scheduler / Cron for Sidekiq jobs | Cron Utils library

Getting 'Forbidden' on clicking 'Enqueue now' in staging and production environment.

Using 'rails', '5.1.6', sidekiq-cron (1.0.4) which uses fugit (~> 1.1) and sidekiq (>= 4.2.1)

I can see from sidekiq-cron issue 60 and sidekiq-cron issue 61 that issue got resolved a long back but still getting same issue.

I'm getting following warning at my console:

Passing 'connection' command to redis as is; blind passthrough has been deprecated and will be removed in redis-namespace 2.0 (at /home/tecorb/.rvm/gems/ruby-2.4.1@mproj/gems/sidekiq-5.1.3/lib/sidekiq/web/helpers.rb:152:in `block in redis_connection')

I'm using following gems in my Gemfile:

So I'm using Rails and I have a few Sidekiq workers, but none are enabled. I'm using the sidekiq-cron gem, which requires you to put files in app/workers/, configure a sidekiq scheduler in config/sidekiq_schedule.yml, and also add a few lines in config/initializers/sidekiq.rb. However, I've commented everything out from sidekiq_schedule.yml and also commented the following lines out from sidekiq.rb:

Hello I've installed Gitalb CE (v9.3.8) on my private server (Debian Stretch) and I have got myself into a problem with Sidekiq. Aparently it is trying to load an invalid JSON, but I don't know from where. Do you have any idea, where could have the "nalse" (second line in the log below) come from?

I have a Rails project that uses Sidekiq for worker tasks, and Sidekiq-Cron to handle scheduling. I am running into a problem, though. I built a controller (below) that handled all of my API querying, validation of data, and then inserting data into the database. All of the logic functioned properly.

I then tore out the section of code that actually inserts API data into the database, and moved it into a Job class. This way the Controller method could simply pass all of the heavy lifting off to a job. When I tested it, all of the logic functioned properly.

Finally, I created a Job that would call the Controller method every minute, do the validation checks, and then kick off the other Job to save the API data (if necessary). When I do this the first part of the logic seems to work, where it inserts new event data, but the logic where it checks to see if this is the first time we've seen an event for a specific object seems to be failing. The result is a Primary Key violation in PG.

Code below:

Controller

When run sidekiq, in log receive this error:

Start sidekiq with the command

My application uses Sidekiq and Sidekiq-Cron for background job processing.
Both Sidekiq and Sidekiq-Cron are included as gems in the global section of my Gemfile, and installed with bundle install in my application's rvm gemset.

After launching for the first time sidekiq or bundle exec sidekiq from the root of my Rails application, I received the following error message which I past and copy here for completeness: