On Fri, Jun 7, 2013 at 6:58 AM, James Bardin <[email protected]> wrote: > On Thursday, June 6, 2013 11:40:34 AM UTC-4, James Bardin wrote: >> I've got a running beanstalk showing 1 delayed job, but I can't access it. >> >> >>> bs.stats()['current-jobs-delayed'] >> 1 >> >>> bs.peek_delayed() >> None >> >>> bs.kick() >> 0 > > An upgrade to 1.9 didn't change anything. > However the job did get processed last night. > > I does concern me though, that I couldn't peek, or kick the delayed job at > all.
Was the job in a different tube? It's possible your peek and kick commands were operating on one tube, and the job was in another. The global stats command gives totals for all tubes. -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
