Displaying 20 results from an estimated 3000 matches similar to: "Yet Another Problem with BackgroundRB"
2007 Jan 15
2
Backgroundrb keeps spawning processes
Hi!
I''ve just a created a really simple rails scheduled worker for
backgroundrb to start playing with :
class SessionCleanerWorker < BackgrounDRb::Worker::RailsBase
def do_work(args)
logger.info "SessionCleaner> started"
CGI::Session::ActiveRecordStore::Session.destroy_all( [''updated_at
<?'', 120.minutes.ago] )
2006 Dec 08
2
trouble using ActiveRecord classes
I''ve been trying unsuccessfully for the better part of today to write a
worker that can use by ActiveRecord model classes.
The bizarre thing is that worker just stops at the point accessing the
database connection. An exception isn''t raising, it just dies.
My worker class is below, I''ve interspersed log messages throughout to try
to determine where it is dying.
=====
2007 Dec 18
9
Long-running pages cause mongrel time-outs
Hi all,
We use mongrel behind apache (using mod_proxy_balancer) to run an internal
app for our business. Lately we''ve been seeing frequent errors from some of
our mongrel processes.
[Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] (70007)The timeout
specified has expired: proxy: error reading status line from remote server
127.0.0.1, referer:
2007 Jan 04
10
Intermittent "can''t convert Float into Hash" and results.rb
Hi,
I''m using backgroundrb 0.2.1 in a production environment and for most
parts I''m very happy. We are using it to do some heavy video editing on
the server side and it works great except that under, what seems heavy
load the below problem happens intermittently.
The problem has only happened 5 times out of over 500 runs by our
backgroundrb worker.
This is the code in our
2007 Jan 29
4
loading C extension in worker causes bus error on OS X only
In all likelihood, this doesn''t have anything to do with backgroundrb,
but I''m stuck so I thought someone might be able to help.
I have a pretty simple C extension that I built into a gem and have
installed on my system. It works fine when required from rails
(1.2.1).
But when I have a Backgroundrb worker class use the extension (under
os x), I get:
2007 Jan 27
1
Memory leaks in backgroundrb
While debugging stale backgroundrb it became apparent that there''re
memory leaks in it. Here''s top object counts dump:
36715 String
6211 Array
5598 Proc
3150 Hash
1478 DRb::DRbObject
1313 Regexp
1272 Class
750 Thread
741 Socket
739 Slave
739 Slave::LifeLine
737 Process::Status
691 DrillReminderWorker
391 Module
160 Range
75 Gem::Version
2007 May 15
6
Behaviour of pool_size setting
Hi,
I have backgroundrb running to decouple the execution of massive
business logic from an ActionWebservice request. The service is designed
to take some configuration parameters and fire a lot of background
workers to do the requested work. Due to performance reasons I want to
limit the number of workers to a maximum number of 30. But when I start
a configuration that requires for example
2007 Mar 04
6
Backgroundrb spiking CPU after first run on Mongrel cluster
I''ve been troubleshooting this problem for several hours now and haven''t
been able to figure out what''s wrong. I have two boxes, dev and prod, both
are identical except that prod uses Ruby 1.8.5 and dev uses 1.8.4. Both are
running Slave 1.2.0, Daemons 1.0.5, and Backroundrb 0.2.1.
The behavior I''m seeing is this. When I first start Backgroundrb, this is
what
2007 Mar 13
5
worker starting twice
Hi gang,
Thanks to other help I''ve gotten on this list, I''ve got backgroundrb
up and running using postgres alongside my rails app. I''ve designed
the system to have several eternally-running workers that periodically
poll the database to see if there''s any work for them to do, and set
things up in the config file to make them restart quickly if any of
them
2007 May 22
4
Recommendations for eternally-running backgroundrb workers?
I''ve got some workers that I want to have running all the time. Right
now I''m just launching them manually, by requesting a special page in
my rails app that includes lines like:
MiddleMan.new_worker(:class=> :receiver, :job_key=>:r,
:args=>{:sleep_time=>10})
This strikes me as a really weak way to fire up my workers. I
basically want to automate things so
2007 Apr 18
5
[BUG] worker stopping abruptly
I have been facing this damn ugly issue since quite sometime.
So this worker reads RSS feed from Yahoo news and stores it in a DB.
The worker is scheduled to run at every 40 minutes and my
background_schedules.yml looks like this:
feed_worker:
:class: :feed_worker
:job_key: :feed_worker_key
:worker_method: :do_work
:trigger_args:
:start: <%= Time.now + 5 %>
2007 Apr 04
6
Exception when doing DRb remote calls from a BackgrounDRb worker
Hello,
I am trying to make DRb calls to a external server from a backgrounDRb
worker, but I''m getting always the next exception when I make the remote
call.
> ERROR:
> drbunix:///tmp/backgroundrb.11175/experimenter_worker_3e899de945f0803a82cd257cfac316d0_0_0.0738904928422051
> - #<Errno::ENOENT: No such file or directory -
>
2008 Jan 14
3
problem with backgroundrb
hi, i am using drb and it is working fine on my local pc on windows..
and after uploading the code to the server it was working for
sometime but now it gives me error every time i invoke the process..
error---
uninitialized constant EmailWorker::Notifier - (NameError)
/usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/
dependencies.rb:477:in `const_missing''
2007 Aug 08
3
Cannot start workers in production mode
I have a job that I am starting from a Rails controller in production mode
using MiddleMan:
MiddleMan.new_worker(:class => :import_ccg_category_worker, :args => {
:category_id => @category.id, :remote_category_id =>
params[:remote_category_id], :description => "Importing CCG products for #{@
category.name}" })
Both of the category ID variables are just basic integers. I
2007 Jan 19
6
Stopping DRb after using BackgrounDRb::MiddleManDRbObject.init
Hi,
I''m having a problem where connections started through
BackgrounDRb::MiddleManDRbObject.init are not stopped, resulting in an
ever growing established connections between my Mongrels and remote
backgroundrbs
I added DRb.stop_service to my code executed after requests that init
MiddleManDRbObjects but that does not help.
Any ideas?
Thanks,
Robert Bjarnason
2006 Aug 07
2
uninitialized constants in worker class
I am new to this list and relatively new to the backgroundrb plugin,. So
first i will say hello to everybody here, especially to Ezra
Zygmuntowicz!
I played a little bit with a dummy worker and so far everything worked
well.
But now i want to do real work in a worker but now i get that error[1].
It looks like that the constants configured in environment* configs are
not available to the worker
2006 Nov 29
6
Noob needs help installing backgroundrb on Windows XP
Hey Guys,
In the readme for Backgroundrb it says that windows support has been
depcreated for this version, but then it goes on to mention how to use
it in Windows. So I''m not sure if it should be running on windows or
not, so I''ll ask anyway. Also, I''m new to ruby and I''m also new to
server administration, so I apologize if my questions are pretty
2007 Apr 09
1
Drb Connection error on multiple dispatch.fcgi ''s
Hi All,
I''m using Backgroundrb as a general purpose long-running-task back-end
(upload processing, email sending, etc), and it''s been a great solution.
However I''ve recently run into some some intermittent connection issues
that have me baffled. I''m running on apache2/fcgid and the problem
occurs in both devlopment and production mode. The problem seems to
2007 Nov 30
1
backgroundrb not cleaning up tmp files?
I just had an interesting issue on a production system that has been
running nicely for about a year. There were approximately 10,000
backgroundrb temp files in the /tmp directory. It looks like
backgroundrb wasn''t cleaning them up.
I noticed it with the following error:
DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/
backgroundrb_logger_0_0.101544829808665 -
2006 Nov 20
4
Production RAILS_ENV / DB Selection
Hey all,
I''m having some issues moving a project that incorporates Backgroundrb onto
a staging server... For some reason (surely of my own doing), my RailsBase
workers are insisting on using trying to access my development DB instead of
my "production" DB.
When I try to load a model object from within a worker, I get the following:
20061120-21:54:28 (26296)