[rabbitmq-discuss] Unable to start rabbitmq-server on a fresh installed server

[Oren Shomron]

I've had this happen to me as well.
Killing epmd by hand and then starting RabbitMQ seemed to do the job.

Also, make sure name resolution is working for your local node name - this 
also can cause RabbitMQ to fail to start.

  - Oren

On Friday, May 31, 2013 10:44:40 AM UTC-4, Steven Yue wrote:
>
> Hi, everyone
>
> I'm trying to install rabbitmq-server on my VPS server. The server is 
> running newly fresh installed Ubuntu 12.04, and the rabbitmq is installed 
> from APT repository.
>
> The console shows this information:
>
> * Starting message broker rabbitmq-server
> * FAILED - check /var/log/rabbitmq/startup_\{log, _err\}
>
>
> And I check the log file, it shows this:
>
> ERROR: node with name "rabbit" already running on "mydomain"
>
> DIAGNOSTICS
> ===========
>
> nodes in question: [rabbit@ mydomain]
>
> hosts, their running nodes and ports:
> - mydomain: [{rabbit,56948}]
>
> current node details:
> - node name: rabbitmqprelaunch5633@ mydomain
> - home dir: /var/lib/rabbitmq
> - cookie hash: AfrR2Uw6t3aBV6UMzo2KHA==
>
> When I run 'ps aux | grep rabbit', I get this:
>
> rabbitmq  5607  0.0  0.0   7416   316 ?        S    14:55   0:00 
> /usr/lib/erlang/erts-5.8.5/bin/epmd -daemon
>
> I tried to stop the server, by running:
>
> sudo rabbitmqctl stop
>
> And it show: Error: unable to connect to node rabbit@ mydomain: nodedown
>
> I've tried to google this problem, and followed those instructions in the 
> following posts, but still couldn't get any luck:
>
> http://stackoverflow.com/questions/8737754/node-with-name-rabbit-already-running-but-also-unable-to-connect-to-node
> http://stackoverflow.com/questions/10347751/rabbitmq-refusing-to-start
>
> I want to know why this happens on a newly install server? And can anyone 
> help me out to solve this?
>
> Thanks
>
> Steven
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130602/2164a148/attachment.htm>