| Author |
Message |
|
| Guest |
 Posted: Fri Jan 08, 2010 4:44 am |
 |
|
|
Guest
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 10, 2010 4:09 am |
|
|
|
Guest
|
I've tried setting the RABBITMQ_NODENAME and RABBITMQ_NODE_IP_ADDRESS environment variables. But for some reason rabbitmq doesn't seem to honor them.
I was hoping the key to this problem was getting rabbitmq to only listen on 127.0.0.1.
am I on the right track here?
On Fri, Jan 8, 2010 at 10:12 AM, vishnu <pathsny@gmail.com (pathsny@gmail.com)> wrote:
|
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 10, 2010 12:56 pm |
|
|
|
Guest
|
Hi Vishnu,
On Sun, Jan 10, 2010 at 09:38:41AM +0530, vishnu wrote:
> I've tried setting the RABBITMQ_NODENAME and RABBITMQ_NODE_IP_ADDRESS
> environment variables. But for some reason rabbitmq doesn't seem to honor
> them.
> I was hoping the key to this problem was getting rabbitmq to only listen on
> 127.0.0.1.
I assume you're using the latest from default (or the new persister),
and not v1.7.0.
I've just spotted a bug in the way we process the env vars which I'll
fix either later today or tomorrow. I don't think this bug existed in
1.7.0. You should be able to set NODENAME and NODE_IP_ADDRESS in
/etc/rabbitmq/rabbitmq.conf or in the env, but I can see that that's
currently broken.
However, provided you're using some version later than v1.7.0, you can
configure this in /etc/rabbitmq/rabbitmq.config with something like:
[{rabbit, [{tcp_listeners, [{"127.0.0.1", 5672}]}]}].
This is currently working (in fact, it was the changes to support this
that have broken the env var settings. Sigh).
Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 10, 2010 1:08 pm |
|
|
|
Guest
|
On Sun, Jan 10, 2010 at 12:55:17PM +0000, Matthew Sackman wrote:
> I've just spotted a bug in the way we process the env vars which I'll
> fix either later today or tomorrow. I don't think this bug existed in
> 1.7.0. You should be able to set NODENAME and NODE_IP_ADDRESS in
> /etc/rabbitmq/rabbitmq.conf or in the env, but I can see that that's
> currently broken.
Actually, although that is broken, that only refers to putting
NODE_IP_ADDRESS in /etc/rabbitmq/rabbitmq.conf. Setting
RABBITMQ_NODE_IP_ADDRESS=127.0.0.1 in the env really does work just
fine.
And both NODENAME=foo in rabbitmq.conf and RABBITMQ_NODENAME=foo in the
env both work fine.
Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 10, 2010 5:01 pm |
|
|
|
Guest
|
Hi Vishnu,
On Sun, Jan 10, 2010 at 10:19:46PM +0530, vishnu wrote:
> hi, so for some reason I found that setting RABBITMQ_NODENAME or
> RABBITMQ_NODE_IP_ADDRESS before running the rabbitmq-server script didnt
> seem to help. But when I modified the rabbitmq-server script to
> sudo -u rabbitmq -H env <whatever> , then it does work.
>
> sadly none of this helps  . If I start the server when I'm on the internet,
> I can't shut it down when I'm off and vice versa.
Hmm, I think this is a known Mac issue. There are some people in the
office who use Macs, I'll see if I can get them to suggest some fixes
or maybe other people on the list can help out. Fortunately, I never
go anywhere near OS X...
Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Sun Jan 10, 2010 5:26 pm |
|
|
|
Guest
|
haha ok, thanks  . It's been driving me nuts
On Sun, Jan 10, 2010 at 10:31 PM, Matthew Sackman <matthew@lshift.net (matthew@lshift.net)> wrote:
Quote: Hi Vishnu,
On Sun, Jan 10, 2010 at 10:19:46PM +0530, vishnu wrote:
> hi, so for some reason I found that setting RABBITMQ_NODENAME or
> RABBITMQ_NODE_IP_ADDRESS before running the rabbitmq-server script didnt
> seem to help. But when I modified the rabbitmq-server script to
> sudo -u rabbitmq -H env <whatever> , then it does work.
>
> sadly none of this helps . If I start the server when I'm on the internet,
> I can't shut it down when I'm off and vice versa.
Hmm, I think this is a known Mac issue. There are some people in the
office who use Macs, I'll see if I can get them to suggest some fixes
or maybe other people on the list can help out. Fortunately, I never
go anywhere near OS X...
Matthew
Post received from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Mon Jan 11, 2010 3:19 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
|
| Back to top |
  
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
