Hi Chris, Not sure if this will help... we were using delayed_job in an AWS environment. Found that every time we deploy a new code, we have to first kill the running delayed_job in the instance first. Deploy the new code and then run the delayed_job again.
Can't remember what it was doing that was causing it to fail (it was done about 2 years go!). Hock Sin On Wed, Sep 24, 2014 at 4:26 PM, Chris Griffin <[email protected]> wrote: > After 2 weeks of banging my head I haven't been able to make this work. I > need to ship this soon. Let me know if you can help. I will pay whatever > your rate is! > > Chris > > -- > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby > --- > You received this message because you are subscribed to the Google Groups > "SD Ruby" 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. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" 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.
