Hmmm, for whatever reason GitLab isn't compatible with the latest version of Sidekiq (2.17.7) and downgrading to 2.17.0 fixes this issue!
Eric Le jeudi 20 mars 2014 à 10:36 +0100, Eric van der Vlist a écrit : > Le jeudi 20 mars 2014 à 10:05 +0100, Sytse Sijbrandij a écrit : > > Are you sure Sidekiq is running and looking in the correct queue? > > Running, yes: > > vdv@community:~$ ps ax | grep sidekiq > 5471 ? Sl 0:11 sidekiq 2.17.7 gitlab [0 of 25 > busy] > > I am trying to find out how I can check if there isn't a mismatch and > where the queue is configured (without success so far)... > > Thanks, > > Eric > > > On Thu, Mar 20, 2014 at 9:53 AM, Eric van der Vlist <[email protected]> > > wrote: > > > Le jeudi 20 mars 2014 à 07:52 +0100, Sytse Sijbrandij a écrit : > > >> Do you have failed Sidekiq tasks? > > > > > > No, according to the background jobs page in the admin area there are no > > > failed tasks, just enqueued tasks that are never processed. > > > > > > Is it possible that there is a mismatch somewhere (in the queue name for > > > instance). > > > > > >> If so, please investigate the error message and the logs for them. > > > > > > The following message is logged when Sidekiq is started: > > > > > > Instance method "lock!" is already defined in ActiveRecord::Base, use > > > generic helper instead or set > > > StateMachine::Machine.ignore_method_conflicts = true. > > > > > > The only other messages in the log are: > > > > > > 2014-03-19T22:52:11Z 9880 TID-ot7djlzlg INFO: Booting Sidekiq 2.17.7 > > > with redis options > > > {:url=>"redis://localhost:6379", :namespace=>"resque:gitlab"} > > > 2014-03-19T22:52:11Z 9880 TID-ot7djlzlg INFO: Running in ruby 2.0.0p247 > > > (2013-06-27 revision 41674) [x86_64-linux] > > > 2014-03-19T22:52:11Z 9880 TID-ot7djlzlg INFO: See LICENSE and the > > > LGPL-3.0 for licensing details. > > > > > > Thanks, > > > > > > Eric > > > > > >> On Thu, Mar 20, 2014 at 12:03 AM, Eric van der Vlist <[email protected]> > > >> wrote: > > >> > Hi, > > >> > > > >> > Emails notifications are queued to the "mailer" queue but never > > >> > processed nor dequeued by the 25 idled workers... > > >> > > > >> > Does anyone have any idea of what can cause this type of situation and > > >> > how I can fix it? > > >> > > > >> > Thanks, > > >> > > > >> > Eric > > >> > > > >> > -- > > >> > You received this message because you are subscribed to the Google > > >> > Groups "GitLab" group. > > >> > To unsubscribe from this group and stop receiving emails from it, send > > >> > an email to [email protected]. > > >> > For more options, visit https://groups.google.com/d/optout. > > >> > > > > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "GitLab" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [email protected]. > > > For more options, visit https://groups.google.com/d/optout. > > > > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
