Thu Mar 14 15:04:54 GMT 2013
In order to get the service approach to work correctly, I modified rabbitmq-server in /etc/init.d as follows:
[root at cluster1 init.d]# diff rabbitmq-server.20130501 rabbitmq-server
< RABBITMQ_PID_FILE=$PID_FILE $START_PROG $DAEMON \
> RABBITMQ_PID_FILE=$PID_FILE $START_PROG $DAEMON -detached \
[root at cluster1 init.d]#
I changed it there because DAEMON appears to be the rabbitmq-server
[root at cluster1 init.d]# grep DAEMON rabbitmq-server
test -x $DAEMON || exit 0
RABBITMQ_PID_FILE=$PID_FILE $START_PROG $DAEMON -detached \
[root at cluster1 init.d]#
When I performed service rabbitmq-server start
It just hung and never came back with a prompt.
However in another window I confirmed the rabbitmq-server was running
I then killed the service console window and looked at the startup_err file:
[root at cluster1 init.d]# more /var/log/rabbitmq/startup_err
Warning: PID file not written; -detached was passed.
and then i had to separately kill the process(s) associated with rabbitmq.
so my questions are thus:
1) the documentation states this is how to normally start the server. Is that normally for all modes or just for a clustered node approach?
2) What can I do to keep the command from hanging if started as a service?
> -------Original Message-------
> From: Gerald Kuch <jkuch at gopivotal.com>
> To: srd <srd at duneram.com>, Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com>
> Subject: Re: [rabbitmq-discuss] another question on cookies version 3.0.4
> Sent: 01 May '13 19:52
> Ooops, my fingers auto-completed the "/etc/init.d" on the end of the
> sentence. Forget about that part.
> On Wed, May 1, 2013 at 12:51 PM, Gerald Kuch <[LINK:
> mailto:jkuch at gopivotal.com] jkuch at gopivotal.com> wrote:
> Depends how you started it: Either /sbin/service/rabbitmq-server stop or
> Of course 'kill' will stop it, but the cleanliness of doing the
> former is preferable in non-emergency circumstances.
> On Wed, May 1, 2013 at 6:26 AM, srd <[LINK: mailto:srd at duneram.com]
> srd at duneram.com> wrote:
> Thank you for your help. I will give this a try.
> I've been starting it wrong all this time.
> what is the best way to stop the server? up until now I have found no
> good way to stop it except
> ps -efwww | grep rabbit
> and then with that kill off the 4-6 associated jobs.
> > -------Original Message-------
> > From: Tim Watson <[LINK: mailto:tim at rabbitmq.com] tim at rabbitmq.com>
> > To: srd <[LINK: mailto:srd at duneram.com] srd at duneram.com>, Discussions
> about RabbitMQ <[LINK: mailto:rabbitmq-discuss at lists.rabbitmq.com]
> rabbitmq-discuss at lists.rabbitmq.com>
> > Subject: Re: [rabbitmq-discuss] another question on cookies version
> > Sent: 01 May '13 13:21
> > Hi,
> > On 1 May 2013, at 14:15, srd wrote:
> > > so my questions are:
> > > 1) How does one normally start the server?
> > Depending on the platform, either /sbin/service rabbitmq-server start
> or via /etc/init.d/.
> > > 2) my reason for wanting to do cookies is I wanted to setup a multi
> node cluster (different servers)
> > > If I start a server (no parameters) on each server the cookie
> hash is different.
> > You need to ensure that all the cookies are the same. You can do this
> by placing the .erlang.cookie file in the /home/rabbitmq directory on each
> > > 3) I have looked at the clustering guide but haven't succeeded
> in a setup using it. How does one normally synchronize the cookies
> across servers?
> > That's up to you - rabbit doesn't provide anything out of the
> box to do this.
> > > 4) where is the cookie file stored? I found one on the rabbitmq
> user's root directory. Is that where it is stored?
> > That's correct.
> > > 5) If I have to set a cookie value, is there a config file where it
> can be set (or env variable?) and what is the syntax to set it?
> > >
> > I would recommend just using the cookie stored in the rabbitmq
> user's home directory.
> > Cheers,
> > Tim
> rabbitmq-discuss mailing list
> [LINK: mailto:rabbitmq-discuss at lists.rabbitmq.com]
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss