Backgroundrb devel - Sep 2006 - Can''t Connect to BackgroundRB

I''m having trouble getting backgroundrb up and running in a  
production environment.

Here''s my backgroundrb.yml:
---
port: "22222"
timer_sleep: 60
load_rails: true
environment: production
host: XXX.XX.XXX.50
database_yml: config/database.yml
acl:
   deny: all
   allow: localhost 127.0.0.1 XXX.XX.XXX.51
   order: deny,allow

I start BackgroundRB from XXX.XX.XXX.50 with script/backgroundrb/ 
start -d
I can then telnet localhost 22222 and connect to the drb server
However when I: telnet XXX.XX.XXX.50 22222 from the same machine I  
get connection refused.

Does this sound like an ACL issue or perhaps my iptables?

Thanks in advance,
Erik

Hey Eric-

On Sep 24, 2006, at 8:21 AM, Erik Morton wrote:
> I''m having trouble getting backgroundrb up and running in a
> production environment.
>
> Here''s my backgroundrb.yml:
> ---
> port: "22222"
> timer_sleep: 60
> load_rails: true
> environment: production
> host: XXX.XX.XXX.50
> database_yml: config/database.yml
> acl:
>    deny: all
>    allow: localhost 127.0.0.1 XXX.XX.XXX.51
>    order: deny,allow
>
> I start BackgroundRB from XXX.XX.XXX.50 with script/backgroundrb/
> start -d
> I can then telnet localhost 22222 and connect to the drb server
> However when I: telnet XXX.XX.XXX.50 22222 from the same machine I
> get connection refused.
>
> Does this sound like an ACL issue or perhaps my iptables?
>
> Thanks in advance,
> Erik
	It could be an acl issue but I rather think it might be a network  
issue, drb is fidgety with NAT and firewalls. IS the other server  
behind NAT or a firewall? If so you may want to look  at DRbFire, its  
an add on to drb to help it navigate firewalls and nat.


Cheers-
-Ezra

Interesting. I have a three server setup at a colo and they are all  
running out of the box firewalls from RedHat EL4. Normally I would  
put my Mongrels on the "app" server with BackgroundRB. In this case  
however my app server is a bit overloaded with a HylaFAX  
installation, so I have my mongrels on the "web" server.

Would you consider it a best practice to keep the mongrels and  
BackgroundRB on the same server?

Erik
On Sep 24, 2006, at 4:40 PM, Ezra Zygmuntowicz wrote:
> Hey Eric-
>
> On Sep 24, 2006, at 8:21 AM, Erik Morton wrote:
>
>> I''m having trouble getting backgroundrb up and running in a
>> production environment.
>>
>> Here''s my backgroundrb.yml:
>> ---
>> port: "22222"
>> timer_sleep: 60
>> load_rails: true
>> environment: production
>> host: XXX.XX.XXX.50
>> database_yml: config/database.yml
>> acl:
>>    deny: all
>>    allow: localhost 127.0.0.1 XXX.XX.XXX.51
>>    order: deny,allow
>>
>> I start BackgroundRB from XXX.XX.XXX.50 with script/backgroundrb/
>> start -d
>> I can then telnet localhost 22222 and connect to the drb server
>> However when I: telnet XXX.XX.XXX.50 22222 from the same machine I
>> get connection refused.
>>
>> Does this sound like an ACL issue or perhaps my iptables?
>>
>> Thanks in advance,
>> Erik
>
> 	It could be an acl issue but I rather think it might be a network  
> issue, drb is fidgety with NAT and firewalls. IS the other server  
> behind NAT or a firewall? If so you may want to look  at DRbFire,  
> its an add on to drb to help it navigate firewalls and nat.
>
>
> Cheers-
> -Ezra

Hey-

	Hrmm, if all your servers are in the same subnet or vlan then you  
should be able to put the drb anywhere. Mongrel on the web server is  
fine if the app server is loaded. ANd drb should work fine wherever  
you put it. I''m not sure what the problems you are having are all  
about, I have a 5 server setup with one of the servers only running  
drb processes and it talks to the other 4 servers in the subnet fine.

	It will be quicker if you put the mongrels and drb on the same  
server, but I don''t think it should meka to much difference on a  
local network.

-Ezra

