All geek questions in one place

Rails Resque.enqueue development environment does not create jobs

I have the same problem as the Rails custom Resque.enqueue environment does not create jobs , but the solution there does not work for me.

I am using Resque for several asynchronous jobs. It works great for a staging environment, but for some reason it stops working in a development environment.

For example, if I run the following:

 $ rails c development > Resque.enqueue(MyLovelyJob, 1)

Nothing is specified. I am checking Resque using resque-web

If I launched it at the stage of setting - it works fine.

 $ rails c staging > Resque.enqueue(MyLovelyJob, 1)

I tried duplicating environment 2, and they seem to use exactly the same configurations (database.yml, config / environment, etc.), but development still doesn't work.

If i do

  > Resque.enqueue(UpdateInstancesData, 2) > => true > Resque.info > => { > :pending => 0, > :processed => 0, > :queues => 0, > :workers => 1, > :working => 0, > :failed => 0, > :servers => [ > [0] "redis://127.0.0.1:6379/0" > ], > :environment => "development" > }

Any suggestions where to look to debug this?

I launch the application through the wizard. My Procfile looks like this:

faye: rackup faye.ru -s thin -E production

worker1: bundle exec rake resque: work QUEUE = * VERBOSE = 1

worker2: bundle exec rake resque: work QUEUE = * VERBOSE = 1

clock: bundle exec rake resque: scheduler VERBOSE = 1

web: bundle exec rails s

For staging , as already mentioned, everything works, and the log from the wizard:

 17:03:42 clock.1 | 2013-06-26 17:03:42 Reloading Schedule 17:03:42 clock.1 | 2013-06-26 17:03:42 Loading Schedule 17:03:42 clock.1 | 2013-06-26 17:03:42 Scheduling logging_test 17:03:42 clock.1 | 2013-06-26 17:03:42 Schedules Loaded 17:03:43 worker2.1 | *** Starting worker ttttt-mbp.local:69573:* 17:03:43 worker2.1 | *** Registered signals 17:03:43 worker2.1 | *** Running before_first_fork hooks 17:03:43 worker1.1 | *** Starting worker ttttt-mbp.local:69572:* 17:03:43 worker1.1 | *** Registered signals 17:03:43 worker2.1 | *** Checking another_queue 17:03:43 worker2.1 | *** Checking anotherqueue 17:03:43 worker2.1 | *** Checking statused 17:03:43 worker2.1 | *** Found job on statused 17:03:43 worker2.1 | *** got: (Job{statused} | LoggingTest | ["57e89a1c1b24ce6866bcf5d0e1c07f01", {}]) 17:06:30 clock.1 | 2013-06-26 17:06:30 queueing LoggingTest (logging_test) 17:06:33 worker1.1 | *** Checking another_queue 17:06:33 worker2.1 | *** Checking another_queue 17:06:33 worker1.1 | *** Checking anotherqueue 17:06:33 worker2.1 | *** Checking anotherqueue 17:06:33 worker1.1 | *** Found job on anotherqueue 17:06:33 worker1.1 | *** got: (Job{anotherqueue} | LoggingTest | ["0d976869a945766e0cfeca83e7349305", {}]) 17:06:33 worker1.1 | *** resque-1.24.1: Processing anotherqueue since 1372259193 [LoggingTest] 17:06:33 worker1.1 | *** Running before_fork hooks with [(Job{anotherqueue} | LoggingTest | ["0d976869a945766e0cfeca83e7349305", {}])] 17:06:33 worker1.1 | *** resque-1.24.1: Forked 69955 at 1372259193 17:06:33 worker2.1 | *** resque-1.24.1: Forked 69956 at 1372259193 17:06:33 worker1.1 | *** Running after_fork hooks with [(Job{anotherqueue} | LoggingTest | ["0d976869a945766e0cfeca83e7349305", {}])] 17:06:33 worker1.1 | JOB :: LoggingTest 17:06:33 worker1.1 | 55555 17:06:33 worker1.1 | *** done: (Job{anotherqueue} | LoggingTest | ["0d976869a945766e0cfeca83e7349305", {}])

whereas for development , it does not seem to get into the queue, and then finds work. If there is work in the queue (waiting, remaining from the intermediate environment), workers from development do not process it.

 17:01:23 clock.1 | 2013-06-26 17:01:23 Reloading Schedule 17:01:23 clock.1 | 2013-06-26 17:01:23 Loading Schedule 17:01:23 clock.1 | 2013-06-26 17:01:23 Scheduling logging_test 17:01:23 clock.1 | 2013-06-26 17:01:23 Scheduling update_instances_data 17:01:23 clock.1 | 2013-06-26 17:01:23 Schedules Loaded 17:03:10 clock.1 | 2013-06-26 17:03:10 queueing LoggingTest (logging_test) 17:03:14 worker1.1 | *** Checking another_queue 17:03:14 worker2.1 | *** Checking another_queue 17:03:14 worker1.1 | *** Checking anotherqueue 17:03:14 worker2.1 | *** Checking anotherqueue 17:03:14 worker1.1 | *** Checking statused 17:03:14 worker2.1 | *** Checking statused
+6
source share
2 answers

The problem turned out to be that I had a gem 'resque_spec' also for the :development group in my Gemfile. Obviously a very wrong thing ...

+23
source

My problem was that orphans were working in the background. Instead, they collected jobs.

By restarting redis, all workers will die.

0
source

Source: https://habr.com/ru/post/948068/

More articles:


All Articles