Re: How to debug code written for delayed_job?

[Oren Teich]

you need to use our new beta logging service ASAP.
http://addons.heroku.com/logging

Oren

On Mon, Jan 3, 2011 at 4:02 PM, Todd  wrote:

>
> I'm curious how people go about debugging code written for
> delayed_job.
>
> I originally had some code that in my model that interacted with a
> webservice, the code was in a single method
> "update_google_mailing_list" -- I then decided to move that code into
> a delayed job. Whenever I call that method, I call
> self.delay.update_google_mailing_list -- and it has worked fine.
>
> I'm now discovering that there are some edge cases that I need to
> handle, and it's not clear exactly what is going wrong with the code.
> I'd love to hook up my debugger to see what is going on, but it's
> production code and I need to identify more information about the
> state of things. I'd love to look at the delayed_job log file, but
> currently this is what I see, even when I do logger.info()
>
>
> ==> dyno-1491696.log <==
> Exceptional::Config.load - no configuration file
> >> Thin web server (v1.2.6 codename Crazy Delicious)
> >> Maximum connections set to 1024
> >> Listening on 0.0.0.0:38556, CTRL+C to stop
>
> Thanks for your advice,
>
> Todd
>
> --
> You received this message because you are subscribed to the Google Groups
> "Heroku" group.
> To post to this group, send email to her...@googlegroups.com.
> To unsubscribe from this group, send email to
> heroku+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

How to debug code written for delayed_job?

[Todd]

I'm curious how people go about debugging code written for
delayed_job.

I originally had some code that in my model that interacted with a
webservice, the code was in a single method
"update_google_mailing_list" -- I then decided to move that code into
a delayed job. Whenever I call that method, I call
self.delay.update_google_mailing_list -- and it has worked fine.

I'm now discovering that there are some edge cases that I need to
handle, and it's not clear exactly what is going wrong with the code.
I'd love to hook up my debugger to see what is going on, but it's
production code and I need to identify more information about the
state of things. I'd love to look at the delayed_job log file, but
currently this is what I see, even when I do logger.info()


==> dyno-1491696.log <==
Exceptional::Config.load - no configuration file
>> Thin web server (v1.2.6 codename Crazy Delicious)
>> Maximum connections set to 1024
>> Listening on 0.0.0.0:38556, CTRL+C to stop

Thanks for your advice,

Todd

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.