On Sep 24, 2006, at 1:59 PM, Erik Morton wrote:
> Interesting. I have a three server setup at a colo and they are all  
> running out of the box firewalls from RedHat EL4. Normally I would  
> put my Mongrels on the "app" server with BackgroundRB. In this
case
> however my app server is a bit overloaded with a HylaFAX  
> installation, so I have my mongrels on the "web" server.
>
> Would you consider it a best practice to keep the mongrels and  
> BackgroundRB on the same server?
>
> Erik
> On Sep 24, 2006, at 4:40 PM, Ezra Zygmuntowicz wrote:
>
>> Hey Eric-
>>
>> On Sep 24, 2006, at 8:21 AM, Erik Morton wrote:
>>
>>> I''m having trouble getting backgroundrb up and running in
a
>>> production environment.
>>>
>>> Here''s my backgroundrb.yml:
>>> ---
>>> port: "22222"
>>> timer_sleep: 60
>>> load_rails: true
>>> environment: production
>>> host: XXX.XX.XXX.50
>>> database_yml: config/database.yml
>>> acl:
>>>    deny: all
>>>    allow: localhost 127.0.0.1 XXX.XX.XXX.51
>>>    order: deny,allow
>>>
>>> I start BackgroundRB from XXX.XX.XXX.50 with script/backgroundrb/
>>> start -d
>>> I can then telnet localhost 22222 and connect to the drb server
>>> However when I: telnet XXX.XX.XXX.50 22222 from the same machine I
>>> get connection refused.
>>>
>>> Does this sound like an ACL issue or perhaps my iptables?
>>>
>>> Thanks in advance,
>>> Erik
>>
>> 	It could be an acl issue but I rather think it might be a network  
>> issue, drb is fidgety with NAT and firewalls. IS the other server  
>> behind NAT or a firewall? If so you may want to look  at DRbFire,  
>> its an add on to drb to help it navigate firewalls and nat.
>>
>>
>> Cheers-
>> -Ezra
>

I got it working with the following ACL:

acl:
   deny:
   allow: localhost 127.0.0.1 XXX.XX.XXX.51
   order: allow,deny

I have iptables blocking port 22222 to all hosts except for the web  
server. Please let me know if you think this is a bad idea...


Thanks again

Erik
On Sep 24, 2006, at 5:07 PM, Ezra Zygmuntowicz wrote:
> Hey-
>
> 	Hrmm, if all your servers are in the same subnet or vlan then you  
> should be able to put the drb anywhere. Mongrel on the web server  
> is fine if the app server is loaded. ANd drb should work fine  
> wherever you put it. I''m not sure what the problems you are having
> are all about, I have a 5 server setup with one of the servers only  
> running drb processes and it talks to the other 4 servers in the  
> subnet fine.
>
> 	It will be quicker if you put the mongrels and drb on the same  
> server, but I don''t think it should meka to much difference on a  
> local network.
>
> -Ezra
>
> On Sep 24, 2006, at 1:59 PM, Erik Morton wrote:
>
>> Interesting. I have a three server setup at a colo and they are  
>> all running out of the box firewalls from RedHat EL4. Normally I  
>> would put my Mongrels on the "app" server with BackgroundRB.
In
>> this case however my app server is a bit overloaded with a HylaFAX  
>> installation, so I have my mongrels on the "web" server.
>>
>> Would you consider it a best practice to keep the mongrels and  
>> BackgroundRB on the same server?
>>
>> Erik
>> On Sep 24, 2006, at 4:40 PM, Ezra Zygmuntowicz wrote:
>>
>>> Hey Eric-
>>>
>>> On Sep 24, 2006, at 8:21 AM, Erik Morton wrote:
>>>
>>>> I''m having trouble getting backgroundrb up and running
in a
>>>> production environment.
>>>>
>>>> Here''s my backgroundrb.yml:
>>>> ---
>>>> port: "22222"
>>>> timer_sleep: 60
>>>> load_rails: true
>>>> environment: production
>>>> host: XXX.XX.XXX.50
>>>> database_yml: config/database.yml
>>>> acl:
>>>>    deny: all
>>>>    allow: localhost 127.0.0.1 XXX.XX.XXX.51
>>>>    order: deny,allow
>>>>
>>>> I start BackgroundRB from XXX.XX.XXX.50 with
script/backgroundrb/
>>>> start -d
>>>> I can then telnet localhost 22222 and connect to the drb server
>>>> However when I: telnet XXX.XX.XXX.50 22222 from the same
machine I
>>>> get connection refused.
>>>>
>>>> Does this sound like an ACL issue or perhaps my iptables?
>>>>
>>>> Thanks in advance,
>>>> Erik
>>>
>>> 	It could be an acl issue but I rather think it might be a  
>>> network issue, drb is fidgety with NAT and firewalls. IS the  
>>> other server behind NAT or a firewall? If so you may want to  
>>> look  at DRbFire, its an add on to drb to help it navigate  
>>> firewalls and nat.
>>>
>>>
>>> Cheers-
>>> -Ezra
>>
>

