similar to: Storing worker driven rails logging in worker log file?

I have a worker which wants to delete itself after it finishes its work- how can it do that? Best Regards, Danny Burkes

Hi, Im just wondering what strategy I should use for checking out from your repo. I''ve seen posts here announcing BackrounDRb 1.0 RC 2, 1.0 but I don''t see any tags in the repo for these releases - I only see two old tags (release-0.2.0 & release-0.2.1). I''m assuming the HEAD code might be a bit unstable at times so should I use timestamps for checking

02.12.2017 2:16, mj via samba пишет: > - power off the old DCs > - reize fsmo roles, cleanup the database, etc why not to transfer roles while old DC are online? > - add new 4.7.2 DCs using their old names/ips > - remove the temporary DC why not simply add new DCs to current production domain? I'm thinking about way to upgrade too, but using "separated environment"

In my app, I store the job key when a worker is fired off and then check back in periodically to see how its doing. The workers delete themselves when they''re done. I would expect when I try to get a worker that has been deleted, I would get nil or a proper exception, but instead I get: >> MiddleMan.worker(''foobar'') NoMethodError: undefined method

We ran into some problems accessing a freshly created worker, and had to insert a sleep of 1 second to get it to work. It looks like Ezra and skaar already know this: from middleman.rb: # HACK: there is a race in the worker/slave creation, we # currently need to sleep between create. sleep 0.1 You might want to increase it to 1 second for those of us on slowly mac books.

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

Hi, Is it possible to start a worker with job_key and then ask_status of that specific worker with the job_key? MiddleMan.ask_work(:worker => :auth_worker, :job_key=>''1'', :worker_method => :auth) and then MiddleMan.ask_status(:worker => :auth_worker, :job_key=>''1'') >From my testing of the new backgroundrb, asking status using job key

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

Hi , I was wondering if anyone else has tried to use the Timeout::timeout method in a backgroundrb Worker and had Timeout raise an exception after the allotted amount of time . I ask because i have written a test script to make sure Timeout would work . I have tested the script by directly feeding it to ruby with : $ ruby test_script.rb and piping the script to the rails console: $

Is there something special I need to do to access session data in a worker? I''m using an AR session store. I''ve been working with Ezra''s tutorial, modifying it a little here and there to figure it out. So I changed the progress bar to a simple count-down in the worker which sends back the count to display in the view. No big deal. But if I try to access session

I have installed backgroundrb. I can start it. I have read everything I can get my hands on, and have read the list for a few months. I have written a worker, and am ready to start. This worker reads a queue, and processes it (sends queued emails). Sends 10, sleeps for a minute, sends 10 until done - very straightforward. My question is, what would be the best way to run this? I have

Hi all, i was using bdrb a while ago and it wasn''t stable enough in version 0.2.1 for doing the job - it loss jobs or did execute only the first one invoked and so on. Now i gave the new version a try and i found a bug at playing around. When i start a worker_method over the normal Unix scheduler bdrb will start as much as possible the worker_method after the :end-time is reached.

I thought I could delete a busy worker by calling MiddleMan.delete_worker, but doesn''t seem to end. I believe this was possible in 0.2, is it not in 1.0? thanks, Zach -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080103/0c701f29/attachment.html

If there is an exception raised in my worker I rescue it and throw it into the log. This is decent, but it would really help to find out more information. Like the line number, the stack trace, etc. Is this possible? Thanks for your help. Thank You, Ben Johnson E: bjohnson at contuitive.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

I''m using backgroundrb for its scheduled jobs. Now, a job that runs on a daily basis creates an xml file that I currently create with an .rxml template. Can I run a controller action from within a worker ? Can I render() a template from within a worker ? Sorry, I haven''t grasped the whole rails/backgroundrb relationship so I don''t know what I can and not do. Thanks

Hi All, One can easily code a backgroundrb worker so as it can act as a worker queue, having reached a stable status, perhaps its time we should add this feature. Why? Because if you are already running your application using BackgrounDRb, perhaps you don''t want to manage other solutions when capability to do that is right there with you. Interface? This where i need feedback. You can

Hi, I have a page were users can start jobs that may take several hours to run. BackgrounDrb is perfect for me and seems to be working well most of the time but some times I have the following problem: My worker is set up like this: class UploadWorker < BackgrounDRb::MetaWorker set_worker_name :upload_worker set_no_auto_load(true) def create(args = nil ) file = args[:file]

I need to run the same worker''s method twice per day with different arguments. Unfortunately, only the second entry in the schedule is firing. I created an experimental worker to verify this: Worker: class ExperimentWorker < BackgrounDRb::MetaWorker set_worker_name :experiment_worker def create(args = nil) # this method is called, when worker is loaded for the first time

Hi everyone, I have two workers, a connection_worker and an interface_worker, that I want to be able to call methods on each other. Initially I thought I could do this: connection_worker def alive? return true end end interface_worker def test_connection if MiddleMan.worker(:connection_worker).alive?(true) return true end end end Obviously this is a somewhat contrived

Hello, Can someone suggest the simplest way to send email from a worker? At completion, I need to send the results of it''s work to a recipient. Thanks, Doug Turner skype: dduuggllaa -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060629/94d9fb64/attachment.html