similar to: does backgroundrb server need rails environment?

I''m working on an application that does extensive database searching. These searches can take a long time, so we have been working on moving the searches to a backgroundrb worker task so we can provide a sexy AJAX progress bar, and populate the search results as they are available. All of this seems to work fine until the size of the search results gets sufficiently large, when we start

Everything works fine on my development box (Ubuntu 7.10, Ruby 1.8.6) but on my server (Fedora Core 6, Ruby 1.8.5) when I run script/backgroundrb start, the process fails to start. This is with Rails 2.0.2 frozen in the app, and I have the most recent version of the plugin (r297). Is Ruby 1.8.6 a requirement for backgroundrb now? I can''t figure any other reason it would fail...

I have the next including files structure : - controller fileaA.rb including line (#8): require "fileB"... - /lib/fileB.rb with main header: load ''backgroundrb/worker.rb'' load ''backgroundrb/ worker_rails.rb'' class FileB <

Hello backgroundrb-devel my name is Teeranit Ruangdet. I''m fairly new to Ruby on Rails so please bear with me here. I''m currently on a project where I need to import a whole bunch of records from spreadsheet(.csv) and save them in the database. My problem is that while I''m importing (huge file...say 5000 employees), no one else can access the website (it basically block

I override some Rails'' configuration options in my project, like: config.database_configuration_file = "#{RAILS_ROOT}/local/config/ database.yml" But they aren''t picked up in BackgroundRB because Rails ActiveRecord is just initialized directly in MasterWorker#load_rails_env: db_config_file = YAML.load(ERB.new(IO.read("#{RAILS_HOME}/

Hi Folks, I have been working to fix BackgrounDRb memory usage as such. Ruby1.8 GC isn''t fork friendly and it seems to use a lot of memory because when you fork, it sets a bit in all the objects in global scope which causes OS to all pages in child process. A classic solution is to use fork and exec, rather than just fork. Its working and pretty stable, but you loose ability to pass

I get this error periodically in backgroundrb.log, but only on my production box (the one running ruby 1.8.5) - my dev box doesn''t get this error. As far as I can tell, everything is working ok, despite the error (I don''t really know how to determine if the jobs are getting threaded successfully, but they are running, that I am sure of). Here''s the dump: no

Hi there I have recently upgraded to v1.0.1 and I''ve noticed an issue which I don''t believe was present in the 0.2 release. In my worker class I am logging errors as follows: logger.error "the error message" However, this now causes an exception to be thrown in the new version: undefined method `error'' for

i ran rake backgroundrb:setup and modified the default config/backgroundrb.yml file as: --- port: "22223" timer_sleep: 60 load_rails: true environment: production host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow and my database.yml production: adapter: mysql database: chip2_production username: xxxxx password:

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

I recently post on my blog about setting up a Rails environment with RSpec in Windows, and someone left a comment saying that it doesn''t work in EdgeRails. I so I played around with it a bit and was able to confirm that none RSpec appears broken on EdgeRails. I''ll post the various error messages I received below. I''m not expecting any sort of patch or something for this

I just noticed after upgrade from Asterisk 1.4.39 to 1.8.8 my caller ID is not working WARNING[1671]: chan_sip.c:13956 check_auth: username mismatch, have <11>, digest has <pstn-1270> NOTICE[1671]: chan_sip.c:22048 handle_request_invite: Failed to authenticate device "KMIEC Z" <sip:7804715665 at 10.0.0.110>;tag=1c976040515 -- Joseph

Hi, I have a relatively simple Worker: (I added the line numbers to the email, they are not in the worker) ##################################################################################### class ImagetestWorker < BackgrounDRb::MetaWorker set_worker_name :imagetest_worker def create(args = nil) end def save_image(args) @newbook = Book.new @newbook.comment =

I''m getting an error 500 and I''m at my wits end as to what could be causing it. I''m sure the path to the ruby executable is correct so what else could be causing it? -- Posted via http://www.ruby-forum.com/.

Hi Bill, I have "version 1" backgroundrb running on my development server with rails 1.2.1, with no issues (other than the left over DB connections blocking up my MySQL server, which isn''t exactly a new problem). Going to move production servers to rails 1.2.1 very soon, I''ll post back if there''s any trouble. Still would *really* like to get version

Does the sort order matter in sip.conf file? I know sort order might effect: allow=ulaw allow=alaw but does it matter where I place: insecure=invite ? The reason I'm asking is that I've loaded almost two identical (sip.conf and extension.conf) files on the same asterisk server and with one set insecure=invite is working correctly. When I load the second set of dial plan (sip.conf and

Hi, I was trying to schedule a worker to run during the midnight hour like this: :schedules: :collector: :process_something: :trigger_args: 30 * 0 * * 2,3,4,5,6 When I try to start backgroundrb, the "collector" worker failed to start up and I find this in backgroundrb_server.log: /home/mengkuan/apps/testrailsapp/current/vendor/plugins/backgroundrb/

I'm using "insecure=invite" with two different dial plans, it it working with one dial plan but not with the other. What other parameters could influence "insecure=invite" In sip.conf below "insecure=invite" is working OK [pstn-1270] type=friend secret=spa3k username=voice-1270 mailbox=369 host=dynamic insecure=invite canreinvite=no disallow=all allow=ulaw

Hi , If you are following commits, I have pushed following changes: 1. Now, you can specify :environment option in config file to load production environment and stuff. 2. Exeptions that were exposed to the user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory