Backgroundrb devel - Aug 2008 - Starting It In Production?

Hi everyone!

backgroundrb works fine in my local machine in development mode.  When
I first tried it out in my VPS in production tho, I ran into some
problems.  It seems that it keeps looking for the development database
even if I''ve explicitly told it to start the production environment.

Here''s how I started it, then what my config/backgroundrb.yml file
looks like:
http://pastebin.com/m4b7af1b6

I did some searching then saw that this was a problem 2 years ago, but
was supposedly fixed:
http://rubyforge.org/pipermail/backgroundrb-devel/2006-September/000359.html

What I did for now was put the production database details in
database.yml under "development" so it''s pointing to the same
database.  When I tried to start backgroundrb this time, I get:
http://pastebin.com/m4d0084ab

I checked and make sure ~/path/to/app/tmp/pids directory existed
though.  Does this mean backgroundrb is unable to make its own *.pid
files?

Thank you for your time,
-- 
Ramon Tayag

On Aug 12, 2008, at 3:40 PM, Ramon Miguel M. Tayag
wrote:
> backgroundrb works fine in my local machine in development mode.  When
> I first tried it out in my VPS in production tho, I ran into some
> problems.  It seems that it keeps looking for the development database
> even if I''ve explicitly told it to start the production
environment.
>
You can try starting the daemon by prefixing with  
"RAILS_ENV=production", i.e.

   RAILS_ENV=production script/backgroundrb start

On Tue, Aug 12, 2008 at 1:10 PM, Ramon Miguel M. Tayag
<ramon.tayag at gmail.com> wrote:
> Hi everyone!
>
> backgroundrb works fine in my local machine in development mode.  When
> I first tried it out in my VPS in production tho, I ran into some
> problems.  It seems that it keeps looking for the development database
> even if I''ve explicitly told it to start the production
environment.
>
Which version of BackgrounDRb? whats the output of?

./script/backgroundrb --version

(preferred version is the git master copy)

You can also try:

./script/backgroundrb --environment=production
> Here''s how I started it, then what my config/backgroundrb.yml file
looks like:
> http://pastebin.com/m4b7af1b6
>
No problems here. :)

> I did some searching then saw that this was a problem 2 years ago, but
> was supposedly fixed:
>
http://rubyforge.org/pipermail/backgroundrb-devel/2006-September/000359.html
Anything thats two years old should be discarded.
>
> What I did for now was put the production database details in
> database.yml under "development" so it''s pointing to the
same
> database.  When I tried to start backgroundrb this time, I get:
> http://pastebin.com/m4d0084ab
>
> I checked and make sure ~/path/to/app/tmp/pids directory existed
> though.  Does this mean backgroundrb is unable to make its own *.pid
> files?

Check if you have permissons to write to that directory. Usually cap
set symlinks, so as tmp and public are shared between different
deployments. Double check if path is correct.

Please keep the discussion on the list, its immensely useful for folks
looking for solutions to similar problems.


---------------------------------------------------------------

Yup, I just reinstalled it today and got the instructions from the
website.  Got it from git.

version: 1.0.4

It seems that when I do a simple script/backgroundrb I get permission
errors.  However, I see that the current account I''m in is the owner
of script/backgroundrb, tmp, and tmp/pids (I did an "ls -l" to check)
.  What I end up having to run is "RAILS_ENV=production ruby
script/backgroundrb start" instead.  Not sure why...

-e production or --environment=production don''t work.

But you''re right.  I didn''t have the "tmp" folder in
/home/ramon/myapp/shared

Thank you :)

On Tue, Aug 12, 2008 at 3:54 PM, hemant <gethemant at gmail.com>
wrote:
>
> Which version of BackgrounDRb? whats the output of?
>
> ./script/backgroundrb --version
>
> (preferred version is the git master copy)
>
> You can also try:
>
> ./script/backgroundrb --environment=production
>
> No problems here. :)
>
> Anything thats two years old should be discarded.
>
> Check if you have permissons to write to that directory. Usually cap
> set symlinks, so as tmp and public are shared between different
> deployments. Double check if path is correct.
--
Ramon Tayag



-- 
Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
own coals.

http://gnufied.org

Hello,

gnufied pushed a patch earlier today that seems to have fixed this problem
for me.

Do you still get this problem on your local copy if you update to the latest
Git?

Regards
Kieran


On Tue, Aug 12, 2008 at 7:40 PM, Ramon Miguel M. Tayag <
ramon.tayag at gmail.com> wrote:
> Hi everyone!
>
> backgroundrb works fine in my local machine in development mode.  When
> I first tried it out in my VPS in production tho, I ran into some
> problems.  It seems that it keeps looking for the development database
> even if I''ve explicitly told it to start the production
environment.
>
> Here''s how I started it, then what my config/backgroundrb.yml file
looks
> like:
> http://pastebin.com/m4b7af1b6
>
> I did some searching then saw that this was a problem 2 years ago, but
> was supposedly fixed:
>
>
http://rubyforge.org/pipermail/backgroundrb-devel/2006-September/000359.html
>
> What I did for now was put the production database details in
> database.yml under "development" so it''s pointing to the
same
> database.  When I tried to start backgroundrb this time, I get:
> http://pastebin.com/m4d0084ab
>
> I checked and make sure ~/path/to/app/tmp/pids directory existed
> though.  Does this mean backgroundrb is unable to make its own *.pid
> files?
>
> Thank you for your time,
> --
> Ramon Tayag
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080815/af0e6ba8/attachment.html>

Not anymore :) Works great!!

On Fri, Aug 15, 2008 at 2:31 PM, Kieran P <kieran776 at gmail.com>
wrote:
> Hello,
>
> gnufied pushed a patch earlier today that seems to have fixed this problem
> for me.
>
> Do you still get this problem on your local copy if you update to the
latest
> Git?
>
> Regards
> Kieran
>
>
> On Tue, Aug 12, 2008 at 7:40 PM, Ramon Miguel M. Tayag
> <ramon.tayag at gmail.com> wrote:
>>
>> Hi everyone!
>>
>> backgroundrb works fine in my local machine in development mode.  When
>> I first tried it out in my VPS in production tho, I ran into some
>> problems.  It seems that it keeps looking for the development database
>> even if I''ve explicitly told it to start the production
environment.
>>
>> Here''s how I started it, then what my config/backgroundrb.yml
file looks
>> like:
>> http://pastebin.com/m4b7af1b6
>>
>> I did some searching then saw that this was a problem 2 years ago, but
>> was supposedly fixed:
>>
>>
http://rubyforge.org/pipermail/backgroundrb-devel/2006-September/000359.html
>>
>> What I did for now was put the production database details in
>> database.yml under "development" so it''s pointing to
the same
>> database.  When I tried to start backgroundrb this time, I get:
>> http://pastebin.com/m4d0084ab
>>
>> I checked and make sure ~/path/to/app/tmp/pids directory existed
>> though.  Does this mean backgroundrb is unable to make its own *.pid
>> files?
>>
>> Thank you for your time,
>> --
>> Ramon Tayag


-- 
Ramon Tayag