Ok, I thought it might help to mention that I have tried packet 0.1.14 and 0.1.15 and that I have tried out the last stable BackgrounDRB plugin from SVN and the later builds from the git repo. I'm thinking it has something to do with my Packet gem, but I am not getting much back from searching on "packet_master.rb Exec format error".
Another thing that may be helpful to know is that when I run "MiddleMan.worker(:billing_worker).async_charge_customer(:arg => current_customer.id)" in console I get a nil response. Thanks. On Sat, Apr 11, 2009 at 11:14 AM, James McGrath < [email protected]> wrote: > Hi Samer, thanks for the response. > > Yes, I have Xcode installed. I installed in quite some time ago (last year > off the DVD that came with my mac) to get some gems compiling. I'm running: > Xcode version 3.1 > Xcode IDE: 1099.0 > Xcode core:1100.0 > Tool Support: 1086.0 > > My Gcc version is: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. > build 5484) > > Cheers. > > > On Sat, Apr 11, 2009 at 3:11 AM, Samer Masry <[email protected]> wrote: > >> Do you have Xcode installed? >> >> On Fri, Apr 10, 2009 at 12:36 AM, James McGrath < >> [email protected]> wrote: >> >>> Hi All, I've been developing a rails app using the Bitnami RailsStack ( >>> http://bitnami.org/stack/rubystack) and it has always worked as >>> advertised. That is until I have tried to get BackgrounDRB up and running. I >>> have followed the steps given on the plugin's project page, each seems to >>> work. I the plugin install works, I can generate workers etc, but when I >>> start the backgrounDRB server I get the following errors in the backgroundrb >>> log file: >>> >>> >>/Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:116:in >>> `exec': Exec format error - packet_worker_runner >>> 7:6:log_worker:17:/Volumes/DATA/development/rails/sched/lib/workers:/Volumes/DATA/development/rails/sched/script/load_worker_env >>> (Errno::ENOEXEC) >>> >> from >>> /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:116:in >>> `fork_and_load' >>> >> from >>> /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:80:in >>> `start_worker' >>> >> from >>> /Volumes/DATA/development/rails/sched/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:16:in >>> `initialize' >>> >> from >>> /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:19:in >>> `run' >>> >> from >>> /Volumes/DATA/development/rails/sched/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:14:in >>> `initialize' >>> >> from >>> /Volumes/DATA/development/rails/sched/vendor/plugins/backgroundrb/lib/backgroundrb/bdrb_start_stop.rb:48:in >>> `new' >>> >> from >>> /Volumes/DATA/development/rails/sched/vendor/plugins/backgroundrb/lib/backgroundrb/bdrb_start_stop.rb:48:in >>> `start' >>> >> from script/backgroundrb:35 >>> >>> In my frustrations I created a rails project from scratch to make sure it >>> wasn't something in my other code / setup, but I still get the errors. >>> >>> Has anyone seen this type of error before? If you have and suggestions I >>> would love to hear them. I really want to get this plugin working as it is >>> perfect for multiple projects I am working on. BTW: I am running on MacOSX. >>> >>> Thanks. >>> >>> P.S: Thanks to all devs who created this plugin - although I am not up >>> and running yet it looks to be a most useful tool. Cheers. >>> >>> _______________________________________________ >>> Backgroundrb-devel mailing list >>> [email protected] >>> http://rubyforge.org/mailman/listinfo/backgroundrb-devel >>> >> >> >
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
