Sidekiq with Heroku & Rails : my Jobs are stucks in queue on Heroku
up vote
0
down vote
favorite
Solution EDIT :
The worker button on Heroku was not turned from Off to On...
I'm trying to use Sidekiq on my RailsApp. The configuration works fine in development but in Product with Heroku, all Jobs are enqued but stuck in queue.
Some insight :
I've done the config of Redis_to_go on Heroku.
Sidekiq dashboard
Heroku Job logs
2018-11-09T17:28:15.648569+00:00 app[web.1]: I, [2018-11-09T17:28:15.648360 #4] INFO -- : [66d0e53c-5fd1-42a9-bb28-4df4a40b6f09]
[ActiveJob] Enqueued CreateMemberContactJob (Job ID: 12785f83-5b69-4bc4-ad87-3945694e8337)
to Sidekiq(default) with arguments: #<GlobalID:0x000055ec32248780 @uri=#<URI::GID gid://youguildapp/Member/85>>
All my configuration & code :
Procfile
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq
Application.rb
config.active_job.queue_adapter = :sidekiq
Registrationscontroller.rb
CreateMemberContactJob.perform_later @member
class CreateMemberContactJob < ApplicationJob
queue_as :default
CreateMemberContactJob
class CreateMemberContactJob < ApplicationJob
queue_as :default
def perform(member)
api_instance = SibApiV3Sdk::ContactsApi.new
create_contact = SibApiV3Sdk::CreateContact.new
create_contact.email = member.email
api_instance.create_contact(create_contact)
end
end
Please help me, I've passed by all SO posts & Sidekiq wifi & Medium posts & holy books but I didn't figured out.
Many thanks
ruby-on-rails heroku sidekiq rspec-sidekiq
add a comment |
up vote
0
down vote
favorite
Solution EDIT :
The worker button on Heroku was not turned from Off to On...
I'm trying to use Sidekiq on my RailsApp. The configuration works fine in development but in Product with Heroku, all Jobs are enqued but stuck in queue.
Some insight :
I've done the config of Redis_to_go on Heroku.
Sidekiq dashboard
Heroku Job logs
2018-11-09T17:28:15.648569+00:00 app[web.1]: I, [2018-11-09T17:28:15.648360 #4] INFO -- : [66d0e53c-5fd1-42a9-bb28-4df4a40b6f09]
[ActiveJob] Enqueued CreateMemberContactJob (Job ID: 12785f83-5b69-4bc4-ad87-3945694e8337)
to Sidekiq(default) with arguments: #<GlobalID:0x000055ec32248780 @uri=#<URI::GID gid://youguildapp/Member/85>>
All my configuration & code :
Procfile
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq
Application.rb
config.active_job.queue_adapter = :sidekiq
Registrationscontroller.rb
CreateMemberContactJob.perform_later @member
class CreateMemberContactJob < ApplicationJob
queue_as :default
CreateMemberContactJob
class CreateMemberContactJob < ApplicationJob
queue_as :default
def perform(member)
api_instance = SibApiV3Sdk::ContactsApi.new
create_contact = SibApiV3Sdk::CreateContact.new
create_contact.email = member.email
api_instance.create_contact(create_contact)
end
end
Please help me, I've passed by all SO posts & Sidekiq wifi & Medium posts & holy books but I didn't figured out.
Many thanks
ruby-on-rails heroku sidekiq rspec-sidekiq
1
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
1
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Solution EDIT :
The worker button on Heroku was not turned from Off to On...
I'm trying to use Sidekiq on my RailsApp. The configuration works fine in development but in Product with Heroku, all Jobs are enqued but stuck in queue.
Some insight :
I've done the config of Redis_to_go on Heroku.
Sidekiq dashboard
Heroku Job logs
2018-11-09T17:28:15.648569+00:00 app[web.1]: I, [2018-11-09T17:28:15.648360 #4] INFO -- : [66d0e53c-5fd1-42a9-bb28-4df4a40b6f09]
[ActiveJob] Enqueued CreateMemberContactJob (Job ID: 12785f83-5b69-4bc4-ad87-3945694e8337)
to Sidekiq(default) with arguments: #<GlobalID:0x000055ec32248780 @uri=#<URI::GID gid://youguildapp/Member/85>>
All my configuration & code :
Procfile
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq
Application.rb
config.active_job.queue_adapter = :sidekiq
Registrationscontroller.rb
CreateMemberContactJob.perform_later @member
class CreateMemberContactJob < ApplicationJob
queue_as :default
CreateMemberContactJob
class CreateMemberContactJob < ApplicationJob
queue_as :default
def perform(member)
api_instance = SibApiV3Sdk::ContactsApi.new
create_contact = SibApiV3Sdk::CreateContact.new
create_contact.email = member.email
api_instance.create_contact(create_contact)
end
end
Please help me, I've passed by all SO posts & Sidekiq wifi & Medium posts & holy books but I didn't figured out.
Many thanks
ruby-on-rails heroku sidekiq rspec-sidekiq
Solution EDIT :
The worker button on Heroku was not turned from Off to On...
I'm trying to use Sidekiq on my RailsApp. The configuration works fine in development but in Product with Heroku, all Jobs are enqued but stuck in queue.
Some insight :
I've done the config of Redis_to_go on Heroku.
Sidekiq dashboard
Heroku Job logs
2018-11-09T17:28:15.648569+00:00 app[web.1]: I, [2018-11-09T17:28:15.648360 #4] INFO -- : [66d0e53c-5fd1-42a9-bb28-4df4a40b6f09]
[ActiveJob] Enqueued CreateMemberContactJob (Job ID: 12785f83-5b69-4bc4-ad87-3945694e8337)
to Sidekiq(default) with arguments: #<GlobalID:0x000055ec32248780 @uri=#<URI::GID gid://youguildapp/Member/85>>
All my configuration & code :
Procfile
web: bundle exec puma -C config/puma.rb
worker: bundle exec sidekiq
Application.rb
config.active_job.queue_adapter = :sidekiq
Registrationscontroller.rb
CreateMemberContactJob.perform_later @member
class CreateMemberContactJob < ApplicationJob
queue_as :default
CreateMemberContactJob
class CreateMemberContactJob < ApplicationJob
queue_as :default
def perform(member)
api_instance = SibApiV3Sdk::ContactsApi.new
create_contact = SibApiV3Sdk::CreateContact.new
create_contact.email = member.email
api_instance.create_contact(create_contact)
end
end
Please help me, I've passed by all SO posts & Sidekiq wifi & Medium posts & holy books but I didn't figured out.
Many thanks
ruby-on-rails heroku sidekiq rspec-sidekiq
ruby-on-rails heroku sidekiq rspec-sidekiq
edited Nov 10 at 8:06
asked Nov 9 at 17:41
Gdebrick
506
506
1
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
1
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00
add a comment |
1
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
1
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00
1
1
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
1
1
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53230815%2fsidekiq-with-heroku-rails-my-jobs-are-stucks-in-queue-on-heroku%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Stupid assumption, but check if your sidekiq worker is turned on on Heroku, it is off by default
– Vasilisa
Nov 9 at 18:35
1
That is likely the answer: you haven't actually started a Sidekiq worker dyno.
– Mike Perham
Nov 9 at 22:04
@Vasilisa & Mike, you found the solution : it was the button... Many thanks! Cheers
– Gdebrick
Nov 10 at 8:00