Displaying 9 results from an estimated 9 matches for "backgroundrb_debug".
2008 Jan 02
3
disabling backgroundrb_debug.log
is there an easy way to disable logging to backgroundrb_debug.log?
Regards
- reynard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080102/195dee18/attachment.html
2008 Mar 19
2
nil-error
Hi all,
I''ve got the error below in my backgroundrb_debug.log. I''ve tried to
reproduce the error in the development environment, but the only way I
can get the same thing is by calling ask_work with a bogus worker
name. Calling it with the production code causes no error.
Here''s an example of what the code calls:
MiddleMan.ask_work(:wo...
2008 Jan 22
9
Cannot connect when spawning new workers on demand
Hi!
I''m using the latest&greatest backgroundrb with rails 2.0.2 on ubuntu
dapper.
I''ve made an app that lets you run a query on several servers at once,
which are selected at runtime. Therefore, for each server that is
selected, I spawn a new worker and assign its work.
After everything is completed, the workers are deleted.
I often get this error:
2008 Jan 03
5
Start script not working when run via Rake
...e a Rake task, it
doesn''t launch the worker processes.
The Rake task is as follows:
task :start_backgroundrb do
run "cd #{current_path} && ./script/backgroundrb start"
end
When I run this task, the following files are created in the log directory:
backgroundrb.pid
backgroundrb_debug.log
backgroundrb_server.log
Observations: The process ID found in backgroundrb.pid doesn''t exist,
backgroundrb_server.log is zero bytes long and backgroundrb_debug.log
contains the following:
# Logfile created on Thu Jan 03 14:43:24 +0000 2008 by /
It looks like the process is being s...
2008 Jan 04
1
Updates and Fixes on Trunk
Hi,
I am pushing some updates and fixes that addresses much of the issues
that we talked about since last couple of days.
1. Use configuration option :debug_log: false to disable
backgroundrb_debug.log.
2. As shown below, use lazy_load option to disable aggressive loading
of models ( and somewhat stupid too).
3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the
worker, it won''t wait for tasks to finish. I am still skeptic about
the behavior, but since that was th...
2008 Jan 15
1
actionmailer the background
...e production server csv processing works well, but sending emails
throws errors in the background.
Note: I can successfully upload a csv, then fail trying to send
emails, then successfully upload another csv file. Also, sending
emails works in production when used outside of backgroundrb.
backgroundrb_debug.log reports this
PGError: no connection to the server
: SELECT a.attname, format_type(a.atttypid, a.atttypmod), d.adsrc,
a.attnotnull
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = ''sandboxed_libraries''::regclass
A...
2007 Dec 19
6
thread_pooling sleeping
...39;'Thread.new'' method, I get a "no marshal_dump is defined for
class Thread" exception in the backgroundrb_server log. I''m guessing
this has something to do with why I''m supposed to be using thread_pool
instead of Thread).
When I get those read errors, the backgroundrb_debug.log shows "Client
disconected" (sic). I don''t know if this is normal for rails talking
to bgrb or if it''s an error. I don''t see it on every line, but it
seems to coincide with the "some read error" messages in the script.
Am I doing something wrong? A...
2007 Dec 18
1
Backgroundrb crash calling ask_status when worker not running
When I call ask_status on a worker that has not been started I get and
exception of type BackgrounDRb::BdrbConnError, which is fine. I can deal
with that, but I also find that the backgroundrb process dies as well.
The scenario is simple: Call ask_status on a worker that is not auto
loaded. I used a job_key, in case that makes a difference.
-------------- next part --------------
An
2008 Jan 16
2
mysterious crash of a particular worker
...16 16:10 StatusChecker: check method started
2008-01-16 16:10 StatusChecker: processing host head0
2008-01-16 16:10 StatusChecker: processing domain webconsole
2008-01-16 16:10 StatusChecker: processing host host1
After 16:10 the worker seems to have disappeared. I found the
following message in backgroundrb_debug.log:
/home/webcon/apps/webconsole/releases/20080115103838/vendor/plugins/
backgroundrb/server/meta_worker.rb:329:in `check_for
_timer_events'': undefined method `info'' for nil:NilClass (NoMethodError)
from /home/webcon/apps/webconsole/releases/20080115103838/
vendor/plu...