thanks for the tips. I had thought about spawn & god but what's the
point of a daemon if the connection to Active Record goes away?!
how come the memory isn't freed.
Can I call "something" in my loop to
"clean up"? Do I have to?
This graph shows how nuts the process is going (before to be killed I
guess) after the daemons has been running for about a day or 2.
I haven't take the time yet to look at how God can help me - the last
time I looked at God it wasn't trivial :(
But from the Feedzirra perspective (and thus, this is a question to
the main dev), where could be the problem?
Log the output from that daemon.
True, it's pretty dumb to have this require there. I remember having
tried to have it in my environment.rb but was unsuccessful. Anyways, I
moved it to the top of the source file (so outside the method) and
we'll see if it changes anything.
Concerning the logs, they are supposed to be in /log, right? There
nothing relevant there :(
Attached a chart that shows when I restarted the daemon. We'll see
over time if the require was the problem. Aside the daemon, would you
have a good tip to profile my "Episode.fetch_all"?
script/performance isn't much helpful i.m.h.o.
On Wed, May 26, 2010 at 10:59 PM, Paul Dix <pa...@pauldix.net> wrote:
> It depends on how/what you're using to daemonize the process that is
> running these updates. Whatever it is should have the ability to write
> STDOUT and STDERR to some log file. If you aren't specifying that then
> the process is probably just throwing an exception that isn't being
> captured by anything.
These types of errors are a real time suck. Hardest to track down. :(
I would need the "new/next" cron to only start when the previous is
finished. I was thinking to maybe program the next cron 1 minute after
the current is finished. Any Ideas/recommandations?
Sadly like a lot of open source things, Servolux is pretty
undocumented. Watching at this: http://rdoc.info/projects/TwP/servolux
, will anyone have a code sample showing how I could call my
"fetch_episodes" from a worker?
I'm a bit confused.
ps: Obviously it still dies after a few days with the daemon.
I wanted to let you know everything works fine since I started using
the "delay" method from http://tobi.github.com/delayed_job/ instead of
using a daemon. It then spawns himself without any work from me.
Really, the only thing I do other than installing the plugin/gem is:
Podcast.all.each do |podcast|
then I call the first time Episode.delay.fetch_all from one way
(script/console) or another (capistrano) and boom!, it's running for
weeks without any problem.
Hope that helps anyone.