similar to: one more "uninitialized constant" problem

Hi, This is my second question on the poor performance of webrick (previously I had a problem with Ajax). I have a somewhat simple Rails application which works just fine, but when I come back to work the next day, the server responds with error 500. It looks like if it is running more than 12 hours, it''ll crap-out. I don''t use CVS (which I read on the web it is a common cause

Hi everyone, I''ve been working with Mongrel, Mongrel_cluster and Apache and it is great. However, I can''t get mongrel_cluster to start at boot time. I followed the instructions from http://mongrel.rubyforge.org/docs/mongrel_cluster.html (On Boot Initialization Setup) and mongrel_cluster does not start after rebooting the machine. I made sure that the shebang line is correct and

Hi, I have a question regarding RoR and DRb. First of all, I tested with simple client/server examples and everything worked as expected. I have the following lines in my environment.rb: DRb.start_service $rem_obj = DRbObject.new(nil, "druby://#{rname}:9001") Since rem_obj is a global variable, I can call it from any controller and the invoked procedure is run on the server. However,

Hi, I''m getting the dreaded "Premature end of script headers: dispatch.cgi" message on my production server. Before I list all the things that I tried, let me mention that I already have a Rails app working on this server (installed by somebody else). First app is accessible at: http://mydomain.com/cwps and it all works. Second app is accessible at: http://mydomain.com/robo

Hi, I came across something very interesting. I use attachment_fu for file uploads and mongrel_cluster for scalability. Together they should allow me to perform multiple (concurrent) file uploads. This does work with uploads started on Windows, but on Linux something strange happens: the upload started on Linux hangs. So, if you start an upload from a Linux machine, and then start an upload from

Hello, First off, nice improvements hemant! Thanks for all the hard work. I just whipped up a new worker for a scheduled job that sends digest emails. Very smooth. However, moving some of my old backgroundrb into new backgroundrb isn''t going quite as smoothly. I have a import worker that takes a number of parameters and then is started dynamically. Here''s the a

I''m running the latest backgroundrb mainly for scheduled tasks support. As per the documentation I created the backgroundrb_schedules.yml with the following: simple_label: :class: :document_sorter_worker :worker_method: :do_work :job: :bleh :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= Time.now + 10.minutes :repeat_interval: 1.minute Under

I figured out that in the backgroundrb.yml, I had the old setting of making the database RAILS_ENV. It wasn''t a valid variable in backgroundrb 0.2.1, and it wasn''t reporting an error, so I had no idea. Once I changed it to ''development'' or ''production'', it started working. I found that if a worker has an error, it usually logs the error

Hi All, Real neophyte here, to both backgroundrb and ruby/rails in general. (Hey, we''ve all got to start somewhere, right!) :) I''ve just been playing around with the example code at http://backgroundrb.rubyforge.org/ , and trying to get all the pieces to work (btw, I''m using version 0.2.1). I did a ''generate worker example'', which created an

Dear All, I am trying to produce log-log plots in R and I was wondering if any of you have a 'template' for generating these with 'nice' labels and log-log grids? I know I can set up axes individually and use the intervals I want, however, I will be producing a large number of these plots and would not like to do this manually for each of them + I am very new to R and at the

I''m having a little difficulty understanding how to retrieve results from deceased workers (from the documentation it seems that it is possible to do this). I pasted my simple test below. If anyone could point out what i should be doing differently i''d be very grateful. My test worker: class TestWorker < BackgrounDRb::Worker::RailsBase def do_work(args)

Hi I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are detected by Rails (at least nothing is in the Rails log). Nothing untoward is in the Mongrel log. If you try and visit the application, the request times out

Hi, I have to enable batch uploads to my website with CURL and forgery protection in ApplicationController is standing in my way. I do use the restful authentication plugin and I do call login_required on all actions. Should I keep forgery protection around? Forgery protection only makes sure that the client request has originated from client''s session, right? Is there anything else

Hi everyone, I would like to know if there''s a way to synchronize the actions in a mongrel cluster. Basically, how do I make sure that a specific controller action gets executed by only one mongrel server at one time? I obviously cannot use Mutex::synchronize, because we''re talking about different processes. I looked into using optimistic and pessimistic locking. I

Hopefully I can write this out so someone understands it. We are currently running a number of Solaris servers, to which windows computers need to connect. Currently they connect via NFS using hummingbird's NFS client. This requires them to have a separate unix account along with their windows account. Our idea is to implement samba 3.0.0 to eliminate that NFS client. My current

On Thu, Jun 25, 2009 at 2:07 AM, Michael Pliskin<mike at comapping.com> wrote: > Hi all, > > > > Some disclaimer first: I am a complete newbie in mongrel and this list, so > please forgive me if I say something weird. I have a problem, I?ve googled > for a solution for quite a while and failed so far, so decided to ask here. > > > > I am trying to set up my

Dear R users, I am struggling to fit expo-linear equation to my data using "nls" function. I am always getting error message as i highlighted below in yellow color:  Theexpo-linear equation which i am interested to fit my data:       response_variable =  (c/r)*log(1+exp(r*(Day-tt))), where "Day" is time-variable my response variable rl <-