Erik-
	
	I think thats a good setup, you should be all set.

Cheers-
-Ezra

On Sep 24, 2006, at 3:07 PM, Erik Morton wrote:
> I got it working with the following ACL:
>
> acl:
>   deny:
>   allow: localhost 127.0.0.1 XXX.XX.XXX.51
>   order: allow,deny
>
> I have iptables blocking port 22222 to all hosts except for the web  
> server. Please let me know if you think this is a bad idea...
>
>
> Thanks again
>
> Erik
> On Sep 24, 2006, at 5:07 PM, Ezra Zygmuntowicz wrote:
>
>> Hey-
>>
>> 	Hrmm, if all your servers are in the same subnet or vlan then you  
>> should be able to put the drb anywhere. Mongrel on the web server  
>> is fine if the app server is loaded. ANd drb should work fine  
>> wherever you put it. I''m not sure what the problems you are
having
>> are all about, I have a 5 server setup with one of the servers  
>> only running drb processes and it talks to the other 4 servers in  
>> the subnet fine.
>>
>> 	It will be quicker if you put the mongrels and drb on the same  
>> server, but I don''t think it should meka to much difference on
a
>> local network.
>>
>> -Ezra
>>
>> On Sep 24, 2006, at 1:59 PM, Erik Morton wrote:
>>
>>> Interesting. I have a three server setup at a colo and they are  
>>> all running out of the box firewalls from RedHat EL4. Normally I  
>>> would put my Mongrels on the "app" server with
BackgroundRB. In
>>> this case however my app server is a bit overloaded with a  
>>> HylaFAX installation, so I have my mongrels on the "web"
server.
>>>
>>> Would you consider it a best practice to keep the mongrels and  
>>> BackgroundRB on the same server?
>>>
>>> Erik
>>> On Sep 24, 2006, at 4:40 PM, Ezra Zygmuntowicz wrote:
>>>
>>>> Hey Eric-
>>>>
>>>> On Sep 24, 2006, at 8:21 AM, Erik Morton wrote:
>>>>
>>>>> I''m having trouble getting backgroundrb up and
running in a
>>>>> production environment.
>>>>>
>>>>> Here''s my backgroundrb.yml:
>>>>> ---
>>>>> port: "22222"
>>>>> timer_sleep: 60
>>>>> load_rails: true
>>>>> environment: production
>>>>> host: XXX.XX.XXX.50
>>>>> database_yml: config/database.yml
>>>>> acl:
>>>>>    deny: all
>>>>>    allow: localhost 127.0.0.1 XXX.XX.XXX.51
>>>>>    order: deny,allow
>>>>>
>>>>> I start BackgroundRB from XXX.XX.XXX.50 with
script/backgroundrb/
>>>>> start -d
>>>>> I can then telnet localhost 22222 and connect to the drb
server
>>>>> However when I: telnet XXX.XX.XXX.50 22222 from the same
machine I
>>>>> get connection refused.
>>>>>
>>>>> Does this sound like an ACL issue or perhaps my iptables?
>>>>>
>>>>> Thanks in advance,
>>>>> Erik
>>>>
>>>> 	It could be an acl issue but I rather think it might be a  
>>>> network issue, drb is fidgety with NAT and firewalls. IS the  
>>>> other server behind NAT or a firewall? If so you may want to  
>>>> look  at DRbFire, its an add on to drb to help it navigate  
>>>> firewalls and nat.
>>>>
>>>>
>>>> Cheers-
>>>> -Ezra
>>>
>>